Does Laterpay work with WordPress 5.5.1 and PHP 7.4.8? A smoke test was performed on .
3 | PHP notices |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 679.39 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.404 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 | 90+ |
WordPress.org page | https://wordpress.org/plugins/laterpay/ |
Badges |
Get badge code |
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=laterpay%2Flaterpay.php&plugin_status=all&paged=1&s&_wpnonce=a7166552d0 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 1.229 s |
Memory usage | 3.49 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/options-general.php?page=laterpay |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.340 s |
Memory usage | 3.29 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=laterpay-account-tab |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.348 s |
Memory usage | 3.36 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=laterpay-appearance-tab |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.280 s |
Memory usage | 3.4 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=laterpay-contributions-tab |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.307 s |
Memory usage | 3.39 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=laterpay-pricing-tab |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.533 s |
Memory usage | 3.91 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=laterpay-advanced-tab |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.298 s |
Memory usage | 3.39 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.831 s |
Memory usage | 3.22 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/post-new.php |
---|---|
Aspect | new-meta-boxes |
HTTP status | 200 |
Load time | 2.715 s |
Memory usage | 5.23 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.481 s | 0.709 s | +0.228 s | 2.75 MiB | 3.4 MiB | + 665.97 KiB |
/wp-admin/edit.php | 0.249 s | 0.383 s | +0.134 s | 2.8 MiB | 3.46 MiB | + 680.85 KiB |
/wp-admin/post-new.php | 1.663 s | 4.819 s | +3.156 s | 4.54 MiB | 5.31 MiB | + 784.72 KiB |
/wp-admin/upload.php | 0.701 s | 0.716 s | +0.015 s | 2.63 MiB | 3.28 MiB | + 661.91 KiB |
/wp-admin/options-writing.php | 0.187 s | 0.304 s | +0.117 s | 2.64 MiB | 3.25 MiB | + 625.38 KiB |
/wp-admin/media-new.php | 0.211 s | 0.566 s | +0.355 s | 2.6 MiB | 3.25 MiB | + 664.95 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.198 s | 0.203 s | +0.005 s | 2.64 MiB | 3.35 MiB | + 724.77 KiB |
/wp-admin/post-new.php?post_type=page | 1.533 s | 1.740 s | +0.207 s | 4.53 MiB | 5.18 MiB | + 666.34 KiB |
/wp-admin/options-discussion.php | 0.321 s | 0.298 s | -0.023 s | 2.61 MiB | 3.26 MiB | + 662.7 KiB |
/wp-admin/edit-comments.php | 0.234 s | 0.218 s | -0.016 s | 2.65 MiB | 3.36 MiB | + 725.66 KiB |
/ | 0.341 s | 0.607 s | +0.266 s | 2.56 MiB | 3.15 MiB | + 610 KiB |
Average | 0.556 s | 0.960 s | +0.404 s | 3 MiB | 3.66 MiB | + 679.39 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
50ID | Name |
---|---|
lp_subscription | Subscriptions |
lp_passes | Passes |
{
"post": {
"lp_post-pricing": {
"title": "Pricing for this Post",
"context": "side"
},
"lp_post-teaser": {
"title": "Laterpay Teaser Content",
"context": "normal"
}
},
"attachment": {
"lp_post-teaser": {
"title": "Laterpay Teaser Content",
"context": "normal"
},
"lp_post-pricing": {
"title": "Pricing for this Post",
"context": "side"
}
}
}
[08-Sep-2020 01:29:13 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>laterpay/v1/media-price</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
[08-Sep-2020 01:29:20 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>laterpay/v1/media-price</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
[08-Sep-2020 01:29:24 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>laterpay/v1/media-price</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