WP5.0.3 update : Editorial calendar not working – metoo

I know this isn’t a very good answer, but for right now the answer is to disable the Classic Editor Plugin. That plugin causes the Editorial Calendar code to not even get called.

Because for now I need to use “Classic Editor Plugin” (because, in my website we really can’t work with the awful Gutenberg), I will keep it. But as soon there is – maybe an Editorial Calendar update or WP update- then I’ll try to to deactivated it to to check what happens.

(note I’m creating this thread because I feel like it is not only related to the plugin “Disable Gutenberg”)

For your information,
It seems that the calendar works for other Type Post.

And, for classic “post”, the calendar is working if I use the URL
/wp-admin/post.php?page=cal
(not working with with /wp-admin/edit.php?page=cal)

So, a simple solution would be to update the plugin and link in the sidebar to /wp-admin/post.php?page=cal

Hope that helps ??

Hi Zack,

we recently updated our WordPress site from 4.8 to 5.2 and we have the same problem (calender with no entries for all post types we use). Our editors also won’t accept Gutenberg.

The workaround with “/wp-admin/post.php?page=cal” isn’t working for us.

Is there a chance (or a way) to get the calender working again?

Thanks & best regards from Germany!

Thank you for using the Editorial Calendar. I’m sorry you’re having trouble with it.

The error from the top of this thread turned out to be a problem with the Classic Editor Plugin. Are you using that plugin?

If not, then please tell me more about the problem you are having. Is there calendar not found? Are there errors?

The calendar runs well with WordPress 5.2.1. You can see it running on our test blog here: https://www.zackgrossbart.com/extras/sandbox/wp-admin/edit.php?page=cal

Dear Zack,

thanks for your quick reply!

Actually we are running the “Disable Gutenberg”-Plugin but when I deactivate it, the error stays the same (empty calendar).

I just took a look at the apache error log an found this one:

[Mon May 27 10:22:11.129440 2019] [proxy_fcgi:error] [pid 14467:tid 140345052468992] [client XX.XX.XX.XX:22231] AH01071: Got error ‘PHP message: WordPress-Datenbank-Fehler Incorrect DATETIME value: ‘0000%’ f\xc3\xbcr Abfrage SELECT wp_posts.* FROM wp_posts WHERE 1=1 AND wp_posts.post_type = ‘post’ AND post_date >= ‘2019-02-11’ AND post_date < ‘2019-04-22’ AND post_date_gmt NOT LIKE ‘0000%’ ORDER BY wp_posts.post_date DESC von do_action(‘wp_ajax_edcal_posts’), WP_Hook->do_action, WP_Hook->apply_filters, EdCal->edcal_posts, query_posts, WP_Query->query, WP_Query->get_posts\n’, referer: https://www.XXX-SITE.XX/wp-admin/edit.php?page=cal

Is this going to help?

Regards
Jens

Are there any errors in the browser console when you try to view the calendar?

Dear Zack,

only one entry:

Resetting to date from the edcal_Date cookie: Mon Feb 25 2019 00:00:00 GMT+0100 (Mitteleurop?ische Normalzeit)

So let me see if I understand everything that’s going on. You have no errors in the calendar, but your cookie is taking you back to Feb 25. Does the calendar render completely and just have no posts in it? Is the calendar blank?

This really sounds like a conflict with another plugin. Can you try disabling other plugins and themes and see if that resolves the issue?

Yes, the calenders for all post-types are completly blank althought there are posts published today and others already planed for the upcomming days.

I did a reset on the cookie (now saying “edcal_Date cookie: Mon Jun 03 2019”) but the calender is still blank.

We are using pretty much plugins for frontend as well as backend (like Yoast SEO, Updraft, JSON API, FeedWordPress and Admin Management Xtended) but apart from “Disable Gutenberg” we didn’t add any new plugins (just did some Updates) since our update on WordPress from v4.8 to 5.2.1 (and PHP 7.0 to 7.2).

I even did a roll back to version 3.6.4 of your plugin, deleted it and made a clean new install with the latest version, but I didn’t get it to work again. I also recover our old installation (WP 4.8 w/ PHP 7.0) on a seperate server and there your plugin is working fine, which means it DID work before updating WordPress.

What about the apache error on that SQL-Statement mentioned above? Is it possible that there are corrupt entries in [wp_posts]?

That database error might be causing the issue. Did you change the version of your database? I’m happy to log into your blog and take a look if you’d like to send me a credential: [email protected]

Did you change the version of your database?
Good question. In fact we switched the whole server in order to get everything updated. We are running a Bitnami Ubuntu/WP-Installation on Amazon AWS. Instead of updating OS, services and so on, we made a clean new install on another instance and transfered the complete WP application via Updraft backup. The new server is running MySQL v8.0 from March 2019. So I guess we used an older database version on our old server.

I’m happy to log into your blog and take a look if you’d like to send me a credential
Sorry I can’t give you access to our live system. What I can do is to clone the running instance in order to give you access to copy of our live system. I already started the process of creating a new server image. Can inform you via [email protected] when it’s done?

I just sent you the credential for our new staging account to your email adress. Thanks again!!