-
Notifications
You must be signed in to change notification settings - Fork 905
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 Index - Unexpected Server Error #4695
Comments
Can you repro it on a separate project that you can share with view permissions? |
@kof Sure! Here you go: https://p-df5ed58e-e96a-4082-8eca-33ca946adba8.apps.webstudio.is/?authToken=8c04bd93-4cb0-4bb5-b70a-edefd1082a5f&mode=preview Here is the publish location displaying the same issue: https://xml-test-zczcn.wstd.io/sitemap.xml If you need greater access please let me know. Thanks for looking into the issue! |
Wow @kof . 🤦 Thank you. |
## Description closes #4695 Also allow link in xml closes #4401 ## Steps for reproduction 1. click button 2. expect xyz ## Code Review - [ ] hi @kof, I need you to do - conceptual review (architecture, feature-correctness) - detailed review (read every line) - test it on preview ## Before requesting a review - [ ] made a self-review - [ ] added inline comments where things may be not obvious (the "why", not "what") ## Before merging - [ ] tested locally and on preview environment (preview dev login: 0000) - [ ] updated [test cases](https://github.com/webstudio-is/webstudio/blob/main/apps/builder/docs/test-cases.md) document - [ ] added tests - [ ] if any new env variables are added, added them to `.env` file
When I publish a sitemap index XML page structured like so I get an
unexpected server error
message:This is currently published (or should be at least) to https://davidsteedco.com/sitemap.xml. The error occurs on any URL I set the index to be. Dynamically generated and static values have both been tried.
(Just for reference I am attempting to achieve the XML structure specified by Google)
The text was updated successfully, but these errors were encountered: