Use only HTTP POST or PUT methods to change state (e.g., adding to a shopping cart, adding to a wishlist, etc.) and do not expect to see caching on these methods. There are sections that allow you to declare an ‘action’ node without specifying a sections, for instance, when logging out: The following example adds comments to app/code/Magento/Catalog/etc/frontend/sections.xml so you can see what the code is doing. Information will be updated after what comes first: section_data_lifetime time passed or an action that the update cart triggered. Product information will not be simultaneously updated in customer cart (product name, price, product enabled/disabled). After scheduled time passes, section cart will be updated.
Customer cart lifetime option section_data_lifetime which is 60 minutes by default.
Store and website switching, after any of these action customer section cart will be updated.This means that any customer section will not be updated until proper action was made. Magento invalidates the cache on a POST or PUT request.Ĭustomer sections was designed to cache private data in browser storage. Specify actions that trigger cache invalidation for private content blocks in a sections.xml configuration file in the Vendor/ModuleName/etc/frontend directory. Initialize : function () Īll properties are available in the template where the UI component initialized.Įxample of defining a UI component in a layout Invalidate private content MFTF test versioning and backward compatibility policy.Handling outdated in-memory object states.Asynchronous Message Queue configuration files.Migrate install/upgrade scripts to declarative schema.Upload your component to the Commerce Marketplace.Roadmap for developing and packaging components.
0 kommentar(er)
