Hi again @bomalo,
Ad 1. To make the long story short, my plugin does not rely on the native slug & rewrite rules. It shows the native slug, because by default the slug is also added to the end of custom permalinks. It is not required, as you can fully customize the URL. Ergo, the custom permalinks do not have to contain the native slug. In Permalink Manager the native slugs can be removed from the custom permalinks and still my plugin will be able to detect them.
There are 3rd party plugins & other custom solutions that are using the native slugs, that is why my plugin does not change the native slugs to avoid the compatibility issues. Instead it stores & detect the custom permalinks separately. The main advantage of this is that you can easily remove my plugin and then all the native URLs will be restored (because the native slugs are not changed).
Please note that the post slug is only a part of URL and both slug & rest of URL can be edited with my plugin. But, by editing the custom permalinks in my plugin you do not automatically change the native slug.
Ad 2. In the sitemaps Yoast SEO does not parse the slug directly. For sitemap entries it uses the full permalinks that can be filtered by 3rd party plugins (including mine). You can simply verify how it works. If you change the permalink with my plugin, the changes will be applied to both meta tags (canonical URL) and URLs in the sitemap.
The Yoast SEO metabox (in admin panel) shows the permalink based on the native slug, because there is no reliable way to change it and make it display the custom permalink set with Permalink Manager. Yet, the custom permalinks are displayed & work correctly elsewhere (including front-end).
Best regards,
Maciej
-
This reply was modified 5 years, 4 months ago by
Maciej Bis.
-
This reply was modified 5 years, 4 months ago by
Maciej Bis.