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
After changing the permalink structure to the ideal "Structured" option, the permalinks in the post sitemap that Yoast generates (post-sitemap.xml) are broken. e.g. https://example.com/work/%postname%/. Note how %postpath% gets parsed, but%postname% doesn't.
I haven't explored the source in depth yet, so I'm not sure how hard it'd be to fix this... But it'd be great if it could play nicely with the auto sitemap generation that Yoast provides, especially since it's such a popular plugin. The only workaround I could think of in the meantime is to create / update the sitemaps manually, but that isn't ideal for bigger sites or for non tech saavy clients... Is there any other workaround that I've missed?
The text was updated successfully, but these errors were encountered:
After further investigation I'm beginning to think this issue might be isolated to Yoast, as other sitemap generators (e.g. Google Sitemap Generator) don't seem to have this problem. Whether the problem is 100% on the Yoast side or not may be worth investigating, but that doesn't necessarily concern me at this point in time.
I'll leave this open for you guys to investigate, but disabling the Yoast sitemaps and using the Google Sitemap Generator plugin instead is an easy enough workaround for me.
After changing the permalink structure to the ideal "Structured" option, the permalinks in the post sitemap that Yoast generates (post-sitemap.xml) are broken. e.g.
https://example.com/work/%postname%/
. Note how%postpath%
gets parsed, but%postname%
doesn't.I haven't explored the source in depth yet, so I'm not sure how hard it'd be to fix this... But it'd be great if it could play nicely with the auto sitemap generation that Yoast provides, especially since it's such a popular plugin. The only workaround I could think of in the meantime is to create / update the sitemaps manually, but that isn't ideal for bigger sites or for non tech saavy clients... Is there any other workaround that I've missed?
The text was updated successfully, but these errors were encountered: