Forum Replies Created
-
Posts
-
Hey Adam. Thanks for the note. We don’t use shortcodes with this plugin, but template tags should help you accomplish what you’re going for. Those are documented right here: https://theeventscalendar.com/support/documentation. That ought to point you in the right direction but let me know if not. Cheers!
Thanks Jeremy. It definitely sounds like something else is at play here; are you fine continuing to work with the workaround, or do you want to try the deactivation/conflict identification route again?
Hey John: just a heads up that Jonah’s out this afternoon but will be back and can address this tomorrow. Apologies for the delay in the interim.
Hey Rob. Thanks for the note. Just so I’m clear: you’re saying that you have published a series of recurring events that goes on for the next 3 years. And you’re seeing all the instances of that recurrence showing up in list view. Right?
Just wanted to make sure. Assuming that’s the case…using the default list view is always going to show all events in a recurrence pattern. (You can hide individual events from the loop via the “Hide from Upcoming” checkbox within an entry, though). As you add more events the future instances of a recurrence pattern will get pushed off the page…how quickly will depend on the loop counts you set under Settings -> The Events Calendar.
But if you have 10 series of recurring events, and have the loop count at 10, you can generally configure it so that people are seeing upcoming events and aren’t seeing something that is months/years out. You may also want to check out whether anything in our template tag documentation ( https://theeventscalendar.com/support/documentation ) points you towards a way to customize this.
We have had a few requests for functionality along the lines of what you’re requesting: a single entry for recurring events, that all instances link to. Something like this may come down the road but it’s a rather dramatic reengineering of how we’ve built things so far so it probably wouldn’t be at least until the 2.1 lifecycle.
Sorry I couldn’t offer up more. If you’ve got other questions or if I misunderstood the issue entirely, let me know and I’ll get you what you need.
Hey Chris. Any week now; should by this time next month at this point, given some of the dev roadblocks we’ve encountered. Realistically it may be a bit sooner but we don’t want to get anybody’s hopes up.
If you shoot me an email or just post here again over the coming weeks I’d be happy to keep you in the loop. I apologize for the delay so far, though.
Alright, thanks Ken. I’ll get Paul to take a look when he’s back from vacation next week too, to see if he can comment.
Hey Ken: it’s behaving as it should on my end; when I set up an event to occur in the past at a given venue, it’s not showing on the frontend venue page. Have you updated both free & PRO to 2.0.5?
Thanks Odhran! Are you referencing the title tags of the page itself, that appear atop the user’s web browser window?
Hey John. Thanks for the note – sounds like you’ve got a cool project in the works there. Would this data have to be provided via an RSS feed? The calendar does include a “full” calendar which can be segmented out into categories (each of which provide their own list/grid view). Let me know if you think that would meet your needs…if so, it’s a feature available pretty much straight out of the box.
Awesome to hear! Thanks for confirming, Maikel.
Everyone else: let us know the results of your update and whether you’re still having issues from there.
Hey all. Should be all set with this…we’ve hotfixed the issue and re-uploaded The Events Calendar 2.0.5 to WordPress.org a couple hours ago. Please redownload and reinstall The Events Calendar and you should find the issue resolved. Note that there was no change to the PRO code so you need not make any changes there.
Upon doing so, the issue should be resolved for all time zone settings regardless of whether a city or UTC option was selected from the dropdown. Please make sure to clear your cache and resave permalinks after installing the new code.
If the issue is still a problem from there, let me know your time zone settings and we’ll keep looking into it. We tested a wide variety of combinations and all worked fine. Thanks for being patient and apologies for the inconvenience so far.
Thanks, Jim.
Maikel: what are your time zone settings? We’re looking to hotfix this on the live server today, if we can figure out what’s up, but the more information we have the better. Thanks for your report.
Hi Jamie. Thanks for the note here, and for your words – glad to hear you’ve been enjoying the plugin so far. We as a team really appreciate your support.
We definitely hear the need for more randomized recurring events…that’s been one of the most requested features since launching 2.0, and we’re planning on integrating it into the 2.1 lifecycle. So there is relief in sight (if not on the immediate horizon).
It sounds like your issue is two-fold, though: beyond wanting to add independent events to a recurrence pattern, you’re looking to have the comments etc be the same…almost as if there was one entry that all the individual recurrence pattern links went to. Am I wrong there? If so let me know. Otherwise…that’s one we’ve had requested as well, but is more customized than we’ve got in the works at the time, but maybe you can accomplish what you’re going for through creative use of template tags (documented at https://theeventscalendar.com/support/documentation )?
Sorry I couldn’t offer up more. Just know that, at least on the recurrence flexibility front, we are working to provide a solution for users in your position. If we can do anything else or if you have any other questions just holler. Thanks again for your support!
Got it. I’ve sent this Jonah’s way and he should be commenting when he hits the forums next. Thanks for being patient, Tom.
Hey Jim: that’s odd…we’re unable to recreate that on our end with the default 2011 install, the latest WP and the 2.0.5 code for both free & PRO. If you want to send an email to pro (a) tri.be with a set of backend credentials we can take a look at why this would be happening.
Since the bug was just introduced/discovered yesterday, we aren’t quite ready with a fix. Should be shortly though.
