Collapsing Archives 2.1.1
Does Collapsing Archives work with WordPress 5.9.1 and PHP 7.4.8? A smoke test was performed on .
Summary
Errors
| 36 | PHP notices |
| No JavaScript exceptions | |
| All test pages loaded successfully | |
| No resource errors |
Performance
Memory usage: 8.96 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.9.1 |
|---|---|
| PHP version | 7.4.8 |
| MySQL version | 8.0.21 |
| PHP memory limit | 256M |
Plugin Info
| Last updated | |
|---|---|
| Active installs | 3,000+ |
| WordPress.org page | https://wordpress.org/plugins/collapsing-archives/ |
| Badges |
|
Pages 3
Plugins ‹ Test site — WordPress
| URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
|---|---|
| Requested URL | /wp-admin/plugins.php?action=activate&plugin=collapsing-archives%2FcollapsArch.php&plugin_status=all&paged=1&s&_wpnonce=65550fe5b7 |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.428 s |
| Memory usage | 3.28 MiB |
| JS errors | None |
| Resource errors | None |
Test site – Just another WordPress site
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.210 s |
| Memory usage | 3.36 MiB |
| JS errors | None |
| Resource errors | None |
Widgets ‹ Test site — WordPress
| URL | /wp-admin/widgets.php |
|---|---|
| Aspect | new-sidebar-widgets |
| HTTP status | 200 |
| Load time | 1.668 s |
| Memory usage | 5.19 MiB |
| JS errors | None |
| Resource errors | None |
Benchmark
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.343 s | 0.283 s | -0.060 s | 3.37 MiB | 3.38 MiB | + 10.38 KiB |
| /wp-admin/edit.php | 0.176 s | 0.183 s | +0.007 s | 3.4 MiB | 3.41 MiB | + 10.38 KiB |
| /wp-admin/post-new.php | 1.016 s | 1.175 s | +0.159 s | 6.15 MiB | 6.16 MiB | + 14.73 KiB |
| /wp-admin/upload.php | 0.379 s | 0.386 s | +0.007 s | 3.25 MiB | 3.26 MiB | + 9.24 KiB |
| /wp-admin/options-writing.php | 0.322 s | 0.136 s | -0.186 s | 3.24 MiB | 3.24 MiB | - 6.91 KiB |
| /wp-admin/media-new.php | 0.244 s | 0.201 s | -0.043 s | 3.23 MiB | 3.24 MiB | + 9.41 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.226 s | 0.187 s | -0.039 s | 3.27 MiB | 3.28 MiB | + 10.32 KiB |
| /wp-admin/post-new.php?post_type=page | 0.942 s | 1.093 s | +0.151 s | 6.15 MiB | 6.16 MiB | + 10.32 KiB |
| /wp-admin/options-discussion.php | 0.238 s | 0.261 s | +0.023 s | 3.22 MiB | 3.23 MiB | + 9.73 KiB |
| /wp-admin/edit-comments.php | 0.203 s | 0.220 s | +0.017 s | 3.27 MiB | 3.28 MiB | + 9.23 KiB |
| / | 0.251 s | 0.204 s | -0.047 s | 3.35 MiB | 3.36 MiB | + 11.71 KiB |
| Average | 0.395 s | 0.394 s | -0.001 s | 3.81 MiB | 3.82 MiB | + 8.96 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.
| Language | % | Lines of code | Comment lines | Files | |
|---|---|---|---|---|---|
| PHP | 83.3% | 986 | 85 | 9 | |
| PO File | 9.0% | 107 | 46 | 1 | |
| JavaScript | 6.5% | 77 | 4 | 1 | |
| Bourne Again Shell | 1.1% | 13 | 1 | 1 | |
| Total | 1,183 | 136 | 12 | ||
PHP Code Analysis | More results »
| Lines of code | 533 |
|---|---|
| Total complexity | 152 |
| Median class complexity | 10.5 |
| Median method complexity | 2.0 |
| Most complex class | collapsArch |
| Most complex function | list_archives() |
| Classes | 2 |
|---|---|
| Methods | 8 |
| Functions | 4 |
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.
Options wp_options 2
- collapsArchVersion
- widget_collapsarch
Sidebar Widgets 1
| ID | Name |
|---|---|
| collapsarch | Collapsing Archives |
PHP Error Log 36 lines
[10-Mar-2022 12:52:01 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:04 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:04 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:04 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:04 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:04 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:04 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:04 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:04 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:04 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:07 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:07 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:08 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:08 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:08 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:08 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:08 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:08 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:08 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:09 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:11 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:11 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:12 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:12 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:12 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:12 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:12 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:12 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:13 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:13 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:13 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:13 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:13 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:13 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:13 UTC] PHP Notice: 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/support/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 5768
[10-Mar-2022 12:52:14 UTC] PHP Notice: 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/support/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 5768
See also: All tests for this plugin