Does WPL work with WordPress 5.7.2 and PHP 7.4.8? A smoke test was performed on .
16 | PHP notices |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 285.27 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.132 seconds
The average page load time increased by this amount after activating the plugin.
WordPress version | 5.7.2 |
---|---|
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=b4c77ccd22 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 21.800 s |
Memory usage | 3.06 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.291 s |
Memory usage | 3.27 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.698 s |
Memory usage | 3.33 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.501 s |
Memory usage | 3.16 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.357 s |
Memory usage | 3.38 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.485 s |
Memory usage | 3.2 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.315 s |
Memory usage | 3.06 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.259 s |
Memory usage | 3.25 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.288 s |
Memory usage | 3.22 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.288 s |
Memory usage | 3.79 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.489 s |
Memory usage | 3.24 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.487 s |
Memory usage | 3.31 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.679 s |
Memory usage | 3.16 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.993 s |
Memory usage | 2.85 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/widgets.php |
---|---|
Aspect | new-sidebar-widgets |
HTTP status | 200 |
Load time | 1.189 s |
Memory usage | 3.98 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.251 s | 0.531 s | +0.280 s | 2.82 MiB | 3.06 MiB | + 243.06 KiB |
/wp-admin/edit.php | 0.181 s | 0.386 s | +0.205 s | 2.86 MiB | 3.09 MiB | + 231.46 KiB |
/wp-admin/post-new.php | 0.860 s | 1.192 s | +0.332 s | 5.02 MiB | 5.36 MiB | + 347.1 KiB |
/wp-admin/upload.php | 0.463 s | 0.534 s | +0.071 s | 2.7 MiB | 3.01 MiB | + 326.12 KiB |
/wp-admin/options-writing.php | 0.264 s | 0.220 s | -0.044 s | 2.71 MiB | 3 MiB | + 291.06 KiB |
/wp-admin/media-new.php | 0.220 s | 0.244 s | +0.024 s | 2.67 MiB | 2.99 MiB | + 328.96 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.180 s | 0.256 s | +0.076 s | 2.77 MiB | 3.01 MiB | + 248.7 KiB |
/wp-admin/post-new.php?post_type=page | 1.100 s | 1.007 s | -0.093 s | 5.01 MiB | 5.35 MiB | + 346.69 KiB |
/wp-admin/options-discussion.php | 0.290 s | 0.461 s | +0.171 s | 2.68 MiB | 2.99 MiB | + 326.96 KiB |
/wp-admin/edit-comments.php | 0.246 s | 0.306 s | +0.060 s | 2.78 MiB | 3.02 MiB | + 246.67 KiB |
/ | 0.255 s | 0.627 s | +0.372 s | 2.65 MiB | 2.85 MiB | + 201.19 KiB |
Average | 0.392 s | 0.524 s | +0.132 s | 3.15 MiB | 3.43 MiB | + 285.27 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,584 | 11,223 | 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,221 | 117,789 | 750 |
Lines of code | 32,201 |
---|---|
Total complexity | 8,393 |
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,788 |
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 |
[17-Jul-2021 20:26:45 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 5313
[17-Jul-2021 20:26:45 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 5313
[17-Jul-2021 20:26:45 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 5313
[17-Jul-2021 20:26:45 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 5313
[17-Jul-2021 20:26:45 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 5313
[17-Jul-2021 20:26:45 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 5313
[17-Jul-2021 20:26:45 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 5313
[17-Jul-2021 20:26:45 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 5313
[17-Jul-2021 20:26:49 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 5313
[17-Jul-2021 20:26:49 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 5313
[17-Jul-2021 20:26:49 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 5313
[17-Jul-2021 20:26:49 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 5313
[17-Jul-2021 20:26:49 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 5313
[17-Jul-2021 20:26:49 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 5313
[17-Jul-2021 20:26:49 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 5313
[17-Jul-2021 20:26:49 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 5313