You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is something I encounter when translating existing sites:
An example url of a page on a site without translations:
example.com/contenttype/this-is-a-record
After implementing the translate extension, you get something like this:
example.com/en/contenttype/this-is-a-record
The first url now produces a 404 error.
It would be nice to implement a fallback so the old url's somehow redirect automatically to the default locale.
It's possible that this already an option and I just missed it somehow :) If not, this would be a very useful feature.
The text was updated successfully, but these errors were encountered:
This is something I encounter when translating existing sites:
An example url of a page on a site without translations:
example.com/contenttype/this-is-a-record
After implementing the translate extension, you get something like this:
example.com/en/contenttype/this-is-a-record
The first url now produces a 404 error.
It would be nice to implement a fallback so the old url's somehow redirect automatically to the default locale.
It's possible that this already an option and I just missed it somehow :) If not, this would be a very useful feature.
The text was updated successfully, but these errors were encountered: