Bytbil Accesspaket 2.1.9

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

Summary

Errors
8PHP warnings
28PHP notices
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

Memory usage: 89.59 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.8.2
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=c974cc519f
Aspect after-activation
HTTP status 200
Load time 0.472 s
Memory usage 3.2 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.670 s
Memory usage 3.18 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.388 s
Memory usage 3.14 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.352 s
Memory usage 3.14 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.14 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.361 s
Memory usage 3.14 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.371 s
Memory usage 3.14 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.347 s
Memory usage 3.14 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.250 s
Memory usage 2.95 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.304 s0.333 s+0.029 s3.08 MiB3.17 MiB+ 91.09 KiB
/wp-admin/edit.php0.181 s0.202 s+0.021 s3.11 MiB3.26 MiB+ 155.09 KiB
/wp-admin/post-new.php0.779 s0.864 s+0.085 s5.27 MiB5.37 MiB+ 107.27 KiB
/wp-admin/upload.php0.524 s0.302 s-0.222 s3.03 MiB3.12 MiB+ 90.7 KiB
/wp-admin/options-writing.php0.250 s0.150 s-0.100 s3.02 MiB3.1 MiB+ 73.94 KiB
/wp-admin/media-new.php0.339 s0.345 s+0.006 s3.01 MiB3.1 MiB+ 90.87 KiB
/wp-admin/edit-tags.php?taxonomy=category0.183 s0.234 s+0.051 s3.04 MiB3.13 MiB+ 91.04 KiB
/wp-admin/post-new.php?post_type=page0.600 s0.888 s+0.288 s5.26 MiB5.36 MiB+ 108.48 KiB
/wp-admin/options-discussion.php0.255 s0.232 s-0.023 s3 MiB3.09 MiB+ 90.45 KiB
/wp-admin/edit-comments.php0.212 s0.209 s-0.003 s3.04 MiB3.13 MiB+ 89.95 KiB
/0.419 s0.225 s-0.194 s2.96 MiB2.95 MiB- 3.38 KiB
Average 0.368 s0.362 s-0.006 s3.44 MiB3.53 MiB+ 89.59 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
PHP81.8%3,1981753
PO File7.4%2911571
JavaScript6.2%242216
SVG3.1%1231111
JSON1.3%5102
CSS0.1%222
HTML0.0%101
Total 3,908 208 76

PHP Code Analysis | More results »

Lines of code 2,289
Total complexity 248
Median class complexity 2.0
Median method complexity 1.0
Most complex class TF\AccessPackage\Metabox
Most complex function TF\AccessPackage\Scripts::loadScripts()
Classes 35
Methods 95
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 36 lines

[07-Dec-2021 13:52:18 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 47
[07-Dec-2021 13:52:18 UTC] PHP Notice:  Trying to access array offset on value of type null in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 47
[07-Dec-2021 13:52:20 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 47
[07-Dec-2021 13:52:20 UTC] PHP Notice:  Trying to access array offset on value of type null in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 47
[07-Dec-2021 13:52:21 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 47
[07-Dec-2021 13:52:21 UTC] PHP Notice:  Trying to access array offset on value of type null in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 47
[07-Dec-2021 13:52:21 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 47
[07-Dec-2021 13:52:21 UTC] PHP Notice:  Trying to access array offset on value of type null in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 47
[07-Dec-2021 13:52:22 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 47
[07-Dec-2021 13:52:22 UTC] PHP Notice:  Trying to access array offset on value of type null in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 47
[07-Dec-2021 13:52:23 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 47
[07-Dec-2021 13:52:23 UTC] PHP Notice:  Trying to access array offset on value of type null in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 47
[07-Dec-2021 13:52:24 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 47
[07-Dec-2021 13:52:24 UTC] PHP Notice:  Trying to access array offset on value of type null in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 47
[07-Dec-2021 13:52:26 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 5663
[07-Dec-2021 13:52:26 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 5663
[07-Dec-2021 13:52:26 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 5663
[07-Dec-2021 13:52:26 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 5663
[07-Dec-2021 13:52:26 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 5663
[07-Dec-2021 13:52:26 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 5663
[07-Dec-2021 13:52:26 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 5663
[07-Dec-2021 13:52:26 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 1436
[07-Dec-2021 13:52:26 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 1436
[07-Dec-2021 13:52:26 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 1436
[07-Dec-2021 13:52:26 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 1436
[07-Dec-2021 13:52:29 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 5663
[07-Dec-2021 13:52:29 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 5663
[07-Dec-2021 13:52:29 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 5663
[07-Dec-2021 13:52:29 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 5663
[07-Dec-2021 13:52:29 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 5663
[07-Dec-2021 13:52:29 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 5663
[07-Dec-2021 13:52:29 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 5663
[07-Dec-2021 13:52:29 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 1436
[07-Dec-2021 13:52:29 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 1436
[07-Dec-2021 13:52:29 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 1436
[07-Dec-2021 13:52:29 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 1436
See also: All tests for this plugin, How to Hide the "Access package" Admin Menu