You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[X ] I've searched for any related issues and avoided creating a duplicate issue.
Please give us a description of what happened.
When displaying the SEO URL, the related parent custom post type does not appear in the slug or URL. When it is changed to attempt to match the WordPress URL, it adds the change to the WordPress Permalink URL changing the URL and still not matching.
This is actually a duplicate of #3514. Currently, we are refactoring our Snippet Preview into React. Afterward, this can be solved without having to refactor a lot of code that is currently present.
Since it's a duplicate, I'm closing this. If you have anything to add, please do so in the issue I mentioned above. Thanks!
Please give us a description of what happened.
When displaying the SEO URL, the related parent custom post type does not appear in the slug or URL. When it is changed to attempt to match the WordPress URL, it adds the change to the WordPress Permalink URL changing the URL and still not matching.
Ex. http://WPURL.com/customPostType/currentPage
Yoast displays http://WPURL.com/currentPage and the slug only shows currentPage. If changed to customPostType/currentPage, WPURL is changed to http://WPURL.com/customPostType/customPostType/currentPage.
Please describe what you expected to happen and why.
Expected the slug to have customPostType/currentPage or at least the SEO URL to match what WordPress displays.
How can we reproduce this behavior?
Technical info
The text was updated successfully, but these errors were encountered: