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

Sitemap.xml is not correctly redirected to sitemap_index.xml #10649

Closed
2 tasks done
Rbcafe opened this issue Aug 15, 2018 · 7 comments
Closed
2 tasks done

Sitemap.xml is not correctly redirected to sitemap_index.xml #10649

Rbcafe opened this issue Aug 15, 2018 · 7 comments

Comments

@Rbcafe
Copy link

Rbcafe commented Aug 15, 2018

  • I've read and understood the contribution guidelines.
  • I've searched for any related issues and avoided creating a duplicate issue.

Please give us a description of what happened.

Sitemap.xml is not correctly redirected to sitemap_index.xml

Please describe what you expected to happen and why.

Redirect from sitemap.xml to sitemap_index.xml, based on the initial scheme from /wordpress-seo/css/main-sitemap.xsl

How can we reproduce this behaviour ?

  1. I use qtranslate-x
  2. I use also domains with different tld . (fr,de,es,etc...)
  3. I go to sitemap.xml
  4. I obtain a 404 error.
  5. The 404 request for the file : /wordpress-seo/css/index-sitemap.xsl

My fix

  • Creation of the file /wordpress-seo/css/index-sitemap.xsl
  • Creation of the file /wordpress-seo/css/qwp-sitemap.xsl
  • Both files are based on /wordpress-seo/css/main-sitemap.xsl

Technical info

  • WordPress version: 4.9.8
  • Yoast SEO version: 8.0
  • Tested with a private theme.
@benvaassen
Copy link
Contributor

Thanks for reporting this bug! I can reproduce I'm not being redirected when I visit /sitemap.xml with only Yoast SEO 8.0, default theme Twenty Seventeen and WordPress 4.9.8. Instead, I see my homepage.

I’ve marked it as backlog so it appears on the to-do list for our developers.

@Rbcafe
Copy link
Author

Rbcafe commented Aug 16, 2018

Greetings @benvaassen

Thanks for the information.

Best regards

@Rbcafe

@felixarntz
Copy link
Contributor

@Rbcafe Can you verify whether this bug is new in 8.0? Or might it have existed in previous versions (7.9) as well? If it is new, it is likely caused by #10353. I can't replicate the issue at the moment with 8.0, so it appears to be environment-related.

@felixarntz felixarntz self-assigned this Aug 16, 2018
@Rbcafe
Copy link
Author

Rbcafe commented Aug 16, 2018

Greetings @felixarntz ,

Requesting the sitemap.xml expects for qwp-sitemap.xsl and sometimes for index-sitemap.xsl generating a 404 error. Each time I update the wordpress-seo plugin, I must prepare file index-sitemap.xsl and file qwp-sitemap.xsl on the css folder to avoid a 404 error.

The fix would be : Why there is a qwp-sitemap.xsl and index-sitemap.xsl request ?

Best regards

@Rbcafe

@felixarntz
Copy link
Contributor

@Rbcafe Thank you for the quick response, we will look into this.

@benvaassen It didn't redirect for you without having qtranslate-x active? In that case it likely has a different source, might be covered by #10661.

@felixarntz felixarntz removed their assignment Aug 16, 2018
@felixarntz
Copy link
Contributor

I tested a bit further:

  • Using WordPress 4.9.8 and development version of Yoast SEO (i.e. >= 8.0).
  • I installed and activated qTranslate-X. sitemap.xml redirects to sitemap_index.xml. main-sitemap.xsl opens correctly.
  • Then I also installed and activated the plugin Integration: Yoast SEO & qTranslate-X as recommended. Now, sitemap.xmlstill redirects to sitemap_index.xml, but the page is entirely blank. main-sitemap.xsl still opens correctly.

I'm not quite sure where the index-sitemap.xml and qwp-sitemap.xml are coming from. There appear to be some issues with the integration plugin. Are you using it to @Rbcafe or only qTranslate-X itself?

@Djennez
Copy link
Member

Djennez commented Jun 27, 2019

I'm going to close this as outdated (as both WP and Yoast have been renewed and qTranslate-X on WordPress.org is no longer maintained).

If the same, or a similar, issue arises with the latest versions, please do let us know so that we may investigate.

@Djennez Djennez closed this as completed Jun 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants