-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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 generation in wrong folder when vhost is connected to pub folder #2802
Labels
bug report
Issue: Ready for Work
Gate 4. Acknowledged. Issue is added to backlog and ready for development
Comments
Hi @jasperzeinstra Thanks for reporting this issue. We've created an internal ticket MAGETWO-47607 to process it. |
sshrewz
added
the
Issue: Ready for Work
Gate 4. Acknowledged. Issue is added to backlog and ready for development
label
Mar 17, 2016
A good work around for this would be to create a symbolic link pointing to the root sitemap.xml from pub, but if you are creating multiple sitemaps that will get unwieldy fast. |
Duplicate - #1146 |
magento-team
pushed a commit
that referenced
this issue
Apr 19, 2017
…9094 - restored original file content
Fixed in #9094 |
Internal ticket to track issue progress: MAGETWO-67054 |
magento-team
added
Issue: Ready for Work
Gate 4. Acknowledged. Issue is added to backlog and ready for development
bug report
develop
labels
Jul 31, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug report
Issue: Ready for Work
Gate 4. Acknowledged. Issue is added to backlog and ready for development
In my case my domain (vhost) is connected to the pub folder instead of the root folder, for security reasons. Now when I try to generate a sitemap.xml in te root of the url. www.mydomain.com/sitemap.xml I need to fill in
/
as path. But the sitemap is created in the root folder now, instead of the pub folder. And when I set/pub/
as my path I get the URL www.mydomain.com/pub/sitemap.xml returned in the backend. This is an incorrect URL.The text was updated successfully, but these errors were encountered: