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 domideimel: vuestorefront/vue-storefront#5616
Current behavior
When changing some CMS-Block in some global areas like the footer / header and invalidate the cache after that with the invalidation URL for Redis, the blocks do not update. When I open a Category Page or a product detail page everything seems to work fine.
The Block show the correct content only after the Cache TTL has passed. so 24 hours in the default.
I tried it in multiple Browser to exclude the aggressive caching in chrome.
Expected behavior
The CMS Pages with all the non CMS Page parts should show the right content after the cache invalidation
Steps to reproduce the issue
put some CMS-Blocks in header or footer
edit their contents
invalidate the cache and open a cms page
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 domideimel: vuestorefront/vue-storefront#5616
Current behavior
When changing some CMS-Block in some global areas like the footer / header and invalidate the cache after that with the invalidation URL for Redis, the blocks do not update. When I open a Category Page or a product detail page everything seems to work fine.
The Block show the correct content only after the Cache TTL has passed. so 24 hours in the default. I tried it in multiple Browser to exclude the aggressive caching in chrome.
Expected behavior
The CMS Pages with all the non CMS Page parts should show the right content after the cache invalidation
Steps to reproduce the issue
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