Bytbil Accesspaket 2.1.0

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

Summary

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

Memory usage: 83.37 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.1
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=84b58318d7
Aspect after-activation
HTTP status 200
Load time 0.548 s
Memory usage 3.12 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.734 s
Memory usage 3.17 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.394 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.374 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.362 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.377 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.379 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.355 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.225 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.345 s+0.041 s3.08 MiB3.16 MiB+ 78.63 KiB
/wp-admin/edit.php0.193 s0.219 s+0.026 s3.11 MiB3.25 MiB+ 142.63 KiB
/wp-admin/post-new.php0.774 s0.868 s+0.094 s5.27 MiB5.36 MiB+ 99.09 KiB
/wp-admin/upload.php0.394 s0.293 s-0.101 s3.03 MiB3.11 MiB+ 78.23 KiB
/wp-admin/options-writing.php0.150 s0.161 s+0.011 s3.02 MiB3.08 MiB+ 61.47 KiB
/wp-admin/media-new.php0.464 s0.340 s-0.124 s3.01 MiB3.08 MiB+ 78.4 KiB
/wp-admin/edit-tags.php?taxonomy=category0.183 s0.233 s+0.050 s3.04 MiB3.11 MiB+ 78.57 KiB
/wp-admin/post-new.php?post_type=page0.627 s0.777 s+0.150 s5.26 MiB5.36 MiB+ 100.3 KiB
/wp-admin/options-discussion.php0.270 s0.241 s-0.029 s3 MiB3.08 MiB+ 77.98 KiB
/wp-admin/edit-comments.php0.214 s0.211 s-0.003 s3.04 MiB3.12 MiB+ 77.48 KiB
/0.299 s0.238 s-0.061 s2.91 MiB2.95 MiB+ 44.28 KiB
Average 0.352 s0.357 s+0.005 s3.43 MiB3.52 MiB+ 83.37 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.5%3,0422053
PO File7.9%2911571
JavaScript4.8%177216
SVG3.3%1231111
JSON1.4%5102
CSS0.1%222
HTML0.0%101
Total 3,687 211 76

PHP Code Analysis | More results »

Lines of code 2,219
Total complexity 235
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 92
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 34 lines

[14-Oct-2021 14:39:47 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 47
[14-Oct-2021 14:39:47 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
[14-Oct-2021 14:39:49 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 47
[14-Oct-2021 14:39:49 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
[14-Oct-2021 14:39:49 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 47
[14-Oct-2021 14:39:49 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
[14-Oct-2021 14:39:50 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 47
[14-Oct-2021 14:39:50 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
[14-Oct-2021 14:39:51 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 47
[14-Oct-2021 14:39:51 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
[14-Oct-2021 14:39:52 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 47
[14-Oct-2021 14:39:52 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
[14-Oct-2021 14:39:53 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 47
[14-Oct-2021 14:39:53 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
[14-Oct-2021 14:39:55 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
[14-Oct-2021 14:39:55 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
[14-Oct-2021 14:39:55 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
[14-Oct-2021 14:39:55 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
[14-Oct-2021 14:39:55 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
[14-Oct-2021 14:39:55 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
[14-Oct-2021 14:39:55 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
[14-Oct-2021 14:39:55 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
[14-Oct-2021 14:39:55 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
[14-Oct-2021 14:39:55 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
[14-Oct-2021 14:39:58 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
[14-Oct-2021 14:39:58 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
[14-Oct-2021 14:39:58 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
[14-Oct-2021 14:39:58 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
[14-Oct-2021 14:39:58 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
[14-Oct-2021 14:39:58 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
[14-Oct-2021 14:39:58 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
[14-Oct-2021 14:39:58 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
[14-Oct-2021 14:39:58 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
[14-Oct-2021 14:39:58 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