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
Error page custom layout not being always respected and loaded. #7658
Comments
We released 2.13.3 that should fix your issue. Please try again and confirm that it's fixed please. |
Nuxt v. 2.13.3 same issue. Error page with custom layout option works only for requests where error handled on the server side. After that all is fine, client routing works as expected. In other cases error page uses default layout =\ |
Yes, I can confirm what @barfi said is the reality. It is not working as expected even in 2.13.3. |
Spent many hours on this. As I could undestand, if an error occures outside the default layout (for example, 404 error), so there is no current page to use some layout, then error page uses it's own layout (set in the error component |
I am having a similar issue where I will trigger the error page by any means and then any route navigated to after that has its layout overridden by the error pages current set layout. Not sure if 100% related though. For example:
|
+1 for this issue |
Should be resolved with v2.14.5 |
Versions
Reproduction
Additional Details
https://codesandbox.io/s/nuxt-error-layout-not-change-7z60q?file=/pages/index.vue
Steps to reproduce
https://codesandbox.io/s/nuxt-error-layout-not-change-7z60q?file=/pages/index.vue
You can use the sandbox above and you will quickly understand and reproduce the issue even setting the lastest version of nuxt. You will be able to reproduce the case where the error page custom layout is not respected.
What is Expected?
As mentioned in the documentation and as in previous versions we should be able to set a custom layout for the error page.
What is actually happening?
Unfortunately, this has stopped working in the last version and it seems that it was not working on version 2.12.0 too.
The text was updated successfully, but these errors were encountered: