Does PublishPress Future work with WordPress 6.4.2 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: 377.44 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.4.2 |
---|---|
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=2802bfdabf |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.590 s |
Memory usage | 4.16 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.330 s |
Memory usage | 3.68 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=publishpress-future |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.204 s |
Memory usage | 3.75 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.191 s |
Memory usage | 3.72 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.415 s |
Memory usage | 3.71 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.210 s |
Memory usage | 3.72 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.194 s |
Memory usage | 3.75 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/tools.php?page=action-scheduler |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.185 s |
Memory usage | 3.7 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.200 s |
Memory usage | 3.61 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/post-new.php |
---|---|
Aspect | new-meta-boxes |
HTTP status | 200 |
Load time | 0.581 s |
Memory usage | 5.87 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.771 s |
Memory usage | 5.85 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.334 s | 0.332 s | -0.002 s | 3.38 MiB | 3.8 MiB | + 428.3 KiB |
/wp-admin/edit.php | 0.203 s | 0.355 s | +0.152 s | 3.41 MiB | 3.89 MiB | + 499.52 KiB |
/wp-admin/post-new.php | 0.964 s | 1.075 s | +0.111 s | 5.46 MiB | 5.87 MiB | + 423.54 KiB |
/wp-admin/upload.php | 0.703 s | 0.413 s | -0.290 s | 3.32 MiB | 3.67 MiB | + 349.69 KiB |
/wp-admin/options-writing.php | 0.255 s | 0.199 s | -0.056 s | 3.32 MiB | 3.65 MiB | + 339.18 KiB |
/wp-admin/media-new.php | 0.333 s | 0.294 s | -0.039 s | 3.29 MiB | 3.65 MiB | + 360.46 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.229 s | 0.201 s | -0.028 s | 3.31 MiB | 3.69 MiB | + 383.95 KiB |
/wp-admin/post-new.php?post_type=page | 0.588 s | 0.570 s | -0.018 s | 5.45 MiB | 5.85 MiB | + 409.31 KiB |
/wp-admin/options-discussion.php | 0.326 s | 0.311 s | -0.015 s | 3.3 MiB | 3.65 MiB | + 352.42 KiB |
/wp-admin/edit-comments.php | 0.280 s | 0.222 s | -0.058 s | 3.34 MiB | 3.67 MiB | + 345.86 KiB |
/ | 0.293 s | 0.223 s | -0.070 s | 3.36 MiB | 3.61 MiB | + 259.58 KiB |
Average | 0.410 s | 0.381 s | -0.028 s | 3.72 MiB | 4.09 MiB | + 377.44 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 | 70.4% | 9,626 | 2,829 | 133 | |
PO File | 22.5% | 3,083 | 1,877 | 5 | |
CSS | 6.0% | 818 | 36 | 6 | |
JSON | 1.0% | 130 | 0 | 2 | |
JavaScript | 0.2% | 25 | 5 | 6 | |
Total | 13,682 | 4,747 | 152 |
Lines of code | 7,758 |
---|---|
Total complexity | 1,138 |
Median class complexity | 7.0 |
Median method complexity | 1.0 |
Most complex class | PublishPress\Future\Modules\Expirator\Models\ExpirablePostModel |
Most complex function | PublishPress\Future\Core\Plugin::manageUpgrade() |
Classes | 97 |
---|---|
Methods | 508 |
Functions | 25 |
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
11ID | Name |
---|---|
scheduled-action | Scheduled Actions |
{
"post": {
"expirationdatediv": {
"title": "PublishPress Future",
"context": "side"
}
},
"page": {
"expirationdatediv": {
"title": "PublishPress Future",
"context": "side"
}
}
}
[13-Dec-2023 17:59:56 UTC] PUBLISHPRESS FUTURE: Result of creating table wp_ppfuture_actions_args: Created table wp_ppfuture_actions_args