Does PublishPress Future work with WordPress 6.6.2 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: 565.97 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.065 seconds
The average page load time increased by this amount after activating the plugin.
WordPress version | 6.6.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/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=936e54d81a |
Aspect | after-activation |
HTTP status | 200 |
Load time | 3.417 s |
Memory usage | 4.29 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.444 s |
Memory usage | 4.01 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.395 s |
Memory usage | 4.09 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=publishpress-future |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.466 s |
Memory usage | 3.99 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.306 s |
Memory usage | 4.06 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.253 s |
Memory usage | 4.07 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.380 s |
Memory usage | 4.03 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.377 s |
Memory usage | 4.06 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.519 s |
Memory usage | 3.99 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/tools.php?page=action-scheduler |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.240 s |
Memory usage | 3.99 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.285 s |
Memory usage | 3.82 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.384 s | 0.484 s | +0.100 s | 3.47 MiB | 4.01 MiB | + 549.32 KiB |
/wp-admin/edit.php | 0.215 s | 0.321 s | +0.106 s | 3.54 MiB | 4.13 MiB | + 611.61 KiB |
/wp-admin/post-new.php | 0.775 s | 1.143 s | +0.368 s | 5.75 MiB | 6.48 MiB | + 746.81 KiB |
/wp-admin/upload.php | 0.650 s | 0.737 s | +0.087 s | 3.49 MiB | 3.98 MiB | + 497.26 KiB |
/wp-admin/options-writing.php | 0.204 s | 0.307 s | +0.103 s | 3.41 MiB | 3.96 MiB | + 561.64 KiB |
/wp-admin/media-new.php | 0.223 s | 0.309 s | +0.086 s | 3.4 MiB | 3.95 MiB | + 568.45 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.180 s | 0.249 s | +0.069 s | 3.47 MiB | 3.98 MiB | + 520.33 KiB |
/wp-admin/post-new.php?post_type=page | 1.012 s | 0.681 s | -0.331 s | 5.75 MiB | 6.46 MiB | + 734.44 KiB |
/wp-admin/options-discussion.php | 0.227 s | 0.376 s | +0.149 s | 3.41 MiB | 3.96 MiB | + 561.23 KiB |
/wp-admin/edit-comments.php | 0.258 s | 0.305 s | +0.047 s | 3.49 MiB | 3.98 MiB | + 504.12 KiB |
/ | 0.307 s | 0.233 s | -0.074 s | 3.45 MiB | 3.82 MiB | + 370.49 KiB |
Average | 0.403 s | 0.468 s | +0.065 s | 3.88 MiB | 4.43 MiB | + 565.97 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 | 70.9% | 72,729 | 14,391 | 17 | |
PHP | 21.9% | 22,466 | 4,176 | 277 | |
PO File | 5.8% | 5,945 | 4,172 | 10 | |
CSS | 1.1% | 1,159 | 44 | 9 | |
JSON | 0.3% | 270 | 0 | 7 | |
Total | 102,569 | 22,783 | 320 |
Lines of code | 19,200 |
---|---|
Total complexity | 2,834 |
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 | 190 |
---|---|
Methods | 1,493 |
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.