Bytbil Accesspaket 2.3.6

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

Summary

Errors
23PHP warnings
14PHP notices
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

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

Page speed impact: 0.101 seconds
The average page load time increased by this amount after activating the plugin.

Environment
WordPress version5.9
PHP version7.4.8
MySQL version8.0.21
PHP memory limit256M
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=6d2a52b063
Aspect after-activation
HTTP status 200
Load time 0.301 s
Memory usage 3.42 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.626 s
Memory usage 3.4 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.456 s
Memory usage 3.37 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.443 s
Memory usage 3.37 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.423 s
Memory usage 3.37 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.423 s
Memory usage 3.37 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.367 s
Memory usage 3.37 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.601 s
Memory usage 3.37 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.246 s
Memory usage 3.4 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.362 s0.342 s-0.020 s3.36 MiB3.46 MiB+ 95.24 KiB
/wp-admin/edit.php0.206 s0.206 s+0.000 s3.39 MiB3.49 MiB+ 94.53 KiB
/wp-admin/post-new.php1.021 s1.133 s+0.112 s6.14 MiB6.26 MiB+ 114.8 KiB
/wp-admin/upload.php0.383 s0.324 s-0.059 s3.24 MiB3.34 MiB+ 102.84 KiB
/wp-admin/options-writing.php0.300 s0.143 s-0.157 s3.24 MiB3.32 MiB+ 85.96 KiB
/wp-admin/media-new.php0.233 s0.164 s-0.069 s3.22 MiB3.32 MiB+ 103.02 KiB
/wp-admin/edit-tags.php?taxonomy=category0.197 s0.188 s-0.009 s3.25 MiB3.35 MiB+ 103.19 KiB
/wp-admin/post-new.php?post_type=page0.952 s2.201 s+1.249 s6.14 MiB6.25 MiB+ 112 KiB
/wp-admin/options-discussion.php0.220 s0.326 s+0.106 s3.22 MiB3.32 MiB+ 102.59 KiB
/wp-admin/edit-comments.php0.216 s0.223 s+0.007 s3.26 MiB3.35 MiB+ 94.09 KiB
/0.267 s0.213 s-0.054 s3.35 MiB3.4 MiB+ 52.92 KiB
Average 0.396 s0.497 s+0.101 s3.8 MiB3.9 MiB+ 96.47 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,4181956
PO File7.9%3281891
JavaScript5.8%242216
SVG3.0%1231111
JSON1.2%5102
CSS0.0%222
HTML0.0%101
Total 4,165 242 79

PHP Code Analysis | More results »

Lines of code 2,498
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 37 lines

[08-Feb-2022 14:34:38 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/triggerfish-bytbil-accesspaket/filter-fields/class-type.php on line 14
[08-Feb-2022 14:34:39 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/triggerfish-bytbil-accesspaket/filter-fields/class-type.php on line 14
[08-Feb-2022 14:34:40 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/triggerfish-bytbil-accesspaket/filter-fields/class-type.php on line 14
[08-Feb-2022 14:34:40 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/triggerfish-bytbil-accesspaket/filter-fields/class-type.php on line 14
[08-Feb-2022 14:34:41 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/triggerfish-bytbil-accesspaket/filter-fields/class-type.php on line 14
[08-Feb-2022 14:34:42 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/triggerfish-bytbil-accesspaket/filter-fields/class-type.php on line 14
[08-Feb-2022 14:34:43 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/triggerfish-bytbil-accesspaket/filter-fields/class-type.php on line 14
[08-Feb-2022 14:34:45 UTC] PHP Notice:  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 5768
[08-Feb-2022 14:34:45 UTC] PHP Notice:  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 5768
[08-Feb-2022 14:34:45 UTC] PHP Notice:  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 5768
[08-Feb-2022 14:34:45 UTC] PHP Notice:  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 5768
[08-Feb-2022 14:34:45 UTC] PHP Notice:  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 5768
[08-Feb-2022 14:34:45 UTC] PHP Notice:  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 5768
[08-Feb-2022 14:34:45 UTC] PHP Notice:  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 5768
[08-Feb-2022 14:34:45 UTC] PHP Warning:  array_intersect_key(): Expected parameter 1 to be an array, string given in /wp-includes/rest-api/class-wp-rest-server.php on line 1482
[08-Feb-2022 14:34:45 UTC] PHP Warning:  array_intersect_key(): Expected parameter 1 to be an array, string given in /wp-includes/rest-api/class-wp-rest-server.php on line 1482
[08-Feb-2022 14:34:45 UTC] PHP Warning:  array_intersect_key(): Expected parameter 1 to be an array, string given in /wp-includes/rest-api/class-wp-rest-server.php on line 1482
[08-Feb-2022 14:34:45 UTC] PHP Warning:  array_intersect_key(): Expected parameter 1 to be an array, string given in /wp-includes/rest-api/class-wp-rest-server.php on line 1482
[08-Feb-2022 14:34:47 UTC] PHP Warning:  array_intersect_key(): Expected parameter 1 to be an array, string given in /wp-includes/rest-api/class-wp-rest-server.php on line 1482
[08-Feb-2022 14:34:47 UTC] PHP Warning:  array_intersect_key(): Expected parameter 1 to be an array, string given in /wp-includes/rest-api/class-wp-rest-server.php on line 1482
[08-Feb-2022 14:34:47 UTC] PHP Warning:  array_intersect_key(): Expected parameter 1 to be an array, string given in /wp-includes/rest-api/class-wp-rest-server.php on line 1482
[08-Feb-2022 14:34:47 UTC] PHP Warning:  array_intersect_key(): Expected parameter 1 to be an array, string given in /wp-includes/rest-api/class-wp-rest-server.php on line 1482
[08-Feb-2022 14:34:49 UTC] PHP Notice:  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 5768
[08-Feb-2022 14:34:49 UTC] PHP Notice:  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 5768
[08-Feb-2022 14:34:49 UTC] PHP Notice:  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 5768
[08-Feb-2022 14:34:49 UTC] PHP Notice:  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 5768
[08-Feb-2022 14:34:49 UTC] PHP Notice:  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 5768
[08-Feb-2022 14:34:49 UTC] PHP Notice:  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 5768
[08-Feb-2022 14:34:49 UTC] PHP Notice:  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 5768
[08-Feb-2022 14:34:49 UTC] PHP Warning:  array_intersect_key(): Expected parameter 1 to be an array, string given in /wp-includes/rest-api/class-wp-rest-server.php on line 1482
[08-Feb-2022 14:34:49 UTC] PHP Warning:  array_intersect_key(): Expected parameter 1 to be an array, string given in /wp-includes/rest-api/class-wp-rest-server.php on line 1482
[08-Feb-2022 14:34:49 UTC] PHP Warning:  array_intersect_key(): Expected parameter 1 to be an array, string given in /wp-includes/rest-api/class-wp-rest-server.php on line 1482
[08-Feb-2022 14:34:49 UTC] PHP Warning:  array_intersect_key(): Expected parameter 1 to be an array, string given in /wp-includes/rest-api/class-wp-rest-server.php on line 1482
[08-Feb-2022 14:34:50 UTC] PHP Warning:  array_intersect_key(): Expected parameter 1 to be an array, string given in /wp-includes/rest-api/class-wp-rest-server.php on line 1482
[08-Feb-2022 14:34:50 UTC] PHP Warning:  array_intersect_key(): Expected parameter 1 to be an array, string given in /wp-includes/rest-api/class-wp-rest-server.php on line 1482
[08-Feb-2022 14:34:50 UTC] PHP Warning:  array_intersect_key(): Expected parameter 1 to be an array, string given in /wp-includes/rest-api/class-wp-rest-server.php on line 1482
[08-Feb-2022 14:34:50 UTC] PHP Warning:  array_intersect_key(): Expected parameter 1 to be an array, string given in /wp-includes/rest-api/class-wp-rest-server.php on line 1482
See also: All tests for this plugin, How to Hide the "Access package" Admin Menu