Error: Published event pages are displaying as venue pages

[girlswritenow]

We use the Events Calendar (not PRO) and the Eventbrite ticket plug in on our website. I am encountering a very weird problem where when you click on an event listing, it takes you directly to the venue entry for that event’s venue instead. I can still see the events in the WP admin view, but when I click “view event” on the edit page or try to go directly to the URL for an event, it takes me to the venue instead. For example if you view our calendar (http://www.girlswritenow.org/events/) and hover over the event on March 22, the URL is supposed to be http://girlswritenow.org/event/marchchapters. But when you click on it, it takes you to http://www.girlswritenow.org/venue/the-scholastic-auditorium-5/. I don’t know how to resolve this? Please advise!

I checked the forums and found a thread which describes a problem I had previously noticed as well (https://theeventscalendar.com/support/forums/topic/eventbrite-error-venue-name-already-exists/) — that when I added an event on EB and tried to export it to WP, the error message “Venue name already exists” popped up. Everything still seemed functional so I just moved on anyway but FWIW, thought I would mention it here.

Appreciate any help you can give — we’re hoping to send an email to our network on Monday advertising the March 22 event with a link to the page on our site, and need help fixing this ASAP. Thanks!

[Barry]

So this looks to me rather like a caching problem.

If I try to visit http://www.girlswritenow.org/event/marchchapters/ it redirects, incorrectly, to a venue page as you’ve noticed. But if we add some random values in the form of a URL query, like this:

http://www.girlswritenow.org/event/marchchapters/?avoid=caching&random=2314213

Then hopefully, as I did, you will see the correct page.

On the caching front I can see that you are using W3 Total Cache and also Cloudflare. My hunch is that this is an issue stemming from W3TC rather than Cloudflare, but that’s just a hunch.

In the first instance I would suggest adding exceptions so that event/venue pages are not cached. If you can’t solve it that way – or even by turning off W3TC – then you may also need to look at and tweak your Cloudflare settings.

Hope that helps 🙂

[Author]

Posts