Feeling Lucky
?
[#2304] - When components call cacheClean it calls the storage clean method regard...
- Closed
- 24 Oct 2013
- Medium
- Build: master
- # 2304
- Diff
- garyamort:disabledCacheCleanFix
- Success The Travis CI build passed Details
User tests: Successful: Unsuccessful:
...less of whether the cache is enabled or disabled. This will cause problems if the caching mechanism it is using are not configured properly[since they aren't being used!]. Joomla defaults to the first enabled caching method it finds, regardless of whether it is configured properly - thus throwing errors and warnings when cleaning cache.
This hack will switch to file caching if caching is disabled to avoid these issues.
384e7c6
21 Oct 2013
When components call cacheClean it calls the storage clean method regardless of whether the cache is enabled or disabled. This will cause problems if the caching mechanism it is using are not configured properly[since they aren't being used!]. Joomla defaults to the first enabled caching method it finds, regardless of whether it is configured properly - thus throwing errors and warnings when cleaning cache.
When components call cacheClean it calls the storage clean method regardless of whether the cache is enabled or disabled. This will cause problems if the caching mechanism it is using are not configured properly[since they aren't being used!]. Joomla defaults to the first enabled caching method it finds, regardless of whether it is configured properly - thus throwing errors and warnings when cleaning cache.
garyamort
- comment
- 24 Oct 2013
It strikes me that this code can be fixed in the XCache connector to check the php.ini config and not even list itself as an option when it is not configured.
See http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=20476&start=0 for how making calls to disabled cache handlers can cause problems. In 3.2 there is no option for file cache handling so if the XCache extension is installed, Joomla is configured to use the XCache hander and caching is disabled.. afterwards making it impossible to save config changes due to the cache.
This hack switches to the file cache handler when caching is disabled to avoid broken calls to cache methods the user didn't want to enable to begin with.