Does WPL work with WordPress 5.8 and PHP 7.4.8? A smoke test was performed on .
24 | PHP notices |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 244.33 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.035 seconds
The average page load time increased by this amount after activating the plugin.
WordPress version | 5.8 |
---|---|
PHP version | 7.4.8 |
MySQL version | 8.0.21 |
PHP memory limit | 256M |
Last updated | |
---|---|
Active installs | 3,000+ |
WordPress.org page | https://wordpress.org/plugins/real-estate-listing-realtyna-wpl/ |
Badges |
Get badge code |
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=real-estate-listing-realtyna-wpl%2FWPL.php&plugin_status=all&paged=1&s&_wpnonce=e35f499a93 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 28.175 s |
Memory usage | 3.35 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=WPL_main_menu |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 2.262 s |
Memory usage | 3.52 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wpl_admin_data_structure |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.719 s |
Memory usage | 3.58 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wpl_admin_flex |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.341 s |
Memory usage | 3.41 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wpl_admin_locations |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.463 s |
Memory usage | 3.63 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wpl_admin_settings |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.503 s |
Memory usage | 3.44 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wpl_admin_activity |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.326 s |
Memory usage | 3.31 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wpl_admin_notifications |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.207 s |
Memory usage | 3.5 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wpl_admin_user_manager |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.268 s |
Memory usage | 3.47 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wpl_admin_profile |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.222 s |
Memory usage | 4.04 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wpl_admin_add_listing |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.543 s |
Memory usage | 3.49 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wpl_admin_listings |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.504 s |
Memory usage | 3.56 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wpl_addon_idx |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.733 s |
Memory usage | 3.4 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.918 s |
Memory usage | 3.19 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/widgets.php |
---|---|
Aspect | new-sidebar-widgets |
HTTP status | 200 |
Load time | 1.763 s |
Memory usage | 4.69 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.313 s | 0.558 s | +0.245 s | 3.08 MiB | 3.37 MiB | + 290.25 KiB |
/wp-admin/edit.php | 0.185 s | 0.431 s | +0.246 s | 3.11 MiB | 3.4 MiB | + 291.85 KiB |
/wp-admin/post-new.php | 1.761 s | 1.300 s | -0.461 s | 5.27 MiB | 5.5 MiB | + 237.89 KiB |
/wp-admin/upload.php | 0.549 s | 0.606 s | +0.057 s | 3.03 MiB | 3.25 MiB | + 225.83 KiB |
/wp-admin/options-writing.php | 0.279 s | 0.214 s | -0.065 s | 3.02 MiB | 3.23 MiB | + 211.28 KiB |
/wp-admin/media-new.php | 0.255 s | 0.267 s | +0.012 s | 3.01 MiB | 3.23 MiB | + 227.79 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.181 s | 0.239 s | +0.058 s | 3.04 MiB | 3.26 MiB | + 226.51 KiB |
/wp-admin/post-new.php?post_type=page | 1.113 s | 0.889 s | -0.224 s | 5.26 MiB | 5.49 MiB | + 237.48 KiB |
/wp-admin/options-discussion.php | 0.333 s | 0.477 s | +0.144 s | 3 MiB | 3.23 MiB | + 228.73 KiB |
/wp-admin/edit-comments.php | 0.250 s | 0.294 s | +0.044 s | 3.04 MiB | 3.26 MiB | + 224.52 KiB |
/ | 0.280 s | 0.606 s | +0.326 s | 2.91 MiB | 3.19 MiB | + 285.55 KiB |
Average | 0.500 s | 0.535 s | +0.035 s | 3.43 MiB | 3.67 MiB | + 244.33 KiB |
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 | |
---|---|---|---|---|---|
PO File | 38.1% | 61,096 | 100,066 | 9 | |
PHP | 36.6% | 58,659 | 11,233 | 449 | |
JavaScript | 11.4% | 18,251 | 5,810 | 120 | |
CSS | 7.9% | 12,610 | 611 | 35 | |
SVG | 3.4% | 5,443 | 70 | 98 | |
SQL | 1.6% | 2,623 | 0 | 2 | |
JSX | 0.7% | 1,199 | 0 | 14 | |
HTML | 0.2% | 242 | 9 | 11 | |
JSON | 0.1% | 122 | 0 | 5 | |
Markdown | 0.0% | 29 | 0 | 1 | |
XML | 0.0% | 16 | 0 | 4 | |
GraphQL | 0.0% | 5 | 0 | 1 | |
Sass | 0.0% | 1 | 0 | 1 | |
Total | 160,296 | 117,799 | 750 |
Lines of code | 32,274 |
---|---|
Total complexity | 8,417 |
Median class complexity | 15.0 |
Median method complexity | 3.0 |
Most complex class | wpl_scssc |
Most complex function | wpl_scss_parser::parseChunk() |
Classes | 198 |
---|---|
Methods | 1,789 |
Functions | 3 |
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
5ID | Name |
---|---|
wpl_search_widget | (WPL) Search |
wpl_carousel_widget | (WPL) Carousel |
wpl_agents_widget | (WPL) Agents |
wpl_googlemap_widget | (WPL) Google Maps |
[21-Jul-2021 22:19:22 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5535
[21-Jul-2021 22:19:22 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>idx_api/v1/import/(?P<token>[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 5535
[21-Jul-2021 22:19:22 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5535
[21-Jul-2021 22:19:22 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>idx_api/v1/update/(?P<token>[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 5535
[21-Jul-2021 22:19:22 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5535
[21-Jul-2021 22:19:22 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>idx_api/v1/update_json/(?P<token>[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 5535
[21-Jul-2021 22:19:22 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5535
[21-Jul-2021 22:19:22 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>idx_api/v1/import_json/(?P<token>[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 5535
[21-Jul-2021 22:19:26 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5535
[21-Jul-2021 22:19:26 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>idx_api/v1/import/(?P<token>[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 5535
[21-Jul-2021 22:19:26 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5535
[21-Jul-2021 22:19:26 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>idx_api/v1/update/(?P<token>[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 5535
[21-Jul-2021 22:19:26 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5535
[21-Jul-2021 22:19:26 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>idx_api/v1/update_json/(?P<token>[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 5535
[21-Jul-2021 22:19:26 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5535
[21-Jul-2021 22:19:26 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>idx_api/v1/import_json/(?P<token>[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 5535
[21-Jul-2021 22:19:30 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5535
[21-Jul-2021 22:19:30 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>idx_api/v1/import/(?P<token>[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 5535
[21-Jul-2021 22:19:30 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5535
[21-Jul-2021 22:19:30 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>idx_api/v1/update/(?P<token>[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 5535
[21-Jul-2021 22:19:30 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5535
[21-Jul-2021 22:19:30 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>idx_api/v1/update_json/(?P<token>[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 5535
[21-Jul-2021 22:19:30 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5535
[21-Jul-2021 22:19:30 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>idx_api/v1/import_json/(?P<token>[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 5535