Bytbil Accesspaket 1.9.7

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: 73.94 KiB
The average PHP memory usage increased by this amount after activating by the plugin.

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

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=e521eac81c
Aspect after-activation
HTTP status 200
Load time 0.314 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.572 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.380 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.375 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.403 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.380 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.339 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.351 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.202 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.355 s0.556 s+0.201 s3.08 MiB3.15 MiB+ 73.4 KiB
/wp-admin/edit.php0.178 s0.210 s+0.032 s3.11 MiB3.25 MiB+ 137.4 KiB
/wp-admin/post-new.php1.113 s1.486 s+0.373 s5.27 MiB5.36 MiB+ 93.87 KiB
/wp-admin/upload.php0.632 s0.468 s-0.164 s3.03 MiB3.1 MiB+ 73 KiB
/wp-admin/options-writing.php0.193 s0.260 s+0.067 s3.02 MiB3.08 MiB+ 56.24 KiB
/wp-admin/media-new.php0.274 s0.224 s-0.050 s3.01 MiB3.08 MiB+ 73.17 KiB
/wp-admin/edit-tags.php?taxonomy=category0.198 s0.218 s+0.020 s3.04 MiB3.11 MiB+ 73.34 KiB
/wp-admin/post-new.php?post_type=page1.360 s2.266 s+0.906 s5.26 MiB5.35 MiB+ 95.07 KiB
/wp-admin/options-discussion.php0.332 s0.305 s-0.027 s3 MiB3.07 MiB+ 72.75 KiB
/wp-admin/edit-comments.php0.226 s0.216 s-0.010 s3.04 MiB3.11 MiB+ 72.25 KiB
/0.288 s0.250 s-0.038 s2.96 MiB2.95 MiB- 7.14 KiB
Average 0.468 s0.587 s+0.119 s3.44 MiB3.51 MiB+ 73.94 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,9392053
PO File8.1%2911571
JavaScript4.9%177216
SVG3.4%1231111
JSON1.4%5102
CSS0.1%222
HTML0.0%101
Total 3,584 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

[17-Sep-2021 00:02:06 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 52
[17-Sep-2021 00:02:06 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
[17-Sep-2021 00:02:07 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 52
[17-Sep-2021 00:02:07 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
[17-Sep-2021 00:02:08 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 52
[17-Sep-2021 00:02:08 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
[17-Sep-2021 00:02:09 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 52
[17-Sep-2021 00:02:09 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
[17-Sep-2021 00:02:10 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 52
[17-Sep-2021 00:02:10 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
[17-Sep-2021 00:02:11 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 52
[17-Sep-2021 00:02:11 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
[17-Sep-2021 00:02:11 UTC] PHP Notice:  Undefined variable: options in /wp-content/plugins/triggerfish-bytbil-accesspaket/templates/tabs/theming-settings-fields.php on line 52
[17-Sep-2021 00:02:11 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
[17-Sep-2021 00:02:13 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
[17-Sep-2021 00:02:13 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
[17-Sep-2021 00:02:13 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
[17-Sep-2021 00:02:13 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
[17-Sep-2021 00:02:13 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
[17-Sep-2021 00:02:13 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
[17-Sep-2021 00:02:13 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
[17-Sep-2021 00:02:13 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
[17-Sep-2021 00:02:13 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
[17-Sep-2021 00:02:13 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
[17-Sep-2021 00:02:17 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
[17-Sep-2021 00:02:17 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
[17-Sep-2021 00:02:17 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
[17-Sep-2021 00:02:17 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
[17-Sep-2021 00:02:17 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
[17-Sep-2021 00:02:17 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
[17-Sep-2021 00:02:17 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
[17-Sep-2021 00:02:17 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
[17-Sep-2021 00:02:17 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
[17-Sep-2021 00:02:17 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