You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Magento EE, blocks can have different invalidation than the page.
An example of this is the cart/minicart/items.phtml template. By default, inline JavaScript is emitted only when there are items inside the cart. When the cart changes, the block is invalidated - so this normally works fine.
With FPC and magento-footer-js, however, the JavaScript is moved to the footer only when it is first cached. Then the footer js is assumed to be static, even if the block is updated.
STR:
View the homepage with a new browser session. This will cache the homepage with an empty cart and no JavaScript.
Navigate to a product detail page and add to cart.
Return to the homepage. The minicart will update its content, but the page will not have the associated JavaScript.
Click "Remove" on any product. The link will fail, since it's a GET and missing a form key.
Possibly, it might be necessary to use a separate Processor, so that the js can be moved back to the footer after being pulled from the container cache. Getting it to order correctly with other already moved js seems potentially tricky.
The text was updated successfully, but these errors were encountered:
@ogivaljevo Hi, I'm afraid that I don't provide installation support. It can either be installed through the use of modman or by copying the app directory in to place. If you have any further problems, please create a separate issue rather than appending on this, unrelated, one.
In Magento EE, blocks can have different invalidation than the page.
An example of this is the cart/minicart/items.phtml template. By default, inline JavaScript is emitted only when there are items inside the cart. When the cart changes, the block is invalidated - so this normally works fine.
With FPC and magento-footer-js, however, the JavaScript is moved to the footer only when it is first cached. Then the footer js is assumed to be static, even if the block is updated.
STR:
Possibly, it might be necessary to use a separate Processor, so that the js can be moved back to the footer after being pulled from the container cache. Getting it to order correctly with other already moved js seems potentially tricky.
The text was updated successfully, but these errors were encountered: