killsparrow

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 @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 @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.