Auto Bulb Finder for WordPress 2.6.6

Does "Auto Bulb Finder for WP & WC - Year/Make/Model" work with WordPress 6.2 and PHP 8.1.12? A smoke test was performed on .

Summary

Errors
22PHP notices
2PHP deprecation warnings
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

Memory usage: 92.66 KiB
The average PHP memory usage increased by this amount after activating by the plugin.

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

Environment
WordPress version6.2
PHP version8.1.12
MySQL version10.6.10
PHP memory limit512M
Plugin Info
Last updated
Active installs 20+
WordPress.org page https://wordpress.org/plugins/auto-bulb-finder-for-wp-wc/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 6

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=auto-bulb-finder-for-wp-wc%2Fauto-bulb-finder.php&plugin_status=all&paged=1&s&_wpnonce=8973ca4d7f
Aspect after-activation
HTTP status 200
Load time 0.283 s
Memory usage 3.1 MiB
JS errors None
Resource errors None

Auto Bulb

Page screenshot: Auto Bulb
URL /wp-admin/admin.php?page=auto-bulb-finder-for-wp-wc
Aspect menu-item
HTTP status 200
Load time 0.742 s
Memory usage 3.16 MiB
JS errors None
Resource errors None

Auto Bulb → Adaptions

Page screenshot: Auto Bulb → Adaptions
URL /wp-admin/admin.php?page=auto-bulb-finder-adaption
Aspect menu-item
HTTP status 200
Load time 0.260 s
Memory usage 3.12 MiB
JS errors None
Resource errors None

Auto Bulb → Vehicles

Page screenshot: Auto Bulb → Vehicles
URL /wp-admin/admin.php?page=auto-bulb-finder-vehicle
Aspect menu-item
HTTP status 200
Load time 0.134 s
Memory usage 3.11 MiB
JS errors None
Resource errors None

Auto Bulb → Statistics

Page screenshot: Auto Bulb → Statistics
URL /wp-admin/admin.php?page=auto-bulb-finder-statistic
Aspect menu-item
HTTP status 200
Load time 0.134 s
Memory usage 3.08 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.273 s
Memory usage 3.03 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.281 s0.449 s+0.168 s3.07 MiB3.17 MiB+ 100.46 KiB
/wp-admin/edit.php0.185 s0.188 s+0.003 s3.1 MiB3.18 MiB+ 83.77 KiB
/wp-admin/post-new.php0.744 s0.873 s+0.129 s5.02 MiB5.2 MiB+ 183.33 KiB
/wp-admin/upload.php0.512 s0.361 s-0.151 s3.02 MiB3.11 MiB+ 98.16 KiB
/wp-admin/options-writing.php0.146 s0.141 s-0.005 s3.01 MiB3.05 MiB+ 36.91 KiB
/wp-admin/media-new.php0.271 s0.208 s-0.063 s2.99 MiB3.05 MiB+ 62.34 KiB
/wp-admin/edit-tags.php?taxonomy=category0.163 s0.173 s+0.010 s3.01 MiB3.09 MiB+ 83.52 KiB
/wp-admin/post-new.php?post_type=page0.598 s1.098 s+0.500 s5.01 MiB5.19 MiB+ 177.98 KiB
/wp-admin/options-discussion.php0.195 s0.267 s+0.072 s3 MiB3.06 MiB+ 66.65 KiB
/wp-admin/edit-comments.php0.191 s0.213 s+0.022 s3.03 MiB3.09 MiB+ 66.19 KiB
/0.291 s0.208 s-0.083 s2.97 MiB3.03 MiB+ 59.94 KiB
Average 0.325 s0.380 s+0.055 s3.38 MiB3.47 MiB+ 92.66 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
PHP85.2%4,01860828
JavaScript7.8%36972
CSS6.9%32522
SVG0.1%303
Total 4,715 617 35

PHP Code Analysis | More results »

Lines of code 2,645
Total complexity 466
Median class complexity 27.0
Median method complexity 2.0
Most complex class ABFinder\Helper\ABFinder_Database
Most complex function ABFinder\Helper\ABFinder_Database::query_vehicles()
Classes 11
Methods 115
Functions 32

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.

Database Tables 3

Options wp_options 3

PHP Error Log 24 lines

[10-Apr-2023 18:44:55 UTC] PHP Deprecated:  Optional parameter $current_page declared before required parameter $search_val is implicitly treated as a required parameter in /wp-content/plugins/auto-bulb-finder-for-wp-wc/templates/admin/adaptions/class-abfinder-adaptions-list.php on line 120
[10-Apr-2023 18:44:56 UTC] PHP Deprecated:  Optional parameter $current_page declared before required parameter $search_val is implicitly treated as a required parameter in /wp-content/plugins/auto-bulb-finder-for-wp-wc/templates/admin/vehicles/class-abfinder-vehicles-list.php on line 119
[10-Apr-2023 18:44:57 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>jquery</code> handle. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 5865
[10-Apr-2023 18:44:59 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>jquery</code> handle. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 5865
[10-Apr-2023 18:45:00 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>jquery</code> handle. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 5865
[10-Apr-2023 18:45:00 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>jquery</code> handle. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 5865
[10-Apr-2023 18:45:00 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>jquery</code> handle. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 5865
[10-Apr-2023 18:45:00 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>jquery</code> handle. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 5865
[10-Apr-2023 18:45:00 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>jquery</code> handle. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 5865
[10-Apr-2023 18:45:00 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>jquery</code> handle. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 5865
[10-Apr-2023 18:45:00 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>jquery</code> handle. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 5865
[10-Apr-2023 18:45:01 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>jquery</code> handle. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 5865
[10-Apr-2023 18:45:01 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>jquery</code> handle. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 5865
[10-Apr-2023 18:45:02 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>jquery</code> handle. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 5865
[10-Apr-2023 18:45:04 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>jquery</code> handle. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 5865
[10-Apr-2023 18:45:04 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>jquery</code> handle. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 5865
[10-Apr-2023 18:45:04 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>jquery</code> handle. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 5865
[10-Apr-2023 18:45:04 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>jquery</code> handle. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 5865
[10-Apr-2023 18:45:04 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>jquery</code> handle. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 5865
[10-Apr-2023 18:45:04 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>jquery</code> handle. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 5865
[10-Apr-2023 18:45:04 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>jquery</code> handle. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 5865
[10-Apr-2023 18:45:04 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>jquery</code> handle. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 5865
[10-Apr-2023 18:45:05 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>jquery</code> handle. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 5865
[10-Apr-2023 18:45:05 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>jquery</code> handle. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 5865
See also: All tests for this plugin, How to Hide Auto Bulb Finder for WP & WC - Year/Make/Model Admin Menus