1322
Quote:
No problem. You can hide any parts if you want.
However, to make it work, you must install the whole package before predator gives a stand-alone module.
kaliman wrote:
Is it possible to hide the other parts of the modules?
No problem. You can hide any parts if you want.
However, to make it work, you must install the whole package before predator gives a stand-alone module.
1323
yes, so far this hack is just interesting, although it may work for personal hack.
To make it ready for xoops, there are many things to do.
Considering the xoops-notificationHandler, xoops-searchHandler and this hack(or further hack), as well as some cross-module hacks I am working on, I feel that XoopsModule might need some modification. Just brief thought.
To make it ready for xoops, there are many things to do.
Considering the xoops-notificationHandler, xoops-searchHandler and this hack(or further hack), as well as some cross-module hacks I am working on, I feel that XoopsModule might need some modification. Just brief thought.
1324
Quote:
yes, not fully tested though.
PyromanFO wrote:
*edit* Okay, so another question, do the modules currently support these updateCache and clearCache functions?
yes, not fully tested though.
1325
Per page cache update is of course the goal but not possible in xoops' current structure.
For instance, when a news article submitted, not only the news article page that can be determined by using a cache-id available by editing the news module, but also relevant blocks that needs module-wide handling. This is why pre module cache update is employed in the hack.
Per page cache update might be feasible if xoopsModule is modified correspondlingly.
For instance, when a news article submitted, not only the news article page that can be determined by using a cache-id available by editing the news module, but also relevant blocks that needs module-wide handling. This is why pre module cache update is employed in the hack.
Per page cache update might be feasible if xoopsModule is modified correspondlingly.
1326
Quote:
No, it updates only relevant cached files.
However, we can not determine which cached files are really affected by the content change so all cached files related to the module, in which the content change occurs, will be updated.
EDIT:sure, to find out the specific files that affected by the content change is a goal
PyromanFO wrote:
The link you gave merely clears the cache when something changes.
No, it updates only relevant cached files.
However, we can not determine which cached files are really affected by the content change so all cached files related to the module, in which the content change occurs, will be updated.
EDIT:sure, to find out the specific files that affected by the content change is a goal
1327
might be misunderstanding but ::
Quote:
So far, I guess yes
Quote:
The link I gave is intended to do similar things.
However, we can not make all the modules content-based-caching, for instance, when click is counted.
So, the right way might be both, time-based and 'content'(I call it event)-based
Quote:
PyromanFO wrote:
I was wondering, with XOOPS how does the caching work? I've read threads where it seems like a simple time based thing.
So far, I guess yes
Quote:
PyromanFO wrote:
I edited the News module to have content based cacheids. So now as soon as something changes you see it, but you're viewing static content when nothing has changed.
The link I gave is intended to do similar things.
However, we can not make all the modules content-based-caching, for instance, when click is counted.
So, the right way might be both, time-based and 'content'(I call it event)-based
1330
This is great. I have been always looking for.
I would help with no hesitation if it is kicked-off
I would help with no hesitation if it is kicked-off
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | May 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|