Support

July 22, 2020 at 8:49 am

Hi there,

Go to Dashboard -> Settings -> Permalinks.

You don’t need to do anything there as loading the page will flush your permalinks but you can hit save to be sure.

Do the events then use the courses slug?

July 22, 2020 at 10:01 am

Usually, it means something forced permalinks to flush at an unexpected point in the request when EE’s rewrite rules have not been added.

For example, we’ve seen something similar happen when the permalinks are flushed on the login request. EE doesn’t run on that request and so doesn’t inject it’s rewrite rules.

I would leave it as is and check if it happens again, if so, you can try adding this to the site:

https://gist.github.com/Pebblo/fd47c19d038ec7b5ce0aa397ba2aacc4

Which basically tells EE to run on the login request.

Then if it continues to happen with the above code in place we can work through some additional troubleshooting steps to narrow down what is doing it. That involves adding some debug code to the site which write a log entry each time the permalinks are flushed with a stacktrace to view what called the flush.

July 27, 2020 at 1:01 pm

This happened again… did the permalink thing and the event loads now but still has the espresso events slug, instead of the courses one we set.

Is ‘courses’ still set as the slug in Event Espresso -> General Settings?

I added that code snippet in as well, but we need some kind of a permanent solution so this doesn’t keep happening when people are trying to register.

I can’t give you a solution as I have no idea what is causing it, the snippet I gave you tells EE to load on the login requests as we’ve seen it happen on those but depending on your plugins it could be happening on something completely different.

If you add this plugin to your site:
https://gist.github.com/Pebblo/a6d2b949d0ae784c09de442b9848ff7d

Then add this code in your site’s wp-config.php file:
https://eventespresso.com/wiki/troubleshooting-checklist/#wpdebug
(replace the single line define( 'WP_DEBUG', false); with the above snippet)

It will log any requests that call to flush permalinks to a log file we can view to see if it shows any further clues on what is causing it. Again, none of the above will fix/prevent this from happening but should help identify why it is happening the next time it does.