Forum Replies Created
-
Posts
-
Thanks for the note Jesse. There has definitely been a demand for this and since we’re planning on beefing up the venue pages in the 2.1 lifecycle anyway, this will likely be one of the changes that comes about during that.
Hey Robert. Thanks for the note here, and sorry that you’re having issues. The plugin will create a different event entry for each day you’ve set it to recur. For example if I have a series that recurs 15 times, I’m going to have 15 different entries (rather than 1 master entry where everything is contained). Each entry represents a different day. You can make changes to one and have that carry over to all after it, or can break that event out into a stand-alone (non-recurring) event as you see fit.
That help? Let me know if not and I can provide further elaboration as needed. Cheers!
Received, thanks. I went in and took a look around this afternoon and a few points on this…
The Events section is, overall, running extremely slowly. When I clicked into the “Events” list from the admin it took upwards of a minute just for anything to happen, when clicking into the other sections there was relatively snappy. I would wager that side has something to do with the number of events you’ve got in the system…we’ve been receiving reports that sites with thousands of events have been slowing down, and have verified / are working to fix that for 2.1. At this point there is no solid solution though, unfortunately.
The fact that there are 34 thousand + items in the Events trash also could be cause for concern. I would suggest wiping that, and if possible testing on another similar environment without as many events (try keeping it under 500) to see if the issue persists. Please also try editing a non-recurring event to see if the problem happens here. I’m wondering if it’s just slow loading for the events overall that is causing the issue, and keeping it hanging on that update screen accordingly.
Thanks Matthew. Apologies for the inconvenience in the interim.
Multiple possible solutions for you there, Robert 🙂 Want to give one/each of them a go and let us know if it resolves this issue?
Hey John. Thanks for the follow-up, man. I just responded to your email a few moments ago. Let’s keep the discussion going there 🙂
Thanks for the heads up, guys. Let me see what Jonah has to say when he hits the forums this morning. Stay tuned.
Hey Robert. Thanks for the note here. I believe this is doable, but am not positive…I’ve asked our dev Jonah (more knowledgeable at such issues than myself) to chime in directly when he hits the forums today. Stay tuned.
Hey Christopher. Thanks for the suggestion here. This is definitely on the radar in the form of our Community Events add-on: https://theeventscalendar.com/shop/wordpress-community-events/. That plugin (along with the Events 2.0.6 code required to run it) should be out at the beginning of next month.
Hope that helps! Let me know if you have any other questions here. Thanks again for your interest.
Hey Carlos: we have had a few users report this, and the solution has generally been different for each of them. But a good starting point would be Tony’s suggestion above. Want to give it a go and let us know the results?
If that doesn’t do the trick, please try the deactivation route (plugins + theme) and let us know if the issue persists with no other plugins/just default 2011 theme active. We’ll do what we can to assist from there.
That’s an interesting issue, Lydia. What level of user are you (admin or lower)? Have you created a custom role that you could be logged in as?
I’d check re-saving your permalinks, and then giving it another go as well. Let me know what that yields and we can keep trying to troubleshoot from there. Apologies for the inconvenience in the interim.
Lydia: Henry’s suggestion above should be spot-on. Want to give it a go and let us know the results?
Hey Micah. Thanks for reaching out. Not sure about this myself, but our dev Jonah may have some ideas. I’ve asked him to take a look when he hits the forums later today…stay tuned.
Hey Alex. Thanks for the follow-up here. Not sure how this one slipped through the cracks as we check the forums daily 🙂 Either way, my apologies for the delay.
There is a changelog included in the readme.txt file, and we publish one as a blog post here on the tri.be site as well each time a plugin is released. But if you copied your files over to that ‘views’ folder your changes shouldn’t be lost upon update anyway…the advantage of that template override procedure is that you can update the core plugin without your changes being lost. And as long as it’s not a major update like pre 2.0 -> post 2.0, there won’t be major changes to those templates on a core level anyway.
That help, or have I misunderstood your question here?
Hey Matthew. Thanks for the follow-up; we hit the forums daily (except weekends) so it looks like this slipped through the cracks.
As this is obviously not a core behavior of the plugin, something else is at play here. If it’s not a plugin conflict my guess is that it’s almost certainly an issue with the theme. Want to set me up with an admin account so I can attempt to recreate the problem myself? I didn’t see a “Create” link on that page you sent me to, but if you can do that today I’ll be able to take a look this afternoon to see what can be done. (I’m not going to change anything on your site; will just be looking around the backend). If you set me up with an admin account email the creds to pro /a/ tri.be. Thanks!
