The topic ‘Tribe Rewrite Issues causing 404s’ is closed to new replies.

Hi @killsparrow

Thanks for reaching out, and my sincerest apologies for the inconvenience.

The thread was closed by the moderator due to multiple users reporting the same issue on a single support thread.

If anyone needs support for this plugin then per the forum guidelines please start your own topic.

With our latest release of?The Events Calendar 6.2.1,??we have added some fixes to prevent the 404 errors.
?
We recommend that you update both plugins to the latest released versions.
?
As always, we suggest testing updates on a staging site first and having a recent backup, but it should all be smooth sailing. You can remove any workarounds after updating the plugins if you implemented them.
?
Let me know how it goes.

Hi @d0153,

Can you confirm that your team was able to replicate the issue, understood the problem and fixed it?

The issue everyone was experiencing, was that the plugin was rewriting permalinks and leaving out all the other custom post type permalinks, causing those posts and archive pages to 404. Obviously saving permalinks would fix, but this wasn’t doable 5+ times a week with an unhappy client.

Most importantly this would only happen in production. It never once happened in staging, dev or locally. So testing in dev or staging isn’t an option.

We have already removed these plugins and started a custom build – but using this plugin we purchased would be easier – however I cannot risk putting the plugin back up if it will go down again without a clear answer as to what the issue was and how it was resolved.

Thank you.

Hello @killsparrow,

Thanks for your reply.

Yes. As Darian mentioned, the issue was fixed in version 6.2.1 of the plugin. You can find it in the released note he shared – https://share.getcloudapp.com/4guRzjNn.

Simply update the plugin to the lastest version and that does the trick. You can as well test it in a Staging Environment if you have any.

I hope that helps. Please let me know if you need anything else.

Hi @d0153 and @frankremmy ,

As mentioned before, we have a staging env, but the 404 only happened in production.

Everyone experiencing the same issue (only happening in production for everyone), are no longer reachable because the thread was closed. This is frustrating for me, because I can no longer communicate with all my peers having the same trouble.

Do you know if this recent fix has resolved the issue for everyone else on the old thread who experienced CPT going down ONLY in production?

Because the issue only persisted in production – testing in stage or dev is useless.

Thank you.

Hi @killsparrow

I just checked Forum threads and Help Desk tickets experiencing the issue, and none of them confirmed or replied after we sent an update that the fix is out.

Could you try creating a staging version of your live site using the WP Staging, and see if you can replicate the issue from there? The staging site should be created on the same server as your production server.

If you can replicate it from the staging site, please try updating your plugins and check if that resolves the issue.

Let me know how it goes.

Thank you @d0153 – we had been experiencing the down CPT(s) for close to a year before we removed your plugin to fix the problem. We eventually found that other people were having the exact same problem (before the thread was closed), and it has been made clear by many (not just us), the 404s only happen in production, for some reason. We have local env, dev, staging, all with close to, if not the exact same environments. Only production would go down consistently. We never once experienced the issue outside of production (WP Engine, GES, Multisite).

If we decide to put your plugin back up, I will let you know how it goes – but that is up to the client.

It is a bit backwards that the last thread was closed were there was an actual community of people having the same problem – and now we can no longer communicate.

Hi @killsparrow

Thanks for your response.

A customer responded that they had experienced the same issue, but confirmed that the latest version has resolved the problem.

Please let me know if you encounter further issues after updating your website.

Hi @killsparrow

This thread has been inactive for a while, so we’ll go ahead and mark it Resolved. Please open a new thread if any other questions arise, and we’d be happy to help.