mwschaff

I use Google authenticator and it has worked well for quite awhile.

I looked in /wp-content/error_log and there were 3 messages about “Cannot modify header information – headers already sent”. If I should be looking in another place please let me know.

The automated email from WP showed the following info (note – I have replaced user ID info with all *’s)

WordPress version 6.4.3 Active theme: Kadence Child (version 1.1.35.1682449397) Current plugin: All In One WP Security (version 5.2.7) PHP version 8.2.15 Error Details ============= An error of type E_ERROR was caused in line 678 of the file /home3//public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/classes/wp-security-user-login.php. Error message: Uncaught Error: Call to undefined function get_active_blog_for_user() in /home3//public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/classes/wp-security-user-login.php:678 Stack trace: #0 /home3//public_html/wp-includes/class-wp-hook.php(324): AIOWPSecurity_User_Login->wp_logout_action_handler(0) #1 /home3//public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(false, Array) #2 /home3//public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #3 /home3//public_html/wp-includes/pluggable.php(671): do_action(‘wp_logout’, 0) #4 /home3//public_html/wp-content/plugins/google-authenticator/google-authenticator.php(624): wp_logout() #5 /home3//public_html/wp-includes/class-wp-hook.php(324): GoogleAuthenticator->check_otp(Object(WP_User), ‘‘, ‘s%u(@l9Z(vVEbIH…’) #6 /home3//public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters(Object(WP_User), Array) #7 /home3//public_html/wp-includes/pluggable.php(618): apply_filters(‘authenticate’, NULL, ‘‘, ‘s%u(@l9Z(vVEbIH…’) #8 /home3//public_html/wp-includes/user.php(106): wp_authenticate(‘‘, ‘s%u(@l9Z(vVEbIH…’) #9 /home3/*/public_html/wp-login.php(1311): wp_signon(Array, true) #10 {main} thrown

Excellent clarification. Thank you. (I voted too *****)

Thank you for the clarification; it is very helpful. I don’t like to make changes as the description seemed to be suggesting without understanding the rationale for it and the risks and benefits.

Thanks @topher1kenobe and thanks again for the help.

I think I found the issue. Based on @topher1kenobe suggestion I did try troubleshooting mode but it seemed to give inconsistent results so I started looking at possible settings conflicts in each of the plugins I was using.

It appears to be a setting within the Docket Cache – Object Cache Accelerator plugin that is causing the problem. Within the configuration settings is “Post Missed Schedule Tweaks” described as “Fix the WordPress Missed Schedule Error after scheduling a future blog post”. I had this set to enabled and it was that way for quite sometime without issue. When I changed it to disabled I was able to schedule a post. I also had a separate Missed Schedule plugin for quite sometime. However, deactivating that plugin did not solve the issue from which I infer that it wasn’t in conflict with Docket Cache since the problem was there even when the Missed Schedule plugin was deactivated.

To resolve the missed schedule problem I disable WP-Cron being initiated by a site visitor by adding define(‘DISABLE_WP_CRON’, true); to the wp-config.php file and then running a cron job through CPanel every 5 minutes to run wp-cron.php. I also deactivated the Missed Schedule plugin at the above does the same thing.

This is all based on a limited number of scheduled test posts so I’m not absolutely positive this resolves it but it looks very promising. More real world confirmation is needed.

I signed up for Discord as suggested by @topher1kenobe but they are talking way over my head as my developer skills are limited (to put it very kindly).

To summarize the issue: When I schedule a WP post in either classic editor or block editor in both WP 5.8.3 or WP 5.9 although the post shows it scheduled when I go to the Posts listings (all posts) it immediately shows as published. As @topher1kenobe confirm it does in fact publish and is visible to all. I first noticed this on a post on January 31st and didn’t have the issue (as best I recall) on a post of January 12th.

To summarize what I’ve tried:
– in the troubleshooting mode with all plugins disabled I still had the issue
– in the troubleshooting mode with all plugins disabled and using the default theme associated with the version of WP I was on (tried with 5.8.3 and 5.9) I still had the issue.
– I re-installed the core WP files for version 5.8.3 and still had the issue
– I updated WP to 5.9 and still have the issue
Basically regardless of WP version with no plugins enabled and using a default theme I have the issue.

I can’t find very much online about this issue. It seems some possible areas to look at are:
– Cron job – is a “hook” not being established so it defaults to publish immediately. How I would verify this and fix if it is this is beyond my knowledge
– Settings – I don’t recall changing any settings prior to this starting but I guess that is possible
– Permission levels – I don’t recall changing any permission levels prior to this starting but I guess that is possible
– a real bug in WP -I guess this is possible but seems unlikely as I seem to be the only one with this issue

If anyone has a suggestion it would be greatly appreciated.

• This reply was modified 3 years, 1 month ago by mwschaff.
• This reply was modified 3 years, 1 month ago by mwschaff.

I completely understand – thanks for your efforts. I may end up having to live without scheduling or hopefully this might be fixed when I go to WP5.9.

It happens with classic editor also. If it were a real bug everyone would have the same issue wouldn’t they?

• This reply was modified 3 years, 1 month ago by mwschaff.

Ok now this is getting weird.

I used the troubleshooting mode of Site Health
– all plugins disabled
– default theme enabled – tried it with 2020 and 2019

The problem still happened.

I did notice 2 unusual thing.
First
– I would schedule the post in block editor and click on the WP logo in the upper-left corner to get back to the ALl Posts page of wp-admin
– at this point is showed as scheduled and was not visible on the website
– if I refreshed the All Posts page or cleared cache the scheduled post immediately changed to published and showed up on the website.

Second,
On the trouble shooting page I saw this message

“When enabling the plugin, wordpress-seo, a site failure occurred. Because of this the change was automatically reverted.”

I use Yoast SEO no plugin called “wordpress-seo. Disabling Yoast did not resolve the issue.

I also removed some changes in wp-config.php and the child theme functions.php that were put in shortly before this issue occurred. Taking them out did not solve the issue.

Thanks. I forgot about the troubleshooting mode in Site Health. It does make it easier.

Well it looks like it’s a plugin. With all deactivated it shows scheduled and doesn’t appear. Activate all and it is published.

Now to wade through them and figure out which one. Was hoping for an easier solution but that’s just how it goes sometimes.

Thanks. I’m removing it now. And working on the staging site setup.

Thanks. I take it that you confirm it is published and shows a date of Feb 17th? Is that correct?

I will try setting up a staging site to deactivate all the plugins and use a default theme.

Here is a link to a test post scheduled to go live on Feb 17th. However it shows on my home pages etc.

https://mikeschaffnerphotography.com/test-post/ (now removed)

• This reply was modified 3 years, 1 month ago by mwschaff.

Will do. Thank you very much for your help.

Update: Realized I failed to answer your question. Yes the only plugin I enabled when in the troubleshooting mode was Site Kit.

• This reply was modified 3 years, 2 months ago by mwschaff.