Support

January 3, 2023 at 5:22 am

Hi Debbie,

What you’re describing is usually what happens when ‘something’ forces permalinks to flush at an unexpected point during the request. So basically WordPress then generates it’s “pretty” permalink rules (which make say /events/some-event/ work) WITHOUT Event Espresso having the chance to hook in and say ‘include /events/* in permalinks’ within those rules (I’m simplifying this a lot to the help explain but that’s the general idea).

De-activating and reactivating Event Espresso will force EE to call a permalink flush again, which then fixes the problem but there is also an easier method.

The next time this happens go to Dashboard -> Settings -> Permalinks.

Don’t make any changes and just hit save. That will flush your permalinks again.

Does that fix the problem at hand?

—-

Now, I’m not saying that’s your solution here because obviously, we don’t want the permalinks to stop working in the first place… but, if the above fixes this the next time it happens it confirms its an issue with permalinks and then we can try to troubleshoot those further (we’ve seen this before, it’s often a plugin calling to flush at some point but it could b any code and is often hard to track down).

January 3, 2023 at 12:50 pm

I’ll give you the next step for this just incase, you can apply it now if you like but it may turn out to be unrelated.

The snippet in this file:

https://gist.github.com/Pebblo/a6d2b949d0ae784c09de442b9848ff7d#file-1tw_log_rewrite_rules_array-php

Writes a log entry each time the permalinks are flushed and more importantly outputs the track trace for what called the flush. So if you have the above code in place and its writing to the log file correct, the next time it happens, if the above permalink fix I mentioned works the log file may show some clues as to why it happened.

You can add that to a custom functions plugin on your site, we have some documentation on creating one here:

https://eventespresso.com/wiki/create-site-specific-plugin-wordpress-site/

January 5, 2023 at 5:20 am

Are you comfortable with FTP/File Manager?

If so, open up your sites wp-config.php file and find this line:

define( 'WP_DEBUG', false );

Replace that single line with this snippet:

https://eventespresso.com/wiki/troubleshooting-checklist/#wpdebug

That tells WordPress to log errors on your site.

You have my custom function in a plugin and it’s activated, correct?

After you’ve changed the above, do the Permalink settings again and hit save.

Let me know and I’ll confirm if the log entries are being added.

January 9, 2023 at 4:26 am

Ok, so it relates to the login requests on your site.

First, try adding this to your site:

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

Once that’s been added, delete the log file from above (I have a copy of it) and let’s see if this happens again (a new log file will be created the next time the function writes to it).

January 10, 2023 at 3:33 am

Just checking in to see if you’ve had any further reports of this?

Looking over the logs it would appear not but just checking.

January 10, 2023 at 4:54 am

OK, so a quick explanation of what the above did.

We don’t run all of Event Espresso on every request so we monitor the request types and basically drop out of it if it’s nothing to do with EE. The snippet I gave you removes the check for the login requests and runs EE in the background of those.

Something is flushing permalinks on those requests and becuase EE is dropping out of them, you get the above. Let’s see if it continues to work as is for now, I’ll investigate a little further if that’s the case.