Forum Replies Created
-
Posts
-
I should add to the above that you’ll want to copy everything from the original venue.php file before commenting out the line, which is located in plugins/the-events-calendar/views/modules/meta.
Yes it does. Thanks!
For the record, a change like that probably should have been shared. Many of us have done cool stuff that works with ECP, but that stuff starts breaking inexplicably when a major object structure changes like that. 🙂
This should give you an idea: http://plugins.svn.wordpress.org/meta-box/tags/4.3.8/inc/meta-box.php
I hear your skepticism, but this was working fine prior to the recent round of ECP updates, which obviously had a major bug with saving recurring events.
So, the code above was run and successfully saved post meta on a recurring event?
Hey Barry,
I appreciate that, but it’s most definitely a bug with ECP, interfering with a very simple, common customization.
Here’s enough of the plugin to see what’s happening: https://gist.github.com/logoscreative/7daa90a4507eb53eab08
It works on top of the Meta Box plugin.
Again, I’ve been able to isolate this to recurring events only, with the default theme enabled and only the TEC and ECP plugins enabled, along with this meta box.
I’m still having this issue when I edit a recurring event. The clean up script mostly works, but goes right back to creating a ton of instances the next time the event is edited.
Barry, I still saw them even after clearing filters.
So far, the fix for us has been to edit the event, add something like a space at the end of the content, and save again. The issue is having to hunt them down and do that for each one.
A change in event recurrence (we think) caused the event to replicate over 300 times, and they also didn’t want to be deleted. I’m having to go in through the database now.
The event slugs are coming out looking like event-name-2014-09-01-2014-09-01-3-2014-09-01-2014-09-01-2014-09-01-2014-09-01-2014-09-01-2014-09-01-2014-09-01-2014-09-01-2014-09-01-2014-09-01-2014-09-01-2014-09-01-2014-09-01-2014-09-0-95
Anyway, back to my original question, because I figured this would happen: can I disable AJAX in that view (or all)?
That’s why I qualified my help for debugging in the original thread. 🙂
The theme developer won’t be helpful. I’ve already switched of script debugging, and it didn’t seem to change anything.
I didn’t explicitly mention: I know it’s a theme issue because I switched to a default theme and it worked.
Thanks, Rob. I’m going to email you, but I wanted to leave a public response that this very much satisfies my requirements for the time being. I appreciate your transparency, insight, and assistance.
