Since I've move from 2.0.x to 2.2 final I had massive problems with several modules that act like lemmings.

My problem is that these modules were the reason using XOOPS and not giving up with it ages ago.

I need a patch, hack or something that will cause lines like: "include ($xoopsConfig['root_path']."header.php");" to start working again please.

before the usuall "it works for me"/"it no longer works like that" lines that are common in technical forums I would rather have no answer and assume no one gives a dman then come back to what looks like an answer but is in reality people blowing smoke out thier arse.

I am so super pee'd off with this problem and the spegitti of code that I waided through that there is a good chance my general tone is not the most plesent. Even so this reprisents a superhuman effort not to smash stuff and sware never to code again if I have to look at any more XOOPS code which generally gives my a similar unplesent sensation to being drunk. (if you want to know what's so unplesent about that: ask a glass of water).

change
$xoopsConfig['root_path']."header.php"
to
XOOPS_ROOT_PATH."/header.php"

and also look for
$xoopsConfig['xoops_url']
and replace with
XOOPS_URL