Based on some of the forum issues, this was a poorly tested and implemented update.
Oh definitely not, we spent at least a month testing, probably more. The problem comes with the variety of themes, plugins, servers, etc that can all be different. We do have a few issues though, but we are taking it all in and working to get them fixed as soon as possible.
Did the update we just pushed today to 3.0.2 help with any of your issues?
Oh definitely so. 😉
Having now tested grouped calendars on 2 different themes and sites, HTML parsing on the same, and seeing the other issues – many with fundamentally basic features germane to the functionality you promote, I’d say it was a less rigorous beta test than you believe.
I use few plug-ins – and only those common in the HUGE majority of WordPress sites. I also disabled them just to test the grouped calendar timezone issue.
Don’t get me wrong.. I’m using a free plug-in. It’s annoying but not disastrous. If I were paying for the premium, it would be unacceptable, however.
I develop software and I appreciate the complexities you are dealing with. I’ve released an upgrade or two over 20 years that was similarly problematic.
But I learned, when key features fail in a production release, better to admit it, fix it, and move on. Such is the life of software development.
For my part, I’ve simply had to strip HTML from the description and provide links to two distinct calendars. Again.. annoying but not disastrous.
I look forward to the future fix.
So did the update to 3.0.2 or 3.0.3 help with any of this?
Also, what are your timezone settings on the grouped calendar vs the individual calendars?
Timezone is working – for PST.
I had the timezone set to use the “Event Source Default”. I’ve set all 3 calendars – the two I’m grouping and the group calendar itself, to use the theme’s timezone because the events listed are in LA.
However, I speak and perform outside of PST. I am curious how that will be impacted. When I have some time, I’ll create some out of state events – different timezone – and test it.
Unfortunately, html=”yes” in the description, still doesn’t work.
Unfortunately, html=”yes” in the description, still doesn’t work
Any change in the latest version (3.0.9)?
If not then what is not working about it?
Sorry.. just added items. It is working now.
