You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey there,
maybe I'm really stupid here but I'm quite new to Sveltekit and has struggled with getting this plugin to work on a Netlify deploy. It get's added correctly to the build folder, which I can also see when I download the deploy from Netlify, but when visiting the mysite.com/sitemap.xml url, I get a 404 and I interpret it like Sveltekit expects a route, but nothing found.
Do I need to exclude the sitemap from the routes somehow?
I've seen some other solutions online where people create their own loader and custom build function for the sitemap which I could do of course, but I was under the impression this was not needed for this plugin? Or how are people actually being able to "visit" their sitemap without Sveltekit interfering and trying to render a route there?
Thanks!
// Jens.
The text was updated successfully, but these errors were encountered:
This plugin states it is built for the static adapter, described here. Static websites allow access to all files by default, thus not requiring a route. It sounds like you are likely using a different adapter on Netlify, causing the issue. If the sitemap is working as desired, you can simply add a route and include the sitemap in the +page.svelte.
Hey there,
maybe I'm really stupid here but I'm quite new to Sveltekit and has struggled with getting this plugin to work on a Netlify deploy. It get's added correctly to the build folder, which I can also see when I download the deploy from Netlify, but when visiting the
mysite.com/sitemap.xml
url, I get a 404 and I interpret it like Sveltekit expects a route, but nothing found.Do I need to exclude the sitemap from the routes somehow?
I've seen some other solutions online where people create their own loader and custom build function for the sitemap which I could do of course, but I was under the impression this was not needed for this plugin? Or how are people actually being able to "visit" their sitemap without Sveltekit interfering and trying to render a route there?
Thanks!
// Jens.
The text was updated successfully, but these errors were encountered: