Does PublishPress Future work with WordPress 6.7.1 and PHP 8.1.12? A smoke test was performed on .
No PHP errors, warnings or notices | |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors | |
Looks good! No problems were detected. |
Memory usage: 602.81 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.069 seconds
The average page load time increased by this amount after activating the plugin.
WordPress version | 6.7.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 |
|
URL | /wp-admin/admin.php?page=publishpress-future |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=post-expirator%2Fpost-expirator.php&plugin_status=all&paged=1&s&_wpnonce=95efd5818a |
Aspect | after-activation |
HTTP status | 200 |
Load time | 1.027 s |
Memory usage | 4.39 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/edit.php?post_type=ppfuture_workflow |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.349 s |
Memory usage | 4.13 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=publishpress-future |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.422 s |
Memory usage | 4.04 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=publishpress-future&tab=general |
---|---|
Aspect | menu-item-tab |
HTTP status | 200 |
Load time | 0.308 s |
Memory usage | 4.08 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=publishpress-future&tab=notifications |
---|---|
Aspect | menu-item-tab |
HTTP status | 200 |
Load time | 0.235 s |
Memory usage | 4.09 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.274 s |
Memory usage | 4.15 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.361 s |
Memory usage | 4.08 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.253 s |
Memory usage | 4.11 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=publishpress-future |
---|---|
Aspect | menu-item-tab |
HTTP status | 200 |
Load time | 0.456 s |
Memory usage | 4.04 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=future-backup#export |
---|---|
Requested URL | /wp-admin/admin.php?page=future-backup |
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.428 s |
Memory usage | 4.02 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=future-backup#export |
---|---|
Requested URL | /wp-admin/admin.php?page=future-backup |
Aspect | menu-item-tab |
HTTP status | 200 |
Load time | 0.366 s |
Memory usage | 4 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/tools.php?page=action-scheduler |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.279 s |
Memory usage | 4.05 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.242 s |
Memory usage | 3.86 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.319 s | 0.457 s | +0.138 s | 3.48 MiB | 4.06 MiB | + 593.79 KiB |
/wp-admin/edit.php | 0.195 s | 0.344 s | +0.149 s | 3.54 MiB | 4.19 MiB | + 660.55 KiB |
/wp-admin/post-new.php | 0.759 s | 0.883 s | +0.124 s | 5.92 MiB | 6.72 MiB | + 811.76 KiB |
/wp-admin/upload.php | 0.568 s | 0.442 s | -0.126 s | 3.5 MiB | 4.03 MiB | + 543.45 KiB |
/wp-admin/options-writing.php | 0.222 s | 0.468 s | +0.246 s | 3.47 MiB | 4.01 MiB | + 549.67 KiB |
/wp-admin/media-new.php | 0.365 s | 0.316 s | -0.049 s | 3.46 MiB | 4 MiB | + 553.71 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.177 s | 0.261 s | +0.084 s | 3.48 MiB | 4.03 MiB | + 566.52 KiB |
/wp-admin/post-new.php?post_type=page | 0.597 s | 0.714 s | +0.117 s | 5.92 MiB | 6.7 MiB | + 795.32 KiB |
/wp-admin/options-discussion.php | 0.259 s | 0.550 s | +0.291 s | 3.47 MiB | 4 MiB | + 542.95 KiB |
/wp-admin/edit-comments.php | 0.405 s | 0.314 s | -0.091 s | 3.49 MiB | 4.03 MiB | + 550.3 KiB |
/ | 0.311 s | 0.191 s | -0.120 s | 3.41 MiB | 3.86 MiB | + 462.85 KiB |
Average | 0.380 s | 0.449 s | +0.069 s | 3.92 MiB | 4.51 MiB | + 602.81 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 | |
---|---|---|---|---|---|
JavaScript | 74.7% | 114,572 | 18,811 | 25 | |
PHP | 18.3% | 28,133 | 4,709 | 320 | |
PO File | 6.0% | 9,232 | 6,464 | 15 | |
CSS | 0.7% | 1,092 | 42 | 8 | |
JSON | 0.2% | 285 | 0 | 12 | |
Markdown | 0.1% | 105 | 0 | 3 | |
Total | 153,419 | 30,026 | 383 |
Lines of code | 24,056 |
---|---|
Total complexity | 3,422 |
Median class complexity | 10.0 |
Median method complexity | 1.0 |
Most complex class | PublishPress\Future\Modules\Workflows\Models\WorkflowModel |
Most complex function | PublishPress\Future\Modules\Workflows\Controllers\ScheduledActions::showArgsInArgsColumn() |
Classes | 219 |
---|---|
Methods | 1,871 |
Functions | 27 |
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
12ID | Name |
---|---|
scheduled-action | Scheduled Actions |
ppfuture_workflow | Action Workflows |
The log file is empty.