Bytbil Accesspaket 1.9.2

Does Bytbil Accesspaket work with WordPress 5.8 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: 78.27 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
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=f1ee69edcc
Aspect after-activation
HTTP status 200
Load time 0.233 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.528 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.362 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.321 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.345 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.437 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.328 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.308 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.199 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.321 s0.327 s+0.006 s3.08 MiB3.15 MiB+ 73.4 KiB
/wp-admin/edit.php0.170 s0.347 s+0.177 s3.11 MiB3.25 MiB+ 137.4 KiB
/wp-admin/post-new.php0.827 s0.961 s+0.134 s5.27 MiB5.36 MiB+ 93.87 KiB
/wp-admin/upload.php0.587 s0.433 s-0.154 s3.03 MiB3.1 MiB+ 73 KiB
/wp-admin/options-writing.php0.172 s0.148 s-0.024 s3.02 MiB3.08 MiB+ 56.24 KiB
/wp-admin/media-new.php0.248 s0.169 s-0.079 s3.01 MiB3.08 MiB+ 73.17 KiB
/wp-admin/edit-tags.php?taxonomy=category0.183 s0.188 s+0.005 s3.04 MiB3.11 MiB+ 73.34 KiB
/wp-admin/post-new.php?post_type=page0.987 s0.762 s-0.225 s5.26 MiB5.35 MiB+ 95.07 KiB
/wp-admin/options-discussion.php0.225 s0.225 s+0.000 s3 MiB3.07 MiB+ 72.75 KiB
/wp-admin/edit-comments.php0.198 s0.194 s-0.004 s3.04 MiB3.11 MiB+ 72.25 KiB
/0.346 s0.205 s-0.141 s2.91 MiB2.95 MiB+ 40.52 KiB
Average 0.388 s0.360 s-0.028 s3.43 MiB3.51 MiB+ 78.27 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
PO File
Language % Lines of code Comment lines Files
PHP82.0%2,9362053
PO File8.1%2911571
JavaScript4.9%177216
SVG3.4%1231111
JSON1.4%5102
CSS0.1%222
HTML0.0%101
Total 3,581 211 76

PHP Code Analysis | More results »

Lines of code 1,961
Total complexity 226
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 5

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

[06-Sep-2021 11:23:57 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 52
[06-Sep-2021 11:23:57 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 52
[06-Sep-2021 11:23:58 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 52
[06-Sep-2021 11:23:58 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 52
[06-Sep-2021 11:23:59 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 52
[06-Sep-2021 11:23:59 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 52
[06-Sep-2021 11:24:00 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 52
[06-Sep-2021 11:24:00 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 52
[06-Sep-2021 11:24:00 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 52
[06-Sep-2021 11:24:00 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 52
[06-Sep-2021 11:24:01 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 52
[06-Sep-2021 11:24:01 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 52
[06-Sep-2021 11:24:02 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 52
[06-Sep-2021 11:24:02 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 52
[06-Sep-2021 11:24:04 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 5535
[06-Sep-2021 11:24:04 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 5535
[06-Sep-2021 11:24:04 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 5535
[06-Sep-2021 11:24:04 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 5535
[06-Sep-2021 11:24:04 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 5535
[06-Sep-2021 11:24:04 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 5535
[06-Sep-2021 11:24:04 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
[06-Sep-2021 11:24:04 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
[06-Sep-2021 11:24:04 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
[06-Sep-2021 11:24:04 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
[06-Sep-2021 11:24:07 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 5535
[06-Sep-2021 11:24:07 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 5535
[06-Sep-2021 11:24:07 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 5535
[06-Sep-2021 11:24:07 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 5535
[06-Sep-2021 11:24:07 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 5535
[06-Sep-2021 11:24:07 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 5535
[06-Sep-2021 11:24:07 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
[06-Sep-2021 11:24:07 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
[06-Sep-2021 11:24:07 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
[06-Sep-2021 11:24:07 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