View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0019881||mantisbt||bugtracker||public||2015-06-24 12:59||2022-07-24 06:35|
|Target Version||1.3.0-beta.3||Fixed in Version||1.3.0-beta.3|
|Summary||0019881: config_flush_cache() doesn't properly clean the cache|
The config api uses several cache variables. Currently the config_flush_cache() function only clears $g_cache_config and $g_cache_config_access.
It should also clear $g_cache_config_eval.
I don't think this issue affects the current MantisBT core in any way, I stumbled upon this problem while performing tests for another issue.
|Tags||No tags attached.|
PR for review https://github.com/mantisbt/mantisbt/pull/613
Maybe we could get rid of the whole config_eval stuff.
It seems to be used just a view times, e.g.
Do we really need this?
I hardly believe that administrators do something like
@atrol, the idea was that the admin will just need to set one config option:
This will in-turn using eval result in the following values:
This also means that if we add a third one $g_xxx_cookie in a future release, then it will automatically pickup the same logical prefix.
Now whether this this is really useful or not is a different story :)