What post type and/or taxonomy slugs are you trying to create?
Any other logged errors showing up in your hosting error log that may provide some extra context of what’s going on?
Is it when registering the content types that it happens? or when trying to use them in some way or viewing the frontend and one of the created posts?
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 3 years, 5 months ago by zacwine.
Not really from me. I know that we aim to keep CPTUI pretty low maintenance and do its job and do it well. That job being that it gets the content types registered for you. I’m not familiar much at all with Avada Layouts, so they would be the best place to go, for which you already have a support request open with.
Let us know what they come up with, if anything. I’ll leave this thread open still as well just in case something is needed on our side.