Skip to content
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

not-found and error pages not working #52

Closed
VugarAhmadov opened this issue Feb 3, 2024 · 2 comments
Closed

not-found and error pages not working #52

VugarAhmadov opened this issue Feb 3, 2024 · 2 comments

Comments

@VugarAhmadov
Copy link

After updating to latest version of nextjs and next-i18n-router my custom not found and error pages not working anymore
i checked the example with react-intl and not-found page not working there too

@VugarAhmadov
Copy link
Author

found the workaround. created [...not-found/page.tsx inside [locale] folder and wrote this code

import { notFound } from "next/navigation";

export default function NotFoundCatchAll() {
notFound();
}

hence, closing this issue

@i18nexus
Copy link
Owner

i18nexus commented Feb 5, 2024

Yes, not-found pages have to be done this way in dynamic segments in Next 13+. More detail can be read here in this previous issue: #36

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants