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 eerohakio: vuestorefront/vue-storefront#5821
Current behavior
If CMS block is disabled from Magento it is still showing in frontend as its served from cache.
However CMS block gets removed from Elasticsearch once its disabled as CMS block indexer utilizes is_active attribute filter when fetching blocks to index.
This behaviour is valid at least when using CMS blocks as category "landing page".
Expected behavior
Once CMS block is disabled it should be not visible in frontend anymore.
Steps to reproduce the issue
Create CMS block with some content
Add CMS block to category as landing page
Visit category to warm cache
Disable CMS block
View category
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.
Environment details
Browser: Chrome 89, Safari 14
OS: macOS BigSur
Node: 12
Code Version: 1.12.2
Additional information
Environment utilizes Varnish.
When refreshing cache x-cache and x-vs-cache headers are correctly showing "Miss" but content is still not updated.
From vue-storefront created by eerohakio: vuestorefront/vue-storefront#5821
Current behavior
If CMS block is disabled from Magento it is still showing in frontend as its served from cache. However CMS block gets removed from Elasticsearch once its disabled as CMS block indexer utilizes is_active attribute filter when fetching blocks to index. This behaviour is valid at least when using CMS blocks as category "landing page".
Expected behavior
Once CMS block is disabled it should be not visible in frontend anymore.
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
Environment utilizes Varnish. When refreshing cache x-cache and x-vs-cache headers are correctly showing "Miss" but content is still not updated.