Problem with footer pages for non-default stores.

[alinadivante]

Current behavior

Links from footer (in non-default stores) redirect to pages without content, and CMS pages to 404 page not found.
When I open CMS page from the footer, the following error occurs in dev console:

And if I open CMS via URL, the following error occurs in dev console:

Expected behavior

All links should work properly, without errors in dev console.

Steps to reproduce the issue

1. Run the latest develop version with mulistore
2. Go to /de or /it store
3. Check links from footer
4. Open CMS pages from footer
5. Open CMS via link, e.g http://localhost:3000/de/i/about-us

Repository

Can you handle fixing this bug by yourself?

• YES
• NO

Which Release Cycle state this refers to? Info for developer.

Pick one option.

• This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
• This is a bug report for current Release Candidate version on https://next.storefrontcloud.io - In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
• This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.

Environment details

• Browser:
• OS:
• Node:
• Code Version:

Additional information

[pkarw]

Seemingly these cms pages were not synced for lang. versions; which is fine and we should probably just better handle the 404 error (not having hydration/console errors); then to remove the links from footer if the currentStoreView().storeCode !== config.i18n.defaultStorecode

[andrzejewsky]

@alinadivante works for me, can you check again with the newest develop (maybe It has been fixed)?

[alinadivante]

@andrzejewsky I still have the same errors, so maybe I'll send you my config and then check again if the problem is also reproducible for you