-
The problemHello, I'm currently working on a project using Astro and integrating keystatic for content management. Initially, everything worked fine, and I was able to access the keystatic admin panel through the However, after enabling Astro's built-in internationalization (i18n) feature, which required changing my routing to include a top-level directory for each locale (e.g., [locale].astro), I've encountered a problem. Now, when I try to access the /keystatic route, I receive a 404 Page Not Found error. My pages directory looks like this:
Basicaly the top level Steps to Reproduce:
Expected Behavior:Access to the /keystatic route should remain unaffected by the addition of locale-specific routing, allowing me to manage my content as before. Actual Behavior:After enabling i18n and creating a [locale].astro top level route, accessing the /keystatic route results in a 404 Page Not Found error. Question:Is there a known workaround or configuration change that needs to be applied to maintain access to the Thank you in advance for your help! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
Beta Was this translation helpful? Give feedback.
-
Yeah I did this and I had to change the |
Beta Was this translation helpful? Give feedback.
-
Collating this in #1080 — there are numerous requests and issues around supporting multi-lingual sites in Keystatic. |
Beta Was this translation helpful? Give feedback.
Yeah I did this and I had to change the
/[locale]
directory to/[...locale]
because single routes can't haveundefined
as value. I don't know if this is the right way.