Closed LeulAria closed 3 years ago
@LeulAria Thanks for that issue, that issue is related with 404 netlify and 404 next. we need to configure netlify for this. we need a PR for this.
may be /* /index.html 200 in _redirects
@LeulAria We've actually tried this. This would have worked when next doesn't have the locale functionality turned on. But in our case Next genertes an en.html
and am.html
files. So we had to write a rule like this based on the locale /am/* /am.html 200
. But for some reason this won't work for three level subpages like /am/hosts/something
. Only solution that came to mind was to make other ridirect rules for each of this routes. But that seemed unscalable. So we just kept it this way till we find a better way but if nothing works we are gonna have to use that.
so @abdulhamidOumer stated , there is an issue with the amharic characters being on the url, there were the same issue with axios , that has to be encoded before sending.
@henoktsegaye that's true, have also found this open issue on the netlify forum . So we can either try writing the encoded URI rule on the redirect directly for the Amharic hosts or find another way to retrieve them from the backend, for the next episode release maybe.
This is fixed now