Bytbil Accesspaket 2.3.11

Does Bytbil Accesspaket work with WordPress 6.1.1 and PHP 8.1.12? A smoke test was performed on .

Summary

Errors
7PHP warnings
18PHP notices
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

Memory usage: 87.99 KiB
The average PHP memory usage increased by this amount after activating by the plugin.

Page speed impact: insignificant.
The plugin didn't make the site noticeably slower.

Environment
WordPress version6.1.1
PHP version8.1.12
MySQL version10.6.10
PHP memory limit512M
Plugin Info
Last updated
Active installs <10
WordPress.org page https://wordpress.org/plugins/triggerfish-bytbil-accesspaket/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 9

Plugins ‹ Test site — WordPress

Page screenshot: Plugins ‹ Test site — WordPress
URL /wp-admin/plugins.php?plugin_status=all&paged=1&s
Requested URL /wp-admin/plugins.php?action=activate&plugin=triggerfish-bytbil-accesspaket%2Ftriggerfish-bytbil-accesspaket.php&plugin_status=all&paged=1&s&_wpnonce=7ef0111516
Aspect after-activation
HTTP status 200
Load time 0.429 s
Memory usage 3.15 MiB
JS errors None
Resource errors None

Settings → Access package

Page screenshot: Settings → Access package
URL /wp-admin/options-general.php?page=access-package.php
Aspect menu-item
HTTP status 200
Load time 0.610 s
Memory usage 3.16 MiB
JS errors None
Resource errors None

Settings → Access package → Filters

Page screenshot: Settings → Access package → 
                    Filters
URL /wp-admin/options-general.php?page=access-package.php&tab=filter
Aspect menu-item-tab
HTTP status 200
Load time 0.386 s
Memory usage 3.13 MiB
JS errors None
Resource errors None

Settings → Access package → Theming

Page screenshot: Settings → Access package → 
                    Theming
URL /wp-admin/options-general.php?page=access-package.php&tab=theming
Aspect menu-item-tab
HTTP status 200
Load time 0.357 s
Memory usage 3.13 MiB
JS errors None
Resource errors None

Settings → Access package → Description

Page screenshot: Settings → Access package → 
                    Description
URL /wp-admin/options-general.php?page=access-package.php&tab=description
Aspect menu-item-tab
HTTP status 200
Load time 0.364 s
Memory usage 3.13 MiB
JS errors None
Resource errors None

Settings → Access package → Mail

Page screenshot: Settings → Access package → 
                    Mail
URL /wp-admin/options-general.php?page=access-package.php&tab=mail
Aspect menu-item-tab
HTTP status 200
Load time 0.375 s
Memory usage 3.13 MiB
JS errors None
Resource errors None

Settings → Access package → DNB

Page screenshot: Settings → Access package → 
                    DNB
URL /wp-admin/options-general.php?page=access-package.php&tab=dnb
Aspect menu-item-tab
HTTP status 200
Load time 0.533 s
Memory usage 3.13 MiB
JS errors None
Resource errors None

Settings → Access package → Single car view

Page screenshot: Settings → Access package → 
                    Single car view
URL /wp-admin/options-general.php?page=access-package.php&tab=single-car
Aspect menu-item-tab
HTTP status 200
Load time 0.348 s
Memory usage 3.13 MiB
JS errors None
Resource errors None

Test site – Just another WordPress site

Page screenshot: Test site – Just another WordPress site
URL /
Aspect front-page
HTTP status 200
Load time 0.218 s
Memory usage 2.99 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.276 s0.316 s+0.040 s3.05 MiB3.14 MiB+ 97.49 KiB
/wp-admin/edit.php0.176 s0.205 s+0.029 s3.07 MiB3.17 MiB+ 97.49 KiB
/wp-admin/post-new.php0.748 s0.824 s+0.076 s4.97 MiB5.08 MiB+ 117.3 KiB
/wp-admin/upload.php0.653 s0.275 s-0.378 s2.99 MiB3.07 MiB+ 80.82 KiB
/wp-admin/options-writing.php0.130 s0.331 s+0.201 s2.99 MiB3.05 MiB+ 66.73 KiB
/wp-admin/media-new.php0.261 s0.184 s-0.077 s2.97 MiB3.06 MiB+ 93.01 KiB
/wp-admin/edit-tags.php?taxonomy=category0.167 s0.169 s+0.002 s2.98 MiB3.08 MiB+ 97.45 KiB
/wp-admin/post-new.php?post_type=page0.630 s0.721 s+0.091 s4.96 MiB5.07 MiB+ 110.51 KiB
/wp-admin/options-discussion.php0.190 s0.195 s+0.005 s2.97 MiB3.05 MiB+ 80.58 KiB
/wp-admin/edit-comments.php0.204 s0.197 s-0.007 s3 MiB3.08 MiB+ 80.08 KiB
/0.266 s0.208 s-0.058 s2.94 MiB2.99 MiB+ 46.45 KiB
Average 0.336 s0.330 s-0.007 s3.35 MiB3.44 MiB+ 87.99 KiB

Code Statistics

Note: Third-party libraries and minified JS/CSS files are excluded from these statistics where possible, so the numbers you see here may be lower than those reported by other tools.

PHP
Language % Lines of code Comment lines Files
PHP82.1%3,4201956
PO File7.9%3281891
JavaScript5.8%242216
SVG3.0%1231111
JSON1.2%5102
CSS0.0%222
HTML0.0%101
Total 4,167 242 79

PHP Code Analysis | More results »

Lines of code 2,500
Total complexity 291
Median class complexity 2.0
Median method complexity 1.0
Most complex class TF\AccessPackage\Metabox
Most complex function TF\AccessPackage\Sync\Car::syncCarToPost()
Classes 38
Methods 102
Functions 6

Additions

Things that the plugin adds to the site. This section is not intended to be comprehensive. The test tool only looks for a few specific types of added content.

Custom Post Types 1

ID Name
tf_carBil

PHP Error Log 25 lines

[01-Dec-2022 00:23:48 UTC] PHP Warning:  foreach() argument must be of type array|object, string given in /wp-content/plugins/triggerfish-bytbil-accesspaket/filter-fields/class-type.php on line 14
[01-Dec-2022 00:23:49 UTC] PHP Warning:  foreach() argument must be of type array|object, string given in /wp-content/plugins/triggerfish-bytbil-accesspaket/filter-fields/class-type.php on line 14
[01-Dec-2022 00:23:50 UTC] PHP Warning:  foreach() argument must be of type array|object, string given in /wp-content/plugins/triggerfish-bytbil-accesspaket/filter-fields/class-type.php on line 14
[01-Dec-2022 00:23:51 UTC] PHP Warning:  foreach() argument must be of type array|object, string given in /wp-content/plugins/triggerfish-bytbil-accesspaket/filter-fields/class-type.php on line 14
[01-Dec-2022 00:23:53 UTC] PHP Warning:  foreach() argument must be of type array|object, string given in /wp-content/plugins/triggerfish-bytbil-accesspaket/filter-fields/class-type.php on line 14
[01-Dec-2022 00:23:54 UTC] PHP Warning:  foreach() argument must be of type array|object, string given in /wp-content/plugins/triggerfish-bytbil-accesspaket/filter-fields/class-type.php on line 14
[01-Dec-2022 00:23:55 UTC] PHP Warning:  foreach() argument must be of type array|object, string given in /wp-content/plugins/triggerfish-bytbil-accesspaket/filter-fields/class-type.php on line 14
[01-Dec-2022 00:23:58 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>accesspackage/v1/cars</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5835
[01-Dec-2022 00:23:58 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>accesspackage/v1/filters</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5835
[01-Dec-2022 00:23:58 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>accesspackage/v1/filters</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5835
[01-Dec-2022 00:23:58 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. REST API <code>$args</code> should be an array of arrays. Non-array value detected for <code>accesspackage/v1/filters</code>. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.1.0.) in /wp-includes/functions.php on line 5835
[01-Dec-2022 00:23:58 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>accesspackage/v1/mail</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5835
[01-Dec-2022 00:23:58 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. REST API <code>$args</code> should be an array of arrays. Non-array value detected for <code>accesspackage/v1/mail</code>. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.1.0.) in /wp-includes/functions.php on line 5835
[01-Dec-2022 00:23:58 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>accesspackage/v1/saveFilterOrder</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5835
[01-Dec-2022 00:23:58 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>accesspackage/v1/saveHeroImage</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5835
[01-Dec-2022 00:23:58 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>accesspackage/v1/saveFallbackImage</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5835
[01-Dec-2022 00:24:01 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>accesspackage/v1/cars</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5835
[01-Dec-2022 00:24:01 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>accesspackage/v1/filters</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5835
[01-Dec-2022 00:24:01 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>accesspackage/v1/filters</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5835
[01-Dec-2022 00:24:01 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. REST API <code>$args</code> should be an array of arrays. Non-array value detected for <code>accesspackage/v1/filters</code>. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.1.0.) in /wp-includes/functions.php on line 5835
[01-Dec-2022 00:24:01 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>accesspackage/v1/mail</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5835
[01-Dec-2022 00:24:01 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. REST API <code>$args</code> should be an array of arrays. Non-array value detected for <code>accesspackage/v1/mail</code>. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.1.0.) in /wp-includes/functions.php on line 5835
[01-Dec-2022 00:24:01 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>accesspackage/v1/saveFilterOrder</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5835
[01-Dec-2022 00:24:01 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>accesspackage/v1/saveHeroImage</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5835
[01-Dec-2022 00:24:01 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>accesspackage/v1/saveFallbackImage</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5835
See also: All tests for this plugin, How to Hide the "Access package" Admin Menu