[Xoops-trackers] [ xoops-Feature Requests-1417839 ] Cache and Preferences requires seperation

Feature Requests item #1417839, was opened at 2006-01-29 09:01
Message generated for change (Comment added) made by herkocoomans
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1417839&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Administration
Group: XOOPS 2.x
Status: Open
Resolution: None
Priority: 1
Submitted By: Xoops_Gold (xoops_gold)
Assigned to: Nobody/Anonymous (nobody)
Summary: Cache and Preferences requires seperation

Initial Comment:
Hallo!

I noticed a major difference after I made some changes
in the system preferences under:

modules/system/admin.php?fct=preferences&op=showmod&confcat_id=1&mod=1

So If I want to have one new theme selected I need it
to be atleasted listed through the system preferences
for it to appear in the themes block.

Updating or submitting this, it deleted the entire
cache. But this is not what I wanted. I did not change
or wanted to change aningthing in the chache. Simply
changing anything in this form deletes everything in
the chache folder.

This slows down the entire site. There were blocks and
modules with 1 Month chache preference.

I beleive that there should be a clear seperation
between the two, like Cache controller annd Preference
Manager...

----------------------------------------------------------------------

>Comment By: Herko Coomans (herkocoomans)
Date: 2006-01-29 10:26

Message:
Logged In: YES 
user_id=441189

Actually, this behaviour makes sense. When you change
something in your general settings, which are site-wide by
default, you want these changes to resolve throughout the
whole site immediately, and not just after a month. For
instance, if you switch to another template set, you want to
see the effect immediately, not after the time all the
blocks have 'expired' their cache lifetimes.
Plus, it's only the lifetimes that are reset, so the site is
only a bit slower for the very first person that sees the
pages again, because at that time the new cached versions
are generated and used for consecutive visits.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1417839&group_id=41586