Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cache tags does not get created for widgets. #5417

Closed
bgkavinga opened this issue Jul 2, 2016 · 11 comments
Closed

Cache tags does not get created for widgets. #5417

bgkavinga opened this issue Jul 2, 2016 · 11 comments
Labels
bug report Component: Cms Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release

Comments

@bgkavinga
Copy link

Since Magento\Cms\Block\Widget\Block class does not implement from Magento\Framework\DataObject\IdentityInterface, X-Magento-Tags related to widgets does not get created. This will effect to widgets & static blocks created from admin panel. Once you update static block contents or widgets, the changes will not get effected in the front end because of the missing cache tags.
Refer: Magento\PageCache\Model\Layout\LayoutPlugin::afterGetOutput()

@ilol
Copy link

ilol commented Jul 28, 2016

MDVA-764

@andimov
Copy link
Contributor

andimov commented Aug 1, 2016

@bgkavinga
Thank you for reporting!
Did you try to use MDVA-764 as a fix for your issue?

@bgkavinga
Copy link
Author

@andimov what you mean by MDVA-764?

@andimov
Copy link
Contributor

andimov commented Aug 2, 2016

@bgkavinga
Sorry, I made a mistake assuming that support patch already released.
It is our internal ticket for this issue.

@andimov andimov added Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development bug report and removed Progress: needs update labels Aug 2, 2016
@koenner01
Copy link
Contributor

Any news on this ?

@magento-engcom-team magento-engcom-team added Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development bug report Component: Cms Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed labels Sep 11, 2017
@magento-engcom-team magento-engcom-team added 2.1.x Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release labels Nov 10, 2017
@magento-engcom-team
Copy link
Contributor

@bgkavinga, thank you for your report.
We've created internal ticket(s) MAGETWO-83661 to track progress on the issue.

@magento-engcom-team
Copy link
Contributor

Hi @bgkavinga

This ticket has been marked as "Triage Wanted" due to low user involvement over time. Over the next 2 weeks we are looking for additional community feedback to decide if it should be archived or not. More information on this is available on the GitHub wiki.

Thank you for collaboration.

@rodrigowebjump
Copy link
Member

@magento-engcom-team Hi, do you have any update on this?

@magento-engcom-team
Copy link
Contributor

Hi @rodrigowebjump
Unfortunately, we do not have any updates regarding this ticket.

@rodrigowebjump
Copy link
Member

rodrigowebjump commented Sep 16, 2018

@magento-engcom-team I am working on it.

@magento-engcom-team
Copy link
Contributor

@bgkavinga, thank you for your report.

Unfortunately, we are archiving this ticket now as it did not get much attention from both Magento Community and Core developers for an extended period. This is done in an effort to create a quality, community-driven backlog which will allow us to allocate the required attention more easily.

Please feel free to comment, reopen or create new ticket according to the Issue reporting guidelines
if you are still facing this issue on the latest 2.4-develop branch. Thank you for collaboration.

magento-engcom-team pushed a commit that referenced this issue Mar 3, 2020
…ery-prs

[Magento Community Engineering] Community Contributions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Component: Cms Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Development

No branches or pull requests

8 participants