-
Notifications
You must be signed in to change notification settings - Fork 3
Description
Hello, thank you for the plugin!
I am running into an issue testing with localized error pages. The plugin does generate a localized 404.html file in the expected language directory. However when running the project build and navigating to a non-existent page, the default-language 404 page is always shown, even if the attempted path seems like it should lead to the localized page.
For example, /es/not-a-page displays /404.html rather than /es/404.html
As the error page is relatively small, I have considered dynamically swapping the page content at runtime using the url path to determine the language that should be displayed. However, components like and no longer work in this case, as they only read the locale set by the plugin and cannot be reconfigured to read the url path instead.