Nothing changed in regards to types or slugs when the 502 started. We thought it might be shared taxonomies across different CPTs, but when we removed them, the problem persisted.
The host says that the log isn’t showing any errors.
It is not clear when or how it is occuring, but it’s the front-end… however, we’re using Avada and after poking around some more, it looks like a conflict between their Layouts and CPT UI. If I turn off the Avada Layout, the problem resolves… but it’s not a solution because we want to use both Layouts and CPT UI.
What’s frustrating is that there doesn’t appear to be a triggering event. I have a ticket open with Avada as well. Any further insight?
-
This reply was modified 4 years ago by zacwine.