Does Impresee CreativeSearch work with WordPress 5.5.1 and PHP 7.4.8? A smoke test was performed on .
6 | PHP notices |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 133.66 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.030 seconds
The average page load time increased by this amount after activating the plugin.
WordPress version | 5.5.1 |
---|---|
PHP version | 7.4.8 |
MySQL version | 8.0.21 |
PHP memory limit | 256M |
Last updated | |
---|---|
Active installs | <10 |
WordPress.org page | https://wordpress.org/plugins/visual-search/ |
Badges |
|
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=visual-search%2Fimpresee-creativesearch.php&plugin_status=all&paged=1&s&_wpnonce=a8c6bf7e4c |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.825 s |
Memory usage | 2.78 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.261 s |
Memory usage | 2.65 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.492 s | 0.357 s | -0.135 s | 2.75 MiB | 2.89 MiB | + 136.03 KiB |
/wp-admin/edit.php | 0.252 s | 0.276 s | +0.024 s | 2.8 MiB | 2.93 MiB | + 135.35 KiB |
/wp-admin/post-new.php | 1.814 s | 2.922 s | +1.108 s | 4.54 MiB | 4.71 MiB | + 169.73 KiB |
/wp-admin/upload.php | 0.746 s | 0.468 s | -0.278 s | 2.63 MiB | 2.76 MiB | + 134.59 KiB |
/wp-admin/options-writing.php | 0.187 s | 0.193 s | +0.006 s | 2.64 MiB | 2.74 MiB | + 102.56 KiB |
/wp-admin/media-new.php | 0.215 s | 0.192 s | -0.023 s | 2.6 MiB | 2.74 MiB | + 134.76 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.234 s | 0.201 s | -0.033 s | 2.64 MiB | 2.78 MiB | + 135.66 KiB |
/wp-admin/post-new.php?post_type=page | 1.657 s | 1.581 s | -0.076 s | 4.53 MiB | 4.69 MiB | + 161.31 KiB |
/wp-admin/options-discussion.php | 0.411 s | 0.282 s | -0.129 s | 2.61 MiB | 2.74 MiB | + 135.07 KiB |
/wp-admin/edit-comments.php | 0.233 s | 0.249 s | +0.016 s | 2.65 MiB | 2.78 MiB | + 134.57 KiB |
/ | 0.443 s | 0.288 s | -0.155 s | 2.56 MiB | 2.65 MiB | + 90.61 KiB |
Average | 0.608 s | 0.637 s | +0.030 s | 3 MiB | 3.13 MiB | + 133.66 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.
wp_options
2[17-Sep-2020 13:40:20 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>impresee/v1/catalog-status/(?P<owner>[a-zA-Z0-9-]+)</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
[17-Sep-2020 13:40:20 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>impresee/v1/catalog/(?P<id>[a-zA-Z0-9-]+)</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
[17-Sep-2020 13:40:20 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>impresee/v1/register-impresee/(?P<verification_code>[a-zA-Z0-9-]+)</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
[17-Sep-2020 13:40:24 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>impresee/v1/catalog-status/(?P<owner>[a-zA-Z0-9-]+)</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
[17-Sep-2020 13:40:24 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>impresee/v1/catalog/(?P<id>[a-zA-Z0-9-]+)</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
[17-Sep-2020 13:40:24 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>impresee/v1/register-impresee/(?P<verification_code>[a-zA-Z0-9-]+)</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