Bytbil Accesspaket 2.3.8

Does Bytbil Accesspaket work with WordPress 5.9.3 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: 90.7 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 version5.9.3
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=04ccd76cfe
Aspect after-activation
HTTP status 200
Load time 0.275 s
Memory usage 3.43 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.677 s
Memory usage 3.41 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.396 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.377 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.346 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.360 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.339 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.578 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.218 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.322 s0.359 s+0.037 s3.37 MiB3.46 MiB+ 95.24 KiB
/wp-admin/edit.php0.183 s0.209 s+0.026 s3.4 MiB3.49 MiB+ 94.53 KiB
/wp-admin/post-new.php0.797 s0.897 s+0.100 s5.68 MiB5.79 MiB+ 110.8 KiB
/wp-admin/upload.php0.384 s0.300 s-0.084 s3.25 MiB3.35 MiB+ 102.84 KiB
/wp-admin/options-writing.php0.232 s0.150 s-0.082 s3.24 MiB3.33 MiB+ 85.96 KiB
/wp-admin/media-new.php0.238 s0.154 s-0.084 s3.23 MiB3.33 MiB+ 103.02 KiB
/wp-admin/edit-tags.php?taxonomy=category0.195 s0.183 s-0.012 s3.27 MiB3.36 MiB+ 95.19 KiB
/wp-admin/post-new.php?post_type=page0.650 s1.034 s+0.384 s5.68 MiB5.78 MiB+ 108 KiB
/wp-admin/options-discussion.php0.470 s0.302 s-0.168 s3.22 MiB3.32 MiB+ 102.59 KiB
/wp-admin/edit-comments.php0.218 s0.201 s-0.017 s3.27 MiB3.36 MiB+ 94.09 KiB
/0.267 s0.213 s-0.054 s3.4 MiB3.4 MiB+ 5.48 KiB
Average 0.360 s0.364 s+0.004 s3.73 MiB3.82 MiB+ 90.7 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

[14-Apr-2022 04:01:50 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/triggerfish-bytbil-accesspaket/filter-fields/class-type.php on line 14
[14-Apr-2022 04:01:51 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/triggerfish-bytbil-accesspaket/filter-fields/class-type.php on line 14
[14-Apr-2022 04:01:52 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/triggerfish-bytbil-accesspaket/filter-fields/class-type.php on line 14
[14-Apr-2022 04:01:53 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/triggerfish-bytbil-accesspaket/filter-fields/class-type.php on line 14
[14-Apr-2022 04:01:54 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/triggerfish-bytbil-accesspaket/filter-fields/class-type.php on line 14
[14-Apr-2022 04:01:54 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/triggerfish-bytbil-accesspaket/filter-fields/class-type.php on line 14
[14-Apr-2022 04:01:55 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/triggerfish-bytbil-accesspaket/filter-fields/class-type.php on line 14
[14-Apr-2022 04:01:57 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 5775
[14-Apr-2022 04:01:57 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 5775
[14-Apr-2022 04:01:57 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 5775
[14-Apr-2022 04:01:57 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 5775
[14-Apr-2022 04:01:57 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 5775
[14-Apr-2022 04:01:57 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 5775
[14-Apr-2022 04:01:57 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 5775
[14-Apr-2022 04:01:59 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
[14-Apr-2022 04:01:59 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
[14-Apr-2022 04:01:59 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
[14-Apr-2022 04:01:59 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
[14-Apr-2022 04:01:59 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
[14-Apr-2022 04:01:59 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
[14-Apr-2022 04:01:59 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
[14-Apr-2022 04:01:59 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
[14-Apr-2022 04:02:01 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 5775
[14-Apr-2022 04:02:01 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 5775
[14-Apr-2022 04:02:01 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 5775
[14-Apr-2022 04:02:01 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 5775
[14-Apr-2022 04:02:01 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 5775
[14-Apr-2022 04:02:01 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 5775
[14-Apr-2022 04:02:01 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 5775
[14-Apr-2022 04:02:02 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
[14-Apr-2022 04:02:02 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
[14-Apr-2022 04:02:02 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
[14-Apr-2022 04:02:02 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
[14-Apr-2022 04:02:02 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
[14-Apr-2022 04:02:02 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
[14-Apr-2022 04:02:02 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
[14-Apr-2022 04:02:02 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