Does LaterPay work with WordPress 5.5 and PHP 7.2.16? A smoke test was performed on .
3 | PHP notices |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 798.08 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.374 seconds
The average page load time increased by this amount after activating the plugin.
WordPress version | 5.5 |
---|---|
PHP version | 7.2.16 |
MySQL version | 8.0.15 |
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=a7f5857bb7 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 2.346 s |
Memory usage | 4.85 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/options-general.php?page=laterpay |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.250 s |
Memory usage | 4.71 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.310 s |
Memory usage | 4.77 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.275 s |
Memory usage | 4.8 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.289 s |
Memory usage | 4.8 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.501 s |
Memory usage | 5.23 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.302 s |
Memory usage | 4.8 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.832 s |
Memory usage | 4.45 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/post-new.php |
---|---|
Aspect | new-meta-boxes |
HTTP status | 200 |
Load time | 2.408 s |
Memory usage | 6.65 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.462 s | 0.680 s | +0.218 s | 3.96 MiB | 4.71 MiB | + 766.89 KiB |
/wp-admin/edit.php | 0.223 s | 0.381 s | +0.158 s | 3.99 MiB | 4.82 MiB | + 847.43 KiB |
/wp-admin/post-new.php | 1.555 s | 4.503 s | +2.948 s | 5.81 MiB | 6.75 MiB | + 958.23 KiB |
/wp-admin/upload.php | 0.745 s | 0.703 s | -0.042 s | 3.83 MiB | 4.63 MiB | + 822.14 KiB |
/wp-admin/options-writing.php | 0.164 s | 0.206 s | +0.042 s | 3.9 MiB | 4.61 MiB | + 724.83 KiB |
/wp-admin/media-new.php | 0.203 s | 0.527 s | +0.324 s | 3.8 MiB | 4.61 MiB | + 825.69 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.176 s | 0.186 s | +0.010 s | 3.91 MiB | 4.64 MiB | + 755.03 KiB |
/wp-admin/post-new.php?post_type=page | 1.478 s | 1.639 s | +0.161 s | 5.8 MiB | 6.56 MiB | + 779.32 KiB |
/wp-admin/options-discussion.php | 0.313 s | 0.257 s | -0.056 s | 3.81 MiB | 4.61 MiB | + 823.98 KiB |
/wp-admin/edit-comments.php | 0.222 s | 0.213 s | -0.009 s | 3.91 MiB | 4.65 MiB | + 757.49 KiB |
/ | 0.356 s | 0.711 s | +0.355 s | 3.69 MiB | 4.4 MiB | + 717.79 KiB |
Average | 0.536 s | 0.910 s | +0.374 s | 4.22 MiB | 5 MiB | + 798.08 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
52ID | 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"
}
}
}
[17-Aug-2020 00:37:47 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
[17-Aug-2020 00:37:53 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
[17-Aug-2020 00:37:57 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