Does WPL work with WordPress 5.5.1 and PHP 7.4.8? A smoke test was performed on .
12 | PHP notices |
4 | PHP deprecation warnings |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 238.45 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.371 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 | 2,000+ |
WordPress.org page | https://wordpress.org/plugins/real-estate-listing-realtyna-wpl/ |
Badges |
|
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=f68227eafa |
Aspect | after-activation |
HTTP status | 200 |
Load time | 21.771 s |
Memory usage | 2.98 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=WPL_main_menu |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 1.588 s |
Memory usage | 3.18 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 | 3.672 s |
Memory usage | 3.25 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.796 s |
Memory usage | 3.02 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.511 s |
Memory usage | 3.3 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.914 s |
Memory usage | 3.06 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.404 s |
Memory usage | 2.92 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.365 s |
Memory usage | 3.1 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.331 s |
Memory usage | 3.07 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.484 s |
Memory usage | 3.65 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.815 s |
Memory usage | 3.14 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.561 s |
Memory usage | 3.22 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.574 s |
Memory usage | 3.01 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 1.232 s |
Memory usage | 2.78 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/widgets.php |
---|---|
Aspect | new-sidebar-widgets |
HTTP status | 200 |
Load time | 1.560 s |
Memory usage | 3.9 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.482 s | 0.744 s | +0.262 s | 2.75 MiB | 2.96 MiB | + 215.33 KiB |
/wp-admin/edit.php | 0.239 s | 0.571 s | +0.332 s | 2.8 MiB | 3.01 MiB | + 215.09 KiB |
/wp-admin/post-new.php | 1.649 s | 2.595 s | +0.946 s | 4.54 MiB | 4.79 MiB | + 250.53 KiB |
/wp-admin/upload.php | 0.686 s | 0.674 s | -0.012 s | 2.63 MiB | 2.86 MiB | + 238.07 KiB |
/wp-admin/options-writing.php | 0.176 s | 0.283 s | +0.107 s | 2.64 MiB | 2.84 MiB | + 203.33 KiB |
/wp-admin/media-new.php | 0.226 s | 0.309 s | +0.083 s | 2.6 MiB | 2.84 MiB | + 242.79 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.209 s | 0.350 s | +0.141 s | 2.64 MiB | 2.91 MiB | + 268.91 KiB |
/wp-admin/post-new.php?post_type=page | 1.619 s | 3.172 s | +1.553 s | 4.53 MiB | 4.77 MiB | + 242.12 KiB |
/wp-admin/options-discussion.php | 0.380 s | 0.567 s | +0.187 s | 2.61 MiB | 2.84 MiB | + 239.23 KiB |
/wp-admin/edit-comments.php | 0.243 s | 0.422 s | +0.179 s | 2.65 MiB | 2.92 MiB | + 276.11 KiB |
/ | 0.357 s | 0.655 s | +0.298 s | 2.56 MiB | 2.78 MiB | + 231.44 KiB |
Average | 0.570 s | 0.940 s | +0.371 s | 3 MiB | 3.23 MiB | + 238.45 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
5ID | Name |
---|---|
wpl_search_widget | (WPL) Search |
wpl_carousel_widget | (WPL) Carousel |
wpl_agents_widget | (WPL) Agents |
wpl_googlemap_widget | (WPL) Google Maps |
[02-Sep-2020 21:26:15 UTC] PHP Deprecated: Array and string offset access syntax with curly braces is deprecated in /wp-content/plugins/real-estate-listing-realtyna-wpl/libraries/path.php on line 117
[02-Sep-2020 21:26:15 UTC] PHP Deprecated: Array and string offset access syntax with curly braces is deprecated in /wp-content/plugins/real-estate-listing-realtyna-wpl/libraries/path.php on line 119
[02-Sep-2020 21:26:15 UTC] PHP Deprecated: Array and string offset access syntax with curly braces is deprecated in /wp-content/plugins/real-estate-listing-realtyna-wpl/libraries/path.php on line 121
[02-Sep-2020 21:26:47 UTC] PHP Deprecated: Function get_magic_quotes_gpc() is deprecated in /wp-content/plugins/real-estate-listing-realtyna-wpl/views/backend/settings/tmpl/internal_requirements.php on line 130
[02-Sep-2020 21:26:59 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 5225
[02-Sep-2020 21:26:59 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 5225
[02-Sep-2020 21:26:59 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 5225
[02-Sep-2020 21:26:59 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 5225
[02-Sep-2020 21:26:59 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 5225
[02-Sep-2020 21:26:59 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 5225
[02-Sep-2020 21:27:04 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 5225
[02-Sep-2020 21:27:04 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 5225
[02-Sep-2020 21:27:04 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 5225
[02-Sep-2020 21:27:04 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 5225
[02-Sep-2020 21:27:04 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 5225
[02-Sep-2020 21:27:04 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 5225