Feeling Lucky
?
[#3487] - Misleading cache time settings
- Closed
- 25 Apr 2014
- Medium
- Build: master
- # 3487
- Foreign ID 33641
Suppose I need to configure cache time for a module.
I find this option in the Advanced Module Settings > Cache Time: 900
But it’s not clear 900 of what? hours, minutes???
- Why time unit is not specified in description? My customers repeatedly ask this question.
- One can suppose that the unit is a minute, since cache time in Global Configuration is set in minutes. But it turns out to be wrong, cache time in module cache settings must be set in seconds.
- Is it that important to set module cache time up to a second?
- If you need to set a long cache time e.g. 5 days, it’s pretty complicated to fill in this field. You’ll definitely need a calculator to accomplish the task (5 * 24 * 60 * 60 = 432000 sec), which is very inconvenient.
Currently, we have these descriptions:
Global Configuration > Cache Settings > Cache Time
“The maximum length of time in minutes for a cache file to be stored before it is refreshed.”
Module Manager > Any Module > Advanced Module Settings > Cache Time
“The time before the module is recached” <- time unit is not specified
To avoid confusion and simplify cache setting process we need:
- always describe what time unit is used for cache settings
- keep to the same time unit everywhere in cache settings. I think it’s better to use minutes.
zero-24
- | Description | <h3>Suppose I need to configure cache time for a module.</h3> <p>I find this option in the Advanced Module Settings > Cache Time: 900</p> <p>But it’s not clear 900 of what? hours, minutes???</p> <ul> <li>Why time unit is not specified? My customers repeatedly ask this question.</li> <li>One can suppose that the unit is a minute, since cache time in Global Configuration is set in minutes. But it turns out to be wrong, cache time in module cache settings must be set in seconds.</li> <li>Is it that important to set module cache time up to a second? </li> <li>If you need to set a long cache time e.g. 5 days, it’s pretty complicated to fill in this field. You’ll definitely need a calculator to accomplish the task (5 * 24 * 60 * 60 = 432000 sec), which is very inconvenient.</li> </ul><h4>Currently, we have these descriptions:</h4> <p><strong>Global Configuration > Cache Settings > Cache Time</strong><br> “The maximum length of time <strong>in minutes</strong> for a cache file to be stored before it is refreshed.”</p> <p><strong>Module Manager > Any Module > Advanced Module Settings > Cache Time</strong><br> “The time before the module is recached”</p> <h4>To avoid confusion and simplify cache setting process we need:</h4> <ul> <li>always describe what time unit is used for cache settings</li> <li>keep to the same time unit everywhere in cache settings. I think it’s better to use minutes. </li> </ul> | ⇒ | <h3>Suppose I need to configure cache time for a module.</h3> <p>I find this option in the Advanced Module Settings > Cache Time: 900</p> <p>But it’s not clear 900 of what? hours, minutes???</p> <ul> <li>Why time unit is not specified in description? My customers repeatedly ask this question.</li> <li>One can suppose that the unit is a minute, since cache time in Global Configuration is set in minutes. But it turns out to be wrong, cache time in module cache settings must be set in seconds.</li> <li>Is it that important to set module cache time up to a second? </li> <li>If you need to set a long cache time e.g. 5 days, it’s pretty complicated to fill in this field. You’ll definitely need a calculator to accomplish the task (5 * 24 * 60 * 60 = 432000 sec), which is very inconvenient.</li> </ul><h4>Currently, we have these descriptions:</h4> <p><strong>Global Configuration > Cache Settings > Cache Time</strong><br> “The maximum length of time <strong>in minutes</strong> for a cache file to be stored before it is refreshed.”</p> <p><strong>Module Manager > Any Module > Advanced Module Settings > Cache Time</strong><br> “The time before the module is recached” <- time unit is not specified</p> <h4>To avoid confusion and simplify cache setting process we need:</h4> <ul> <li>always describe what time unit is used for cache settings</li> <li>keep to the same time unit everywhere in cache settings. I think it’s better to use minutes. </li> </ul><p>Joomla 3.3<br><a href="http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=33641&start=0">http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=33641&start=0</a></p> |
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2014-04-25 07:55:38 |
| Labels |
Added:
?
?
|
||
| Labels |
Added:
?
Removed: ? ? |
||
JensKirk
- comment
- 25 Feb 2016
Why not have an option in the module so the module cache time can inherited from the global cache settings? In this way, we do not need to specify a cache time value for each module because it gets the cache time from the global settings.
I think that many Joomla webmasters are unware that they also have to set the cache time for each module. And they are also unware that the global cache time is set in minutes whereas the cache in the module is set in seconds.
Even in Joomla 3.5 beta2 it is not clear that the cache time in the module is in seconds.
there is JoomlaCode Tracker Item - id33641