Details
-
Bug
-
Resolution: Fixed
-
Low
-
None
-
4.4.1, 4.5.0, 4.6.0
-
None
Description
in the documentation describing the use of EZP_INI_FILEMTIME_CHECK (a feature introduced in 4.4) located here: doc/features/4.4/ini_enhancement.txt
there is a warning in the section for this feature:
"There is one down side to this, it won't detect automatically that you have added new ini files in existing locations (already activated extensions/siteaccess, or override folder) anymore.
So you'll need to clear ini cache in these cases."
this warning does not accurately describes the behavior. there's absolutely no detection to any changes done in .ini caches until a cache clean is performed. the warning should be clear, with the feature in use, any modification needs a cache clean to be applied.
also, there is no mention to the behavior in a clustered installation. there are two warnings to make:
1 - the feature needs to be set equal in all the web servers. different nodes with some set to true others to false lead to inconsistent behavior.
2- with the feature on, the cache clean needs to be performed on every node each time a change is made, or else the .ini change will not propagate to all the nodes.
Attachments
Issue Links
- relates to
-
EZP-18509 (ezupgrade) upgrade consistencie check's gives warnings in ezp 4.2.0 and 4.1.x upgrade to ezp 4.5
- Open