Why Allow to Set Up Fallback Redirects when Adding Variants and Translations?
The URLs to your live site change when you add Scroll Document’s variants and translations to your site. Allow Viewport to automatically generate fallback redirects to prevent any broken links.
Your help center content might grow and become more complex over time. Our app Scroll Documents supports you in your content development by allowing you to manage content in different variants or languages - and add these to your Viewport site.
In order to accommodate this new content, Viewport will adjust the URL format. If your site was live and shared before, it means that all or some of your URLs will change. This change breaks any previously shared links.
When this change happens, the app will automatically prompt you to decide if fallback redirects should be set up for you. We strongly recommend that you opt for the generation of fallback redirects. The redirects will be to your site’s default variant and default language.
When are fallback redirects needed?
Fallback redirects are only needed if your Viewport site is already live and you decide to do at least one of the following things:
You set up variants for a Scroll Document content source that has been part of your live site before you set up the variants
You set up languages for a Scroll Document content source that has been part of your live site before you set up the languages
You add a default language to your Viewport site (under Site Settings) AND this site has at least one Scroll Document content source with languages set up.
In all these cases, your URL format will change, either for some content sources or for all.
How do URLs change?
When you set up variants for a Scroll Document content source that is already part of a live Viewport site, your URLs for that content source (and only that content source) will change:
from
/content-source/version/
to
/content-source/version/variant/
When you set up languages for a Scroll Document content source that is already part of a live Viewport site with a defined site default language,
OR if you add a default language for the first time on a site that has at least one Scroll Document content source with languages set up, your URLs for all content sources (including spaces) will change:
from
/content-source/version/
to
/language/content-source/version/.
How do fallback redirects prevent broken links?
Fallback redirects redirect whole groups of pages and fire exclusively when the request would have otherwise been a 404. They never overwrite other working URLs, only 404 pages.
When fallback redirects are needed (see above), Viewport will automatically ask if you want to auto generate them. If you accept, the app will create and save the fallback redirects for you. There is nothing you need to do besides updating the site.
The redirects will always be to your site’s default variant and default language.
You can view, edit and remove the generated redirects at any time under Site settings → Literal Redirects (tick ‘Advanced’ to open the redirect editor).
Need more help?
If you have old links that result in 404 pages, please check if any fallback redirects have been set up (Go to ‘Site Settings’ → Active Redirects → Manage → Tick ‘Advanced’ to open the redirect editor)
If no redirect are visible in the editor, please reach out to help@k15t.com. We will help you to manually set up fallback redirects that ensure that any old links continue to work.