Tel: 07568 463724

Mail: [email protected]

Magento Bug Killer

Magento CE Bug Static Block Bug

It would appear that the latest update of Magento CE is not without it’s issues, and we are currently looking into a couple of hopefully minor bugs that have cropped up after testing.

[fusion_builder_container hundred_percent=”yes” overflow=”visible”][fusion_builder_row][fusion_builder_column type=”1_1″ background_position=”left top” background_color=”” border_size=”” border_color=”” border_style=”solid” spacing=”yes” background_image=”” background_repeat=”no-repeat” padding=”” margin_top=”0px” margin_bottom=”0px” class=”” id=”” animation_type=”” animation_speed=”0.3″ animation_direction=”left” hide_on_mobile=”no” center_content=”no” min_height=”none”]

Magento Bug Killer
Magento Bug Killer

So far we have found two distinct bugs in the Magento upgrade, and hopefully this is all we will find, however the main one is with regard to the Blocks HTML Output Cache.

Magento Blocks HTML Output Cache Bug in Upgrade

It would appear from our research that there is a problem with the Blocks HTML Output cache in Magento on the upgrade in that cache keys on this particular cache are not being allocated correctly.

Currently the solution to this is to disable the Blocks HTML Output cache in the Configuration -> Cache Management Screen

Disabling the cache should resolve the issue, however it is far from being an ideal solution, in the meantime there is also a Magento Extension that can resolve the issue without the need to hack the core files within Magento

See: Rkt_SbCache on GitHub

We have so far implemented this particular fix on three Magento stores and it has resolved the issue completely on all three, in the absence of patch or new release from the core Magento team, we would suggest you do the same if you are considering an upgrade to Magento 1.9.2 as currently your only real alternative is to disable the Blocks HTML Output cache which will result in a significant performance decrease in magento.

In the mean time whilst we await an action from the core Magento development team, this particular issue can be tracked on Magento’s Issue system as they have it as a registered bug:

Issue #7817: First Static Block cached is always shown.



On Key

Related Posts