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: 362.11 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=6d1e03bda0 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.449 s |
Memory usage | 4.08 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.345 s |
Memory usage | 3.66 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=publishpress-future |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.241 s |
Memory usage | 3.73 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.215 s |
Memory usage | 3.7 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.339 s |
Memory usage | 3.69 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.234 s |
Memory usage | 3.71 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.366 s |
Memory usage | 3.73 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/tools.php?page=action-scheduler |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.209 s |
Memory usage | 3.68 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.220 s |
Memory usage | 3.6 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/post-new.php |
---|---|
Aspect | new-meta-boxes |
HTTP status | 200 |
Load time | 0.641 s |
Memory usage | 5.85 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.654 s |
Memory usage | 5.83 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.396 s | 0.372 s | -0.024 s | 3.38 MiB | 3.78 MiB | + 412.42 KiB |
/wp-admin/edit.php | 0.342 s | 0.269 s | -0.073 s | 3.41 MiB | 3.89 MiB | + 498.49 KiB |
/wp-admin/post-new.php | 0.885 s | 0.631 s | -0.254 s | 5.46 MiB | 5.85 MiB | + 402.8 KiB |
/wp-admin/upload.php | 0.595 s | 0.456 s | -0.139 s | 3.32 MiB | 3.65 MiB | + 333.81 KiB |
/wp-admin/options-writing.php | 0.235 s | 0.192 s | -0.043 s | 3.32 MiB | 3.63 MiB | + 323.3 KiB |
/wp-admin/media-new.php | 0.319 s | 0.594 s | +0.275 s | 3.29 MiB | 3.63 MiB | + 344.59 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.223 s | 0.204 s | -0.019 s | 3.31 MiB | 3.67 MiB | + 368.08 KiB |
/wp-admin/post-new.php?post_type=page | 0.809 s | 0.671 s | -0.138 s | 5.45 MiB | 5.83 MiB | + 388.57 KiB |
/wp-admin/options-discussion.php | 0.318 s | 0.295 s | -0.023 s | 3.3 MiB | 3.63 MiB | + 336.55 KiB |
/wp-admin/edit-comments.php | 0.316 s | 0.234 s | -0.082 s | 3.34 MiB | 3.66 MiB | + 329.98 KiB |
/ | 0.288 s | 0.196 s | -0.092 s | 3.36 MiB | 3.6 MiB | + 244.59 KiB |
Average | 0.430 s | 0.374 s | -0.056 s | 3.72 MiB | 4.08 MiB | + 362.11 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 | 68.6% | 9,225 | 2,823 | 120 | |
PO File | 23.5% | 3,157 | 1,858 | 5 | |
CSS | 5.6% | 757 | 36 | 6 | |
JavaScript | 1.3% | 175 | 27 | 5 | |
JSON | 1.0% | 130 | 0 | 2 | |
Total | 13,444 | 4,744 | 138 |
Lines of code | 6,942 |
---|---|
Total complexity | 1,035 |
Median class complexity | 6.5 |
Median method complexity | 1.0 |
Most complex class | PublishPress\Future\Modules\Expirator\Models\ExpirablePostModel |
Most complex function | postexpirator_update_post_meta() |
Classes | 86 |
---|---|
Methods | 416 |
Functions | 45 |
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"
}
}
}
[06-Dec-2023 21:08:05 UTC] PUBLISHPRESS FUTURE: Result of creating table wp_ppfuture_actions_args: Created table wp_ppfuture_actions_args