-
Notifications
You must be signed in to change notification settings - Fork 36
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
Using TYPO3-404 handling #19
Comments
Let me get this straight.. Do you want to display custom error page, not related with nuxt and vue, for example typo3 error page ? Or do you need display specific error content for specific status code on the nuxt page? |
actually i intended to reuse the core implementation of typo3's error-handling. do you have any suggestion? |
Yes, exactly. What happens if I finally end-up at the 404-page, nuxtjs doesn't interpret the page because of its header and throws an application error. |
If you want display nice error page instead of application error, just create error.vue page in layouts directory. |
@meincms you can switch on develop branch to test selected content page on error pages. This is development branch and might be changed. |
@meincms sorry for delay, we merged it to master |
Hi @mercs600 , can you please add this solution to your documentation? |
Is there any way to use the TYPO3 Error-Handling?
i.E. when configuring the 404-Error-Handling in TYPO3 and the site cannot be found, the website renders the 404-content, but sends an additional 404-Header. What's your recommendation to handle Errors? In fact it leads to the nuxtjs-typo3-error site – and doesn't render the intended content of the errorHandling-site of the TYPO3....
The text was updated successfully, but these errors were encountered: