Content Update Scheduler 2.3.3

Does Content Update Scheduler work with WordPress 6.7 and PHP 8.1.12? A smoke test was performed on .

Summary

Errors
4Unrecognized messages in the PHP error log
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

Memory usage: 43.36 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.

Environment
WordPress version6.7
PHP version8.1.12
MySQL version10.6.10
PHP memory limit512M
Plugin Info
Last updated
Active installs 1,000+
WordPress.org page https://wordpress.org/plugins/content-update-scheduler/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 3

Plugins ‹ Test site — WordPress

Page screenshot: Plugins ‹ Test site — WordPress
URL /wp-admin/plugins.php?plugin_status=all&paged=1&s
Requested URL /wp-admin/plugins.php?action=activate&plugin=content-update-scheduler%2Fcontent-update-scheduler.php&plugin_status=all&paged=1&s&_wpnonce=50639d14b7
Aspect after-activation
HTTP status 200
Load time 0.242 s
Memory usage 3.56 MiB
JS errors None
Resource errors None

Settings → Scheduled Content Update

Page screenshot: Settings → Scheduled Content Update
URL /wp-admin/options-general.php?page=tsu
Aspect menu-item
HTTP status 200
Load time 0.137 s
Memory usage 3.54 MiB
JS errors None
Resource errors None

Test site – Just another WordPress site

Page screenshot: Test site – Just another WordPress site
URL /
Aspect front-page
HTTP status 200
Load time 0.196 s
Memory usage 3.45 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.278 s0.259 s-0.019 s3.48 MiB3.53 MiB+ 56.13 KiB
/wp-admin/edit.php0.187 s0.186 s-0.001 s3.54 MiB3.6 MiB+ 55.69 KiB
/wp-admin/post-new.php0.741 s0.602 s-0.139 s5.92 MiB5.98 MiB+ 60.49 KiB
/wp-admin/upload.php0.549 s0.298 s-0.251 s3.49 MiB3.53 MiB+ 39.13 KiB
/wp-admin/options-writing.php0.217 s0.376 s+0.159 s3.47 MiB3.51 MiB+ 43.13 KiB
/wp-admin/media-new.php0.282 s0.217 s-0.065 s3.46 MiB3.51 MiB+ 51.32 KiB
/wp-admin/edit-tags.php?taxonomy=category0.261 s0.194 s-0.067 s3.47 MiB3.54 MiB+ 61.99 KiB
/wp-admin/post-new.php?post_type=page0.574 s0.868 s+0.294 s5.92 MiB5.97 MiB+ 56.02 KiB
/wp-admin/options-discussion.php0.255 s0.239 s-0.016 s3.47 MiB3.51 MiB+ 39.63 KiB
/wp-admin/edit-comments.php0.211 s0.208 s-0.003 s3.49 MiB3.53 MiB+ 39.13 KiB
/0.291 s0.213 s-0.078 s3.48 MiB3.45 MiB- 25.69 KiB
Average 0.350 s0.333 s-0.017 s3.93 MiB3.97 MiB+ 43.36 KiB

Code Statistics

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.

PHP
Language % Lines of code Comment lines Files
PHP98.4%9994352
Markdown1.6%1601
Total 1,015 435 3

PHP Code Analysis | More results »

Lines of code 1,006
Total complexity 180
Median class complexity 89.5
Median method complexity 3.0
Most complex class ContentUpdateScheduler
Most complex function ContentUpdateScheduler::save_meta()
Classes 2
Methods 44
Functions 1

Additions

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.

No new entries found.

PHP Error Log 4 lines

[15-Nov-2024 20:22:00 UTC] save_meta called for post ID: 39
[15-Nov-2024 20:22:00 UTC] Post status is not cus_sc_publish and no original post found
[15-Nov-2024 20:22:03 UTC] save_meta called for post ID: 40
[15-Nov-2024 20:22:03 UTC] Post status is not cus_sc_publish and no original post found
See also: All tests for this plugin, How to Hide the "Scheduled Content Update" Admin Menu