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: 411.79 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.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=dcf770493d |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.803 s |
Memory usage | 3.95 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.271 s |
Memory usage | 3.85 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=publishpress_future_pro_features_ads |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.200 s |
Memory usage | 3.83 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=publishpress-future |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.428 s |
Memory usage | 3.86 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.292 s |
Memory usage | 3.85 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.190 s |
Memory usage | 3.85 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.182 s |
Memory usage | 3.84 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.179 s |
Memory usage | 3.86 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.596 s |
Memory usage | 3.86 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/tools.php?page=action-scheduler |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.217 s |
Memory usage | 3.85 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.228 s |
Memory usage | 3.72 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.330 s | 0.397 s | +0.067 s | 3.47 MiB | 3.91 MiB | + 442.16 KiB |
/wp-admin/edit.php | 0.195 s | 0.355 s | +0.160 s | 3.54 MiB | 4.02 MiB | + 494.66 KiB |
/wp-admin/post-new.php | 0.738 s | 0.843 s | +0.105 s | 5.75 MiB | 6.21 MiB | + 468.27 KiB |
/wp-admin/upload.php | 0.541 s | 0.388 s | -0.153 s | 3.49 MiB | 3.85 MiB | + 364.34 KiB |
/wp-admin/options-writing.php | 0.392 s | 0.164 s | -0.228 s | 3.41 MiB | 3.83 MiB | + 427.15 KiB |
/wp-admin/media-new.php | 0.226 s | 0.419 s | +0.193 s | 3.4 MiB | 3.83 MiB | + 440.53 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.192 s | 0.189 s | -0.003 s | 3.47 MiB | 3.84 MiB | + 381.7 KiB |
/wp-admin/post-new.php?post_type=page | 0.565 s | 0.623 s | +0.058 s | 5.75 MiB | 6.19 MiB | + 448.49 KiB |
/wp-admin/options-discussion.php | 0.199 s | 0.257 s | +0.058 s | 3.41 MiB | 3.83 MiB | + 428.84 KiB |
/wp-admin/edit-comments.php | 0.218 s | 0.205 s | -0.013 s | 3.49 MiB | 3.85 MiB | + 364.34 KiB |
/ | 0.488 s | 0.195 s | -0.293 s | 3.45 MiB | 3.72 MiB | + 269.16 KiB |
Average | 0.371 s | 0.367 s | -0.004 s | 3.88 MiB | 4.28 MiB | + 411.79 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.7% | 11,633 | 3,110 | 148 | |
PO File | 21.1% | 3,474 | 2,703 | 5 | |
CSS | 6.5% | 1,072 | 44 | 7 | |
JSON | 1.6% | 258 | 0 | 2 | |
JavaScript | 0.2% | 26 | 6 | 7 | |
Total | 16,463 | 5,863 | 169 |
Lines of code | 9,146 |
---|---|
Total complexity | 1,400 |
Median class complexity | 8.0 |
Median method complexity | 1.0 |
Most complex class | PublishPress\Future\Modules\Expirator\Models\ExpirablePostModel |
Most complex function | PublishPress\Future\Core\Plugin::manageUpgrade() |
Classes | 103 |
---|---|
Methods | 609 |
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
11ID | Name |
---|---|
scheduled-action | Scheduled Actions |
The log file is empty.