Well, the full calendar shortcode was not loading for non logged-in users so I had to revert to the previous version. “Loading” would display perpetually. I don’t see any problems in my access or error logs to provide any useful information.
Hi, sorry to hear you’ve had problems with 3.0.0. Unfortunately I’ve not been able to replicate this.
The buttons should have been styled by the plug-in stylesheets. You might have problems then if you’ve disabled the plug-in stylesheets (but looking at your site, it doesn’t look like you’ve done that, so that probably isn’t the cause).
Did the events render ok?
I appreciate you won’t want to debug using a live site, so if you have a test site where you’re experiencing this problem, please do let me know.
Events rendered fine and feeds still worked. The full calendar shortcode worked for logged in users. But as I couldn’t immediately discern any issues and, as you mentioned, I’m loathe to experiment on a live site, I’ll just be content with the old version.
Ah so, it was only logged-out users? … and you have a caching plug-in installed. A bit of stab in the dark but did you clear the cache after updating the plug-in? I wonder if the old stylesheet was cached and applied to the new calendar, perhaps.
It was logged-in users for the missing arrows too but logged out for the events not loading. So the cache would explain the latter but not the former… under usual circumstances. I probably won’t get to it today but I can have another stab sometime in the next couple of days at updating to 3.0 again and testing your hypothesis. I’ll update then.
Thanks,
If you right-click > inspect element, you’ll be able to find the mark-up for the buttons and look at what styling is being applied. You should find the following (displays ‘back’ arrow):
.fc-icon-left-single-arrow:after {
content: "2039";
font-weight: bold;
}
If you’re happy to send me a copy of the theme I’d be happy to confirm/rule-out a theme conflict. Just get in touch via http://wp-event-organiser.com/contact.
Yeah, that’s the problem though. With 3.0, there was no lt or gt code in the span. When I viewed the source, it was blank.
It won’t be, it’s applied (by the stylesheet) as content in the :after
