Forum Replies Created
-
Posts
-
Yours is in the next batch that we’re currently working through, as a heads up. Answer forthcoming 🙂
I’ve got a developer looking into Myriam’s initial request now. Will let you guys know what I hear back; we may just need to change the language files for the next release.
Hey Al – I tried to access the file at that link, but it appears to be gone. Can you drop it into http://pastie.org/ or somewhere else where I can take a look?
Hey Adam. Sounds like you’ve got this answered based on the email exchange with Nick, correct? Just want to make sure.
Hi there Denyce. Thanks for the note; apologies to hear you’re having issues. My guess is you had that item added to the header menu in 1.6.5, and what we’re seeing there is a carryover from that? In the 1.6.5 release events were just a category under the regular posts section; in 2.0 they’re a custom post type entirely. As a result you should be able to fix that by just going to Appearance –> Menus and changing the header link to events from /category/events to just /events, and it’ll carry over fine.
Let me know if that doesn’t work for you and I can keep troubleshooting. Cheers!
Thanks for this report, Bob – you’ve provided exactly what we need right off the bat, and this is a model of a perfect bug report. Thank you.
The issue you’ve reported here has been recreated on our end and is verified as a legit bug; we’re working now to fix it for the 2.0.2 release. I should note that based on what we’ve seen so far this is only occurring if you’re using the default page template with Headway. If you go into Settings -> The Events Calendar and change to the default events template, it should resolve this issue and can work as a temporary fix until we’re able to get a patch deployed.
Thanks again and please let me know if you have other questions about this.
Excellent to hear you figured this one out, Andrew – sorry that you had to do so on your own 🙂 If anything else arises going forward let us know and I’d be happy to look into it for you. Cheers!
Hi David. At this point, the events don’t integrate with our geotagger plugin or any others that exist out there (to the best of our knowledge anyway). We’ve got updates to the WP Geo Tagger on our radar for once we wrap up addressing 2.0 ECP bugs, but that hasn’t been officially scheduled yet so I’m hesitant to give a timetable for when you can expect it.
Since events are a custom post type, it’s possible the dev behing wpgeotags would be able to suggest ways to integrate events. I’m not aware of any method offhand unfortunately. Sorry I couldn’t offer up more here.
Thanks for sending over those creds. I was just able to verify this; it’s an issue another user reported too. A temporary workaround, until we can get this patched for 2.0.2, is just to use the Default Events Template (under Settings –> The Events Calendar) instead of the Default Page Template. Looks like this is only impacting the Default Page Template and I’ve just confirmed that to be the case on your site.
Sorry about the inconvenience in the interim. Luckily right now the Default Events Template looks fine on your site so that should be OK to use in the interim.
Hi Cindy. Thanks for the note on this. I will say that this is definitely designed to be run on at least the 2011 theme; we stopped supporting the 2010 theme at the end of the 1.3 lifecycle and haven’t been running 2.0 on that since 2011 theme was launched with WP3.
The next/previous event issue is a known bug; it seems to only occur with recurring events, best I can tell, but let me if you’re seeing something else. This is an issue we’re working on but have had some trouble nailing down (it looks simpler than it is). As soon as we can patch it the fix will definitely be deployed though.
That point you brought up about the organizers is a valid one; a truly legit bug that I’ve logged so we can fix in 2.0.2. Thanks for pointing that out.
The recurring events are meant to function exactly as you described: the “end on December 18th” should mean there’s a final listing on the 18th; the fact that there isn’t is a bug we introduced in 2.0.1 it looks like, since I was just able to recreate it. Sorry – we’ll get this patched too, for the 2.0.2 release.
That last request you noted was actually posed by someone else just earlier today. I’ve got it logged so we can address that down the road too.
Thanks for all your suggestions and let me know if anything else comes up!
Excellent. That’s extremely helpful; thanks for the follow-up. It definitely doesn’t sound to be behaving as it should.
Ah, gotcha 🙂 Thanks for confirming. If anything else comes to light, drop me a note and we’ll check it out for you.
Thanks for pointing that out, Roberto. We encountered a similar issue on our dev site and our developer noted the following:
“The issue is that the plugin was installed in a directory with a space: “Events PRO”. This works fine for just code, but gets screwed up when enqueuing CSS/JS resources, since WP strips all whitespace out of URLs in its script+style management. So, as long as the user is installing things in a proper dashed or underscored directory, things will work just fine.”
Changing that fixed the issue on our end; might it be the cause of yours as well?
