Report - Bytbil Accesspaket 2.3.2

Does Bytbil Accesspaket work with WordPress 5.8.3 and PHP 7.4.8? A smoke test was performed on 2022-01-24 16:42:28 UTC.

Summary

Errors

8	PHP warnings
14	PHP notices
	No JavaScript exceptions
	All test pages loaded successfully
	No resource errors

Performance

Memory usage: 96.18 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 version	5.8.3
PHP version	7.4.8
MySQL version	8.0.21
PHP memory limit	256M

Plugin Info

Last updated	2025-03-10T15:55:00+00:00
Active installs	<10
WordPress.org page	https://wordpress.org/plugins/triggerfish-bytbil-accesspaket/
Badges	Get badge code

Pages 9

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=1b387c8e1f
Aspect	after-activation
HTTP status	200
Load time	0.560 s
Memory usage	3.2 MiB
JS errors	None
Resource errors	None

Settings → Access package

URL	/wp-admin/options-general.php?page=access-package.php
Aspect	menu-item
HTTP status	200
Load time	0.618 s
Memory usage	3.18 MiB
JS errors	None
Resource errors	None

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.390 s
Memory usage	3.15 MiB
JS errors	None
Resource errors	None

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.361 s
Memory usage	3.15 MiB
JS errors	None
Resource errors	None

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.15 MiB
JS errors	None
Resource errors	None

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.372 s
Memory usage	3.15 MiB
JS errors	None
Resource errors	None

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.386 s
Memory usage	3.15 MiB
JS errors	None
Resource errors	None

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.354 s
Memory usage	3.15 MiB
JS errors	None
Resource errors	None

Test site – Just another WordPress site

URL	/
Aspect	front-page
HTTP status	200
Load time	0.212 s
Memory usage	2.95 MiB
JS errors	None
Resource errors	None

Benchmark

URL	Load time			Memory usage
URL	Inactive	Active	Change	Inactive	Active	Change
/wp-admin/index.php	0.293 s	0.314 s	+0.021 s	3.08 MiB	3.17 MiB	+ 93.57 KiB
/wp-admin/edit.php	0.190 s	0.192 s	+0.002 s	3.11 MiB	3.27 MiB	+ 157.57 KiB
/wp-admin/post-new.php	0.741 s	0.814 s	+0.073 s	5.27 MiB	5.37 MiB	+ 109.75 KiB
/wp-admin/upload.php	0.367 s	0.280 s	-0.087 s	3.03 MiB	3.12 MiB	+ 93.17 KiB
/wp-admin/options-writing.php	0.288 s	0.144 s	-0.144 s	3.02 MiB	3.1 MiB	+ 76.41 KiB
/wp-admin/media-new.php	0.345 s	0.348 s	+0.003 s	3.01 MiB	3.1 MiB	+ 93.34 KiB
/wp-admin/edit-tags.php?taxonomy=category	0.173 s	0.215 s	+0.042 s	3.04 MiB	3.13 MiB	+ 93.52 KiB
/wp-admin/post-new.php?post_type=page	0.901 s	0.756 s	-0.145 s	5.26 MiB	5.37 MiB	+ 110.95 KiB
/wp-admin/options-discussion.php	0.217 s	0.210 s	-0.007 s	3 MiB	3.09 MiB	+ 92.92 KiB
/wp-admin/edit-comments.php	0.202 s	0.193 s	-0.009 s	3.04 MiB	3.13 MiB	+ 92.42 KiB
/	0.241 s	0.212 s	-0.029 s	2.91 MiB	2.95 MiB	+ 44.3 KiB
Average	0.360 s	0.334 s	-0.025 s	3.43 MiB	3.53 MiB	+ 96.18 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
	PHP	81.9%	3,364	19	55
	PO File	7.9%	324	186	1
	JavaScript	5.9%	242	21	6
	SVG	3.0%	123	11	11
	JSON	1.2%	51	0	2
	CSS	0.0%	2	2	2
	HTML	0.0%	1	0	1
Total			4,107	239	78

PHP Code Analysis | More results »

Lines of code	2,444
Total complexity	279
Median class complexity	2.0
Median method complexity	1.0
Most complex class	TF\AccessPackage\Metabox
Most complex function	TF\AccessPackage\Scripts::loadScripts()

Classes	37
Methods	100
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_car	Bil

PHP Error Log 22 lines

[24-Jan-2022 16:42:48 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
[24-Jan-2022 16:42:48 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
[24-Jan-2022 16:42:48 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
[24-Jan-2022 16:42:48 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
[24-Jan-2022 16:42:48 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
[24-Jan-2022 16:42:48 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
[24-Jan-2022 16:42:48 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
[24-Jan-2022 16:42:49 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
[24-Jan-2022 16:42:49 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
[24-Jan-2022 16:42:49 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
[24-Jan-2022 16:42:49 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
[24-Jan-2022 16:42:51 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
[24-Jan-2022 16:42:51 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
[24-Jan-2022 16:42:51 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
[24-Jan-2022 16:42:51 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
[24-Jan-2022 16:42:51 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
[24-Jan-2022 16:42:51 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
[24-Jan-2022 16:42:51 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
[24-Jan-2022 16:42:51 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
[24-Jan-2022 16:42:51 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
[24-Jan-2022 16:42:51 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
[24-Jan-2022 16:42:51 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