Does adwised work with WordPress 5.5 and PHP 7.2.16? A smoke test was performed on .
7 | PHP notices |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 21.43 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.
WordPress version | 5.5 |
---|---|
PHP version | 7.2.16 |
MySQL version | 8.0.15 |
PHP memory limit | 256M |
Last updated | |
---|---|
Active installs | 100+ |
WordPress.org page | https://wordpress.org/plugins/adwised/ |
Badges |
|
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=adwised%2Fadwised.php&plugin_status=all&paged=1&s&_wpnonce=e19f94619a |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.365 s |
Memory usage | 4.04 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=adwised |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.295 s |
Memory usage | 3.97 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.232 s |
Memory usage | 3.66 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.436 s | 0.325 s | -0.111 s | 3.96 MiB | 4 MiB | + 36.83 KiB |
/wp-admin/edit.php | 0.222 s | 0.341 s | +0.119 s | 3.99 MiB | 4.02 MiB | + 31.33 KiB |
/wp-admin/post-new.php | 1.489 s | 1.844 s | +0.355 s | 5.81 MiB | 5.87 MiB | + 61.42 KiB |
/wp-admin/upload.php | 0.880 s | 0.449 s | -0.431 s | 3.82 MiB | 3.85 MiB | + 30.2 KiB |
/wp-admin/options-writing.php | 0.175 s | 0.150 s | -0.025 s | 3.9 MiB | 3.84 MiB | - 63.24 KiB |
/wp-admin/media-new.php | 0.201 s | 0.180 s | -0.021 s | 3.8 MiB | 3.83 MiB | + 30.37 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.190 s | 0.173 s | -0.017 s | 3.91 MiB | 3.94 MiB | + 31.27 KiB |
/wp-admin/post-new.php?post_type=page | 1.396 s | 1.336 s | -0.060 s | 5.8 MiB | 5.86 MiB | + 54.6 KiB |
/wp-admin/options-discussion.php | 0.313 s | 0.548 s | +0.235 s | 3.81 MiB | 3.84 MiB | + 30.68 KiB |
/wp-admin/edit-comments.php | 0.224 s | 0.209 s | -0.015 s | 3.91 MiB | 3.94 MiB | + 30.22 KiB |
/ | 0.352 s | 0.194 s | -0.158 s | 3.69 MiB | 3.66 MiB | - 37.93 KiB |
Average | 0.534 s | 0.523 s | -0.012 s | 4.22 MiB | 4.24 MiB | + 21.43 KiB |
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.
No new entries found.
[18-Aug-2020 14:24:16 UTC] PHP Notice: Trying to get property 'pop_url' of non-object in /wp-content/plugins/adwised/views/settings.php on line 122
[18-Aug-2020 14:24:17 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>adwisedpopup/v1/setconfig</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 5225
[18-Aug-2020 14:24:17 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>adwisedpopup/v1/getversion</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 5225
[18-Aug-2020 14:24:17 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>adwisedpopup/v1/getconfig</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 5225
[18-Aug-2020 14:24:21 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>adwisedpopup/v1/setconfig</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 5225
[18-Aug-2020 14:24:21 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>adwisedpopup/v1/getversion</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 5225
[18-Aug-2020 14:24:21 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>adwisedpopup/v1/getconfig</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 5225