Forum Replies Created
-
Posts
-
This still shows in progress on known issues section and there was no update to the Pro plugin. Can you please confirm this issue was resolved before I try updating AGAIN? I can’t be using my client’s websites to experiment. I need to know for certain. This issue has already caused me enough problems.
Giving up on any hope this will get resolved – support for this plugin has gone downhill rapidly. Not cool.
I had to update all event timezone to UTC-5 to get them to show properly. Unfortunately I cannot leave errors online.
I was never able to get this fixed. I cloned the theme on a new install and added the same plugins one by one. That seemed to resolve the problem. Thanks for trying though!
I also tried changing limit to 4096M. When I do that, I receive this message: “Connection lost. Saving has been disabled until you’re reconnected. We’re backing up this post in your browser, just in case.”
And then page then redirects to https://thaliaumc.org/wp-admin/post.php (404 Error)
Was able to get messages to display and receive this:
Allowed memory size of 536870912 bytes exhausted (tried to allocate 82 bytes) in /home/offixo6/public_html/thalia/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence.php on line 93
I tried increasing the memory limit to 512M, 1024M, and 1G. None of those worked.
No debug messages were shown and no log entries were created. I just get redirected to wp-admin/post.php when updating or adding a recurring event. Single events still work fine.
You are not seeing the error because your test event did not begin before DST ended, which was on November 5. This issue impacts recurring events that started BEFORE November 5 and continue after that date only. As I mentioned in the my last reply, events that begin after November 5 are OK.
I’d rather not use UTC either! That’s the problem! It is the ONLY way the correct time will display on the calendar, so I am left with no other choice at the moment.
I have already sent system info and completed testing before submitting the original ticket, which seems to be an issue with many other users as well. It is clearly not an isolated incident. There are no other errors on the site.
The only way I could get events to display correctly was to make them UTC -4 and in TEC settings use sitewide, not local. This is going to be a problem because this spring I will need to back and change all recurring events again, since they will be off an hour then too when DST starts.
For example, the screenshot attached shows an event that actually starts at 9:30 AM, but since it started before DST, the time shows an hour ahead now. The ONLY way it will work on the calendar is to keep it like this and use UTC-4. Any other configuration throws it off an hour.
Is there going to be a fix for this bug or do we need to rely on these workarounds? If the latter, I need to look for another calendar solution because this isn’t good.
