Does PublishPress Future work with WordPress 6.3.1 and PHP 8.1.12? A smoke test was performed on .
1 | Unrecognized messages in the PHP error log |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 324.83 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
insignificant.
The plugin didn't make the site noticeably slower.
WordPress version | 6.3.1 |
---|---|
PHP version | 8.1.12 |
MySQL version | 10.6.10 |
PHP memory limit | 512M |
Last updated | |
---|---|
Active installs | 100,000+ |
WordPress.org page | https://wordpress.org/plugins/post-expirator/ |
Badges |
Get badge code |
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=post-expirator%2Fpost-expirator.php&plugin_status=all&paged=1&s&_wpnonce=e2ae927994 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.425 s |
Memory usage | 3.48 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=publishpress-future-scheduled-actions |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.289 s |
Memory usage | 3.07 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=publishpress-future |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.220 s |
Memory usage | 3.14 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=publishpress-future&tab=display |
---|---|
Aspect | menu-item-tab |
HTTP status | 200 |
Load time | 0.224 s |
Memory usage | 3.11 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=publishpress-future&tab=defaults |
---|---|
Aspect | menu-item-tab |
HTTP status | 200 |
Load time | 0.372 s |
Memory usage | 3.1 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=publishpress-future&tab=advanced |
---|---|
Aspect | menu-item-tab |
HTTP status | 200 |
Load time | 0.235 s |
Memory usage | 3.11 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=publishpress-future&tab=diagnostics |
---|---|
Aspect | menu-item-tab |
HTTP status | 200 |
Load time | 0.189 s |
Memory usage | 3.13 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/tools.php?page=action-scheduler |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.172 s |
Memory usage | 3.09 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.170 s |
Memory usage | 3.39 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/post-new.php |
---|---|
Aspect | new-meta-boxes |
HTTP status | 200 |
Load time | 0.636 s |
Memory usage | 5.59 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/post-new.php?post_type=page |
---|---|
Aspect | new-meta-boxes |
HTTP status | 200 |
Load time | 0.635 s |
Memory usage | 5.57 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.372 s | 0.302 s | -0.070 s | 2.82 MiB | 3.13 MiB | + 310.92 KiB |
/wp-admin/edit.php | 0.208 s | 0.369 s | +0.161 s | 2.85 MiB | 3.3 MiB | + 460.8 KiB |
/wp-admin/post-new.php | 0.757 s | 1.054 s | +0.297 s | 5.21 MiB | 5.59 MiB | + 386.25 KiB |
/wp-admin/upload.php | 0.865 s | 0.295 s | -0.570 s | 2.77 MiB | 3.05 MiB | + 293.16 KiB |
/wp-admin/options-writing.php | 0.245 s | 0.193 s | -0.052 s | 2.76 MiB | 3.04 MiB | + 285.13 KiB |
/wp-admin/media-new.php | 0.325 s | 0.240 s | -0.085 s | 2.74 MiB | 3.04 MiB | + 305.35 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.196 s | 0.203 s | +0.007 s | 2.76 MiB | 3.06 MiB | + 310.53 KiB |
/wp-admin/post-new.php?post_type=page | 0.692 s | 0.755 s | +0.063 s | 5.21 MiB | 5.57 MiB | + 372.02 KiB |
/wp-admin/options-discussion.php | 0.270 s | 0.295 s | +0.025 s | 2.75 MiB | 3.03 MiB | + 293.66 KiB |
/wp-admin/edit-comments.php | 0.430 s | 0.207 s | -0.223 s | 2.78 MiB | 3.06 MiB | + 292.43 KiB |
/ | 0.279 s | 0.226 s | -0.053 s | 3.13 MiB | 3.39 MiB | + 262.85 KiB |
Average | 0.422 s | 0.376 s | -0.045 s | 3.25 MiB | 3.57 MiB | + 324.83 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 | |
---|---|---|---|---|---|
PHP | 67.9% | 8,948 | 2,766 | 117 | |
PO File | 24.0% | 3,157 | 1,858 | 5 | |
CSS | 5.8% | 760 | 36 | 6 | |
JavaScript | 1.3% | 175 | 27 | 5 | |
JSON | 1.0% | 130 | 0 | 2 | |
Total | 13,170 | 4,687 | 135 |
Lines of code | 6,620 |
---|---|
Total complexity | 998 |
Median class complexity | 6.0 |
Median method complexity | 1.0 |
Most complex class | PublishPress\Future\Modules\Expirator\Models\ExpirablePostModel |
Most complex function | postexpirator_update_post_meta() |
Classes | 83 |
---|---|
Methods | 397 |
Functions | 44 |
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
3ID | Name |
---|---|
scheduled-action | Scheduled Actions |
{
"post": {
"expirationdatediv": {
"title": "PublishPress Future",
"context": "side"
}
},
"page": {
"expirationdatediv": {
"title": "PublishPress Future",
"context": "side"
}
}
}
[06-Sep-2023 16:01:25 UTC] PUBLISHPRESS FUTURE: Result of creating table wp_ppfuture_actions_args: Created table wp_ppfuture_actions_args