1
I'm experimenting with the XoopsModule hack to update the cache in real time and it's working quite nicely.
However, a few quirks are still at large:
a) It takes a few refreshs for the cache to kick in - I don't know if that's a problem with the hack or with XOOPS in general, but anyway it doesn't look like the update is happening as it is supposed to in the hacked method on XoopsModule
b) This is nothing to do with the hack itself but more to do with module writers and the use of logic to determine submenu items, but every time the main menu is loaded, it goes through the xoops_version.php and thus also the code to determine submenu items - this happens
even if you are viewing a page in another module. Now, the question is whether one should put in some checks to only display submenu items if the page viewed is in this module or whether one just has to accept this. A check in xoops_version.php like this
global $xoopsModule;
if ($xoopsModule->getVar('dirname') == 'module_name') {
// Build submenu items
}
would resolve it, but put off JavaScript/DHTML expanding menus. However, it is really a bitch, when I'm trying to get the front page to load with as few SQL queries as possible that such things are there. I am currently at 18 queries, 7 of which come from modules' xoops_version.php and 11 which are impossible to get rid of.
