search

yasglobal / make-paths-relative

This powerful plugin simplifies website maintenance by automatically converting absolute paths (URLs) for resources like links, scripts, stylesheets, and images to relative paths. This ensures your website functions flawlessly regardless of its location on a server or domain.
https://wordpress.org/plugins/make-paths-relative/
GNU General Public License v3.0
4 stars 1 forks source link

Make Paths Relative conflicts with Yoast Sitemap in last version of both plugins #2

Closed albanleandri closed 5 years ago

albanleandri commented 5 years ago

I am using the Pantheon Workflow (Dev > Test > Live) and Make Paths Relative (MPR) is super useful to keep links to images, and urls relative from an environment to another. Recently I found an issue, however. When MPR is activated for all content types, then the Sitemaps generated by Yoast plugin will contain only "relative" paths which is a serious issue for SEO. Indeed Google guidance for sitemaps recomments full absolute URLs, and not relative URLs. I saw that a previous release supposedly tackled this issue, but the benefit is not visible in the latest release of MPR.

Replication steps :

Actual result : Sitemaps urls are relative Expected result : Sitemaps urls should be absolute

albanleandri commented 5 years ago

Hi @yasglobal, here's an issue that requires your attention. Thanks a lot :)

albanleandri commented 5 years ago

Hi @yasglobal, just trying to follow-up, if you can advise for a workaround?

samiahmedsiddiqui commented 5 years ago

@AlbanL74fr Sorry about the issue and thank you for pointing this out.

I have fixed this issue but it appears again due to the recent change of Yoast SEO. I have fixed the issue and will release it at some time today.

samiahmedsiddiqui commented 5 years ago

@AlbanL74fr v1.1.2 is released. You can update the version and it will fix your sitemap issue.

Don't forget to provide us a feedback 😄

albanleandri commented 5 years ago

Hi @yasglobal, thanks, I have tested it according to the steps outlined in my issue description, and the bug seems to be fixed.