Content Update Scheduler 2.3.6

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: 47.45 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=0f54c6704f
Aspect after-activation
HTTP status 200
Load time 0.216 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.125 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.143 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.258 s0.228 s-0.030 s3.51 MiB3.56 MiB+ 56.54 KiB
/wp-admin/edit.php0.174 s0.156 s-0.018 s3.57 MiB3.63 MiB+ 55.73 KiB
/wp-admin/post-new.php0.674 s0.552 s-0.122 s6.06 MiB6.14 MiB+ 80.16 KiB
/wp-admin/upload.php0.774 s0.430 s-0.344 s3.52 MiB3.56 MiB+ 39.17 KiB
/wp-admin/options-writing.php0.182 s0.190 s+0.008 s3.5 MiB3.54 MiB+ 43.16 KiB
/wp-admin/media-new.php0.225 s0.204 s-0.021 s3.49 MiB3.54 MiB+ 51.36 KiB
/wp-admin/edit-tags.php?taxonomy=category0.171 s0.176 s+0.005 s3.5 MiB3.56 MiB+ 62.03 KiB
/wp-admin/post-new.php?post_type=page0.524 s0.543 s+0.019 s6.05 MiB6.12 MiB+ 75.7 KiB
/wp-admin/options-discussion.php0.232 s0.339 s+0.107 s3.5 MiB3.54 MiB+ 39.66 KiB
/wp-admin/edit-comments.php0.340 s0.169 s-0.171 s3.52 MiB3.56 MiB+ 39.16 KiB
/0.325 s0.338 s+0.013 s3.5 MiB3.48 MiB- 20.74 KiB
Average 0.353 s0.302 s-0.050 s3.98 MiB4.02 MiB+ 47.45 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,1324952
Markdown1.4%1601
Total 1,148 495 3

PHP Code Analysis | More results »

Lines of code 1,139
Total complexity 200
Median class complexity 99.5
Median method complexity 3.0
Most complex class ContentUpdateScheduler
Most complex function ContentUpdateScheduler::save_meta()
Classes 2
Methods 45
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

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