- This topic has 11 replies, 2 voices, and was last updated 12 years, 3 months ago by
.
-
Posts
-
Example: http://ncmf.pricelessmisc.com/event/grace-potter-the-nocturnals/ oOr practically any event currently loaded on this site)
Any ideas on how to prevent this? Otherwise I’d prefer just to not have the related events at all.
Hi Justin – I can’t seem to replicate the same behaviour which is definitely not desirable … and we actually have code in place to prevent the same event being returned as part of the results.
Is it possible this is a conflict (whereby another component is modifying queries)? If you deactivate all other plugins and switch to a default, unmodified theme such as Twenty Twelve does the same thing occur?
Yes, I’ve just de-activated all other plugins, and reverted to the Twenty Twelve plugin, and the issue persists.
I’ve also just tried replacing the the-events-calendar and events-calendar-pro plugins w/ freshly downloaded copies, just to make sure there were no inadvertent changes made during development that could cause problems, but this did not resolve the issue either.
If it would help, I can give you (or someone) access to this site’s wp-admin. It’s only a development copy.
Sure, certainly wouldn’t hurt – we might be able to see something in your event data to help us replicate in a clean environment. If you could share your credentials as a private reply that would be great.
Thanks!
I’m not seeing any obvious cause of this, my test data pretty much replicated what you have in place there.
Unfortunately we haven’t heard any other reports of this whatsoever and, at code level, I do see that we’ve got an explicit clause in place to prevent this. All very strange.
I do also appreciate the offer of repo access – but it is equally possible that this issue resides in the database somehow.
A worthy test could be to establish a completely new WordPress installation and start off with only our plugins – build a set of comparable test events (with categories etc) and see if the same issue manifests itself. If it doesn’t then you could basically reverse the same troubleshooting step and build things up by adding all of the components that live on the dev site. Ultimately, that will either isolate a conflict or – if you can’t replicate – would strongly indicate that something has somehow become corrupted in the dev site database.
Is it possible to explore that idea here?
It may be an issue w/ the database, considering the same database has been running one version or another of your events plugin since like 2007.
I’ll have to do more testing.
- The topic ‘Related events shows the same event currently displayed’ is closed to new replies.