This happened to me as well. I took the route of renaming the plugin folder to fix my admin page, but of course that leaves the plugin inoperable. What should we do?
Updated to 3.1.6 the problem still persists.
Same here. Waiting for a fix please!
Crashed my wp-admin.
Hi folks. 3.1.5 was released on Sunday and fixed timezone issues for many of our international folks.
A bug was discovered shortly after by a user related to events without an end time using the [when] tag, and we released 3.1.6 to fix this yesterday (Monday).
If you upgraded to 3.1.6 and are still experiencing issues, we’d love to get the event template tags, public calendar ID, etc. that you’re using.
There’s no way to debug this unless we have these details. See this post on what’s helpful to us when posting support requests.
https://ww.wp.xz.cn/support/topic/read-first-simple-calendar-support-and-troubleshooting-guide/
If you need to revert to 3.1.4 (or older versions) temporarily you can always grab them here:
https://ww.wp.xz.cn/plugins/google-calendar-events/developers/
Thanks!
-
This reply was modified 9 years, 8 months ago by
Phil Derksen.
Unfortunately, activating Simple Calendar causes wp-admin to die (returns 500 status code), so there’s no way to directly collect data. That also seems to indicate that this problem is independent of the particular calendars and tags being used. Is there anything else I could report to you that might help?
@craigdberry After removing 3.1.6 (via FTP I assume), does reinstalling version 3.1.4 not work at all?
I haven’t had the opportunity to try that yet. The recovery sequence so far was
1. ssh to server and rename the plugin directory.
2. Load wp-admin, which then worked, and reported the plugin had been auto-disabled due to lack of directory.
3. Rename the plugin dir back to original.
4. Confirm that wp-admin still loads, and reports plugin as disabled.
If the problem hasn’t been resolved by this evening, I will try reverting to 3.1.4 then. I assume that the sequence would be to uninstall the plugin, and then install 3.1.4 from a locally downloaded copy?
Following.
I didn’t have access to crash data, I just have bluehost to support me.
Ok. Anything you can do to relay details to me from https://ww.wp.xz.cn/support/topic/read-first-simple-calendar-support-and-troubleshooting-guide/ I’d love to take a look at.
Sorry about the crashing, but so far only a few reports (yours) and it’s hard to know what caused it. I’d love to nail this down asap though.
Feel free to email this or any private info to phil AT simplecalendar.io. Thanks.
@craigdberry and I confirmed that it’s a conflict with the major update to W3 Total Cache.
@emilyperryyoga @cheongnicole Are either or both of running W3 Total Cache by chance?
They released a major update 2 days ago, so the update timing was the same. Their update introduced a LOT of changes (first major update since 2014). More info here:
https://wptavern.com/w3-total-cache-0-9-5-packages-xss-vulnerability-patch-with-major-update
I was able to get Simple Calendar 3.1.6 working by disabling W3TCache, then enabling SC. I am going to leave caching disabled until further word on how to reactivate it safely. (Or if I have some spare time tonight I may just experiment with clearing cache and reactivating both — I’ll report here on results if that happens.
Posted over on W3 Total Cache’s forums, but it looks like they are overloaded with support from their major update, so not sure on timing.
Feel free to chime in there if you’d like.
https://ww.wp.xz.cn/support/topic/conflict-with-simple-calendar/
Have you confirmed that this continues to fail if you purge the W3TC caches? I don’t want to try that until I have the spare time to repair the breakage afterward if it fails. My proposed experiment:
1. Start with SC enabled and W3TC disabled (workaround for current issue).
2. Disable SC.
3. Enable W3TC.
4. Purge all W3TC caches.
5. Enable SC.
If it behaves as previously, wp-admin will throw a 500 on attempting to reload after step 5. So if it doesn’t, and you can reload the admin page manually without a failure, then it seems that cache purging resolves the issue.
Hello,
I am running that plugin.
I am disabling it, and waiting to here the final work around.
I REALLY appreciate all the support, and will pay for premium when I get a chance. You guys are on it.
The folks at W3TC just released an update and it’s now resolved.
@emilyperryyoga If possible could you update the star rating of your recent review since the issue didn’t stem from our plugin?
https://ww.wp.xz.cn/support/topic/worked-until-recent-update/
Thanks.
