View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0006108||OXID eShop (all versions)||4.08. Cache||public||2015-04-02 15:38||2016-03-30 17:03|
|Product Version||4.9.3 / 5.2.3|
|Target Version||Fixed in Version||4.9.7 / 5.2.7|
|Summary||0006108: Default Cache Backend requires enabled blDontShowEmptyCategories|
|Description||As reported earlier by other users (0005804) the performance setting blDontShowEmptyCategories can have side effects.|
A very ugly one becomes visible in the lastest OXID eShop Enterprise Edition 5.2.3 when you enable the Default Cache Backend (on filesystem) and leave the option "blDontShowEmptyCategories" inactive (as it is per default after installation and which is recommended for performance reasons).
However, this combination of settings can lead to the generation of an incomplete category tree which is then getting saved to cache-dir/oxcategorytree_1_de.cache
When switching to a shop category of a different root you will see broken/empty categories, because those categories are missing in the cache-file.
Usually there are 25 categories in the oxid default demo shop.... in the cache file, when clicking kiteboarding and kites first, you will only have 13 categories cached - and the shop doesn't recognize that actually parts of the tree are still missing in the cache file.
|Steps To Reproduce||1. set up a fresh EE 5.2.3 shop|
2. activate Default Cache Backend (for filesystem)
3. browse shop: start page, kiteboarding, kites
4. click on category "Bekleidung" and then "Fashion"
5. page is empty, shows no sub categories - see screenshot
|Tags||Cache, Category, Enterprise|
|PHP Version||Not defined|
|Database Version||Not defined|
|related to||0005804||acknowledged||florian.auer||Performance option "Do not display empty Categories" has side effects|
|related to||0006109||closed||QA||Re-indexing the category tree from back-end should automatically clear the Default Cache Backend|
Bildschirmfoto 2015-04-02 um 15.31.11.png (416,780 bytes)
|Are there any error messages which are thrown into the logs?|
No, neither apache error_log nor EXCEPTION_LOG
I just set up a fresh demoshop and executed the steps listed above and had exactly the same behavior.
|Is there an ETA on when this issue will be resolved? We are havin the same problem and neither enabling blDontShowEmptyCategories or disabling the cache is a real option for us, since it has major perfmanca drawbacks.|