Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Yoast SEO URL not working with custom post types #9487

Closed
cestes1177 opened this issue Apr 16, 2018 · 1 comment
Closed

Yoast SEO URL not working with custom post types #9487

cestes1177 opened this issue Apr 16, 2018 · 1 comment

Comments

@cestes1177
Copy link

  • [X ] I've read and understood the contribution guidelines.
  • [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.

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?

  1. Create custom post type
  2. Create a page within the custom post type
  3. Look at the Yoast SEO part of the page in the admin and should see the custom post type missing from the URL

Technical info

  • WordPress version: 4.9.5
  • Yoast SEO version: 7.2
  • Relevant plugins in case of a bug:
  • Tested with theme: Avada
@cestes1177 cestes1177 changed the title Yoast SEO URL not working with custom types Yoast SEO URL not working with custom post types Apr 16, 2018
@benvaassen
Copy link
Contributor

Thanks for your bug report!

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants