Hi @normsash
Pods does not allow changing CPT settings when you extend it. These CPT are registered by other plugins and for that reason Pods won’t change their settings for compatibility reasons.
If you need to modify existing post types you should do so by code or check that plugin’s documentation.
Cheers, Jory
Hi Jory, thanks for the reply.
I don’t really need to change the name of the CPT; I was just thinking that might be the path to resolving the real issue. So let me focus on the real issue instead and then maybe you can provide some pointers.
As mentioned in the OP, when I extend the LearnDash CPT via Pods, for some reason it also forces a change in the permalink structure. What I mean is that I have the LD permalink settings configured to show permalink as //mydomain.com/courses/xxx and that works fine when Pods is not enabled. But as soon as I extend the LD cpt with Pods then the permalink structure for all courses is forced to //mydomain.com/sfwd-courses/xxx. I then can’t find any way to set it back to using just ‘courses’ for the permalinks even though it is set that way in my permalink > LearnDash settings.
One thing that might be impacting this… On the site I used to have a Pods defined cpt called “Courses” (e.g. mimicking the LD Courses / Lessons / Topics). I decided to instead just go with LD so I deleted the Pods CPTs for Courses, Lessons, Topics and then installed LearnDash.
Is it possible that there are still vestiges of the Pods cpt for Courses hanging around somewhere even though I deleted it and it doesn’t show up in Pods admin? Could that then be causing some conflict and forcing a change to the permalink structure?
Hi @normsash
Just to be sure it might be a good idea to fully clear the Pods cache (see Pods settings) and refresh the permalink structure.
Please let me know if this helps.
Also, if you disable Pods again, does LD work ok then?
Cheers, Jory
Thanks for the pointer, Jory. Clearing out the Pods cache resolved it… I didn’t think of that as I had deleted the Pods cpt “Courses” a long time ago (like a year ago) so didn’t think at all that cache would still be hanging around.
Again thanks for the pointer… it seems to be working now.
Hi @normsash
I agree that it’s weird that the cache was stuck that long. Might be related to this PR: https://github.com/pods-framework/pods/pull/5846
Good to hear your issue is resolved!
Cheers, Jory