Content Update Scheduler 2.3.5

Does Content Update Scheduler work with WordPress 6.8.1 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: 53.71 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.8.1
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=0d986a1fd3
Aspect after-activation
HTTP status 200
Load time 0.283 s
Memory usage 3.59 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.158 s
Memory usage 3.57 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.179 s
Memory usage 3.48 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.353 s0.302 s-0.051 s3.51 MiB3.56 MiB+ 56.73 KiB
/wp-admin/edit.php0.215 s0.209 s-0.006 s3.57 MiB3.63 MiB+ 55.91 KiB
/wp-admin/post-new.php0.851 s0.663 s-0.188 s6.06 MiB6.14 MiB+ 80.36 KiB
/wp-admin/upload.php0.784 s0.531 s-0.253 s3.52 MiB3.56 MiB+ 39.36 KiB
/wp-admin/options-writing.php0.237 s0.203 s-0.034 s3.5 MiB3.54 MiB+ 43.35 KiB
/wp-admin/media-new.php0.286 s0.271 s-0.015 s3.49 MiB3.54 MiB+ 51.55 KiB
/wp-admin/edit-tags.php?taxonomy=category0.207 s0.200 s-0.007 s3.5 MiB3.56 MiB+ 62.22 KiB
/wp-admin/post-new.php?post_type=page0.773 s0.637 s-0.136 s6.05 MiB6.12 MiB+ 75.88 KiB
/wp-admin/options-discussion.php0.479 s0.251 s-0.228 s3.5 MiB3.54 MiB+ 39.85 KiB
/wp-admin/edit-comments.php0.253 s0.423 s+0.170 s3.52 MiB3.56 MiB+ 39.35 KiB
/0.337 s0.200 s-0.137 s3.43 MiB3.48 MiB+ 46.28 KiB
Average 0.434 s0.354 s-0.080 s3.97 MiB4.02 MiB+ 53.71 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.6%1,1584932
Markdown1.4%1601
Total 1,174 493 3

PHP Code Analysis | More results »

Lines of code 1,165
Total complexity 202
Median class complexity 100.5
Median method complexity 3.0
Most complex class ContentUpdateScheduler
Most complex function ContentUpdateScheduler::save_meta()
Classes 2
Methods 46
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

[03-May-2025 03:52:30 UTC] save_meta called for post ID: 39
[03-May-2025 03:52:30 UTC] Post status is not cus_sc_publish and no original post found
[03-May-2025 03:52:33 UTC] save_meta called for post ID: 40
[03-May-2025 03:52:33 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