[Geoff]

Awesome! Thanks for confirming. 🙂

I’ll go ahead and close this thread but feel free to start a new one (and link to this) if you happen to find any conflicts in the Twenty Fourteen theme. I wasn’t able to recreate the issue myself, but I’d definitely want to look into it more if you are able to!

Cheers,
Geoff

[Geoff]

Thanks for chiming in here, @Michael! Anna, does switching the display to the Default Events Template in Events > Settings > Display help at all?

Let’s try that before connecting with the host. 🙂

Geoff

[Geoff]

Cool, let’s do that. Earlier in the thread, I provided a link here:

https://theeventscalendar.com/support/documentation/troubleshooting-404-errors/

Did you follow all of the suggestions outlined there? Just making sure because I’ve found that most 404-related issues are covered in there. If the issue continues from there, then we can do some deeper troubleshooting.

Thanks!
Geoff

[Geoff]

Ah, it looks like the CSS worked, but there’s another element to hide:

.aes label {
display: none;
}

You can send a screenshot using a service like: https://cloudup.com/

Thanks!
Geoff

[Geoff]

Geez, this is a head scratcher!

Here’s what we know so far:

• There are no pages that use the /events/ slug in your admin that would cause a conflict
• The issue pops up when using The Events Calendar 3.10 and 3.11
• The issue pops up in the theme you’re using but not TwentyThirteen
• The theme and plugins have worked together in the past

These symptoms are typically the result of customizations in the calendar or updates to the theme, but we’ve ruled those out.

How about when all other plugins are deactivated? It’s another long shot, but just want to make sure we’re covering all our bases.

If the issue continues without plugins and nothing else has changed with the theme or customizations to the plugin, then the next target would certainly be the host. Are you able to send an inquiry to see if anything has recently changed on that end? Sorry to put you in a position to chase answers, but I’m really at a loss since we’ve ruled so many other possibilities out.

Thanks for your help!
Geoff

[Geoff]

Hi Hasan and welcome to the forums!

Thanks for bringing this up. Just to be clear, is this only affecting your installed theme or do you see the same issue when using a default WordPress theme as well? I only ask because we did make some updates to classes from 3.10.1 to 3.11 that may impact some themes, but we haven’t been aware of an issue that affects all themes globally like this.

Geoff

[Geoff]

Good question and sorry about that! It’s over here:
https://wordpress.org/plugins/the-events-calendar/developers/

Geoff

[Geoff]

Hi Karen, and welcome back.

That’s interesting! By chance, does the same thing happen when you switch to default WordPress Twenty Fifteen theme?

If it does, then I definitely want to check that out a little deeper. Either way, we can still hide that with some CSS in your theme’s style.css file:

#tribe-not-title {
display: none;
}

Also, is there a way to not default to the first user alphabetically in the list for submitted events that are not logged in? How do I fix that?

Will you please you send me a screenshot of that? I think I get what you mean, but want to make sure I’m looking at the same thing you are. 🙂

Cheers!
Geoff

[Geoff]

Thanks so much, Anna! Whittling this down to a theme issue is a HUGE help.

I wonder if one of the recent updates to the theme is conflicting with the most recent 3.11 updates of the calendar plugins. Are you able to try downgrading The Events Calendar and The Events Calendar PRO both to 3.10 to see if the previous version is still compatible with existing theme?

Thanks!
Geoff

[Geoff]

Thanks for following up, Bob!

Are we only talking about a 404 issue now, or is the 500 error still something we need to tackle? Just want to make sure I’m looking at the correct issue. 🙂

Thanks,
Geoff

 

[Geoff]

Sure! I think we could hide that extra information by adding this to your theme’s style.css file:

.tribe-events-calendar td .tribe-events-event-meta {
display: none;
}

Let’s give that a shot and see if it cleans things up the way you’d like. 🙂

Cheers!
Geoff

[Geoff]

Thanks! I do see that ticket logged in our system, though it hasn’t been slotted for a specific release just yet.

I’ve noted this thread in the ticket as well, but please do keep your eyes open on the other thread since we will likely follow up directly there when we have more progress to share. 🙂

Cheers!
Geoff

[Geoff]

All very good questions!

This may be a bit of a long shot, but will you please try the first suggestion in this tutorial? I have a very slight hunch this could be related to the need to flush permalinks, but that might be a stretch. Still it doesn’t hurt to try before getting knee-deep in something else!

The very well could be an impact with managed hosting since automatic updates are often a bundled feature of those packages. If the steps above don’t work, then I’m inclined to say we should test on a fresh site and see if we can replicate the same issue. I can walk you through that, so no need to do anything until we’ve tried the permalinks route.

Thanks for your patience while we figure this out!

Geoff

[Geoff]

My pleasure! Thanks again for getting in touch and hope you keep enjoying the calendar. 🙂

Geoff

[Geoff]

Good question! I tried digging around a bit and couldn’t find that exact issue on the forums or in our system. If you point me to what you saw, I might be able to confirm that for you.

Thanks!
Geoff

[Author]

Posts