The open-source frontend for any eCommerce. Built with a PWA and headless approach, using a modern JS stack. We have custom integrations with Magento, commercetools, Shopware and Shopify and total coverage is just a matter of time. The API approach also allows you to merge VSF with any third-party tool like CMS, payment gateways or analytics. Newest updates: https://blog.vuestorefront.io. Always Open Source, MIT license.
From vue-storefront created by slri: vuestorefront/vue-storefront#5578
Description
Directly means it's not a vue-router route, you can also open the page and hard reload (Ctrl + Shift + R).
This is about the page mixin CmsPage.js.
This essentially watches for route change through vue-router, but if you directly visit the page the cms module's single action won't be dispatched, resulting in current being null.
Steps to reproduce the issue
Have a page that uses CmsPage.js as a mixin (Static.vue from Capybara for example)
Have a cms_page (slug: test)
Visit <your website>/test (or whatever your routing is)
Open Vue devtools
Look at Vuex state > cmsPage > current
Current behavior
current is null
Expected behavior
current is an object of a cms page being currently displayed
Version of Vue Storefront
[x] Vue Storefront
[ ] Vue Storefront Next
Can you handle fixing this bug by yourself?
[ ] YES
[x] NO
Which Release Cycle state this refers to? Info for developer. (doesn't apply to Next)
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.
[x] 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.
From vue-storefront created by slri: vuestorefront/vue-storefront#5578
Description
Directly means it's not a vue-router route, you can also open the page and hard reload (Ctrl + Shift + R). This is about the page mixin
CmsPage.js. This essentially watches for route change throughvue-router, but if you directly visit the page the cms module's single action won't be dispatched, resulting incurrentbeingnull.Steps to reproduce the issue
<your website>/test(or whatever your routing is)Current behavior
Expected behavior
Version of Vue Storefront
Can you handle fixing this bug by yourself?
Which Release Cycle state this refers to? Info for developer. (doesn't apply to Next)
Pick one option.
developbranch and create Pull Request2. Feature / Improvementback todevelop.releasebranch and create Pull Request3. Stabilisation fixback torelease.hotfixormasterbranch and create Pull Request4. Hotfixback tohotfix.Environment details
Additional information