Hello all. I have now narrowed down the protector install issue and I have Xoopsinfo to help this time too. (fyi to those who are tracking prior troubles).
This is a completely fresh install, new database, new files, everything.
Install worked after I gave an extended root path:
Previous install was going with /Volumes/XRAID01/Users/<mysite>/Sites - but could never see the modules installed, got path errors or blank screen (depending on the status of protector), and NO access at all through back end.
But this time I provided an extended path (same one) /Network/Servers/<myhost>/Volumes/XRAID01/Users/<mysite>/Sites
TAKE NOTE THAT THIS cleared up the module problem, and things went swimmingly (well), I was able to install and see the contents of and play around with News, Article, Backup, Xoopsinfo - in that order.
I had deliberately held 'Protector' back.
Now I carefully installed protector, setting up the files as instructed and editing in the mainfile to add XOOPS_TRUST_PATH as instructed.
That was fine and I was able to install the protector Module.
THEN I added the two lines at the end of mainfile.php. The result? As before - can't access any modules at all, just blank screens. Luckily I could page back in my browser to the Admin page, so then I commented out the added two lines with this code (which I'd added):
Quote:
include XOOPS_TRUST_PATH.'/modules/protector/include/precheck.inc.php'
And all was fine again. So the problem lies therein. I cannot use debug or Xoopsinfo when the code in mainfile is changed, because it all goes blank.
I tried putting double quotes around it like this Quote:
include XOOPS_TRUST_PATH."/modules/protector/include/precheck.inc.php"
and that gae the same problem.
SUMMARY: I had had two problems which confused the picture. The first is solved (above) the second is isolated.
Any thoughts on this?
Many thanks
Zaph