Forum Replies Created
-
Posts
-
Hey Timothy. A couple users have reported this; we’re still looking into what is causing it. We’re hoping to have a fix for this in an upcoming release, either 2.0.3 (coming Monday) or 2.1 (coming shortly thereafter). Any chance the different templating options under Settings -> The Events Calendar can get this working for you in the interim?
Hi nakturnal. Thanks for the note; sorry to hear that you’re having issues here. Let me see if Jonah can identify what’s up here…though it’d be helpful to have a link to your site as well, if possible.
Ah, excellent to hear. Thanks for confirming Caleb…this will be useful to others who come with the same issue.
This is great to know. Thanks Jonny; let me get this in front of one of our devs so they can identify what’s up and we can get this patched for our next release (probably will be 2.1 at this point, since 2.0.3 is in a code freeze as it’s practically done). Appreciate you guys bringing this to our attention.
Hey Michael. Thanks for the note. If I understand your issue correctly, it’s the same one that we’ve identified as a legit issue (fixing for 2.0.3) and have put up a patch for in the interim: https://theeventscalendar.com/patch-for-the-events-calendar-2-0-2-date-bug/.
Does that help? Or have I misunderstood the issue here? Let me know.
Hey Jamie. Totally! Sorry to hear that the integration process would be against what this client wants; totally understandable though. If you have the client’s Tri.be receipt (or Paypal receipt) handy and want to shoot that over to rob at tri.be, I can get going on the refund process for you.
Hey Eric. Not that we’re aware of, no – but that being said we haven’t tested the plugin on that theme so it’s possible there will be CSS issues that need addressing. Remember that right off the bat, you can help dictate the plugin’s appearance by trying out the different templating options under Settings -> The Events Calendar.
Let me know if upon installing, you have any particular questions/issues and we can take a look. Thanks!
This raises a good point. Thanks for confirming, Tony — I’m no SEO expert either but I can see the issue. Let me run this by the team and see what they think. Appreciate you bringing it up…my guess is that if we can all come to a consensus on it, this will be changing for a future release.
It’s definitely possible; we noticed a number of things broke when the switch to WP 3.3 happened so I would not be surprised. I’d actually just activated 3.3.1 on my site when I tested your issue so I’m not sure I have a pre-3.3.1 environment to test on at this point. Any chance you might?
We should be able to identify the cause either way, so it’s not a huge deal. But would be good to know going into it if there was an easy way to do so.
Hey guys. No prob; we were a bit backlogged on support today but will have a response to this tomorrow morning.
Hey Cary. Just WP access would be fine to start with. Hopefully we could identify the issue from there.
Tony: Thanks for confirming. The reasoning behind making the eventless-days clickable (and we went back and forth on this internally) is because from a usability standpoint, it felt weird having certain dates clickable and other ones not. We could have had it all one way or the other; but since we wanted to include Single Day View as a PRO feature (because a lot of users had requested it), we opted to have all days become clickable. That way there can be no confusion in a frontend reader’s mind whether events are taking place on a given day or not – if not, it’ll clearly tell them as per my previous screenshot.
You raise a good point on it, though…if it’s creating an issue for users we may have thought too much about it. Is the general consensus on here that it’d be preferable to not have this?
Hey Jeremy. This is a good question; I’m not sure what’s up here, but maybe Christina will be able to share whether she had a related experience/resolution?
Hi Jamie. Thanks for the note; generally since 2.0 went live, we haven’t been spending any QA time or resources testing against the 2010 theme because it’s since been replaced by the 2011 theme (which has become the standard for fresh WP installs across the board). Is there a reason your client hasn’t upgraded to the 2011 theme? My guess is that right off the bat, the majority of your issues are related to that. It is also possible that there is another plugin conflicting…although that’s not as likely as the theme issue, it’s worth knowing what other plugins you’ve got active and whether you have an environment to test this with no other plugins active.
On the specific issues you noted:
1) Can you elaborate on this? Is this the start time issue, or something else?
2) This is not an issue that we’ve had reported yet; my guess is it’s related to my point above.
3) Ditto #2.Hope this helps. Let me know whether you’re able to upgrade the theme to 2011 (or even, just revert to the basic 2010 without your modifications to see if they’re conflicting) and if the issues persist. Apologies for the inconvenience in the interim.
