5
There is an article in the FAQ about troubleshooting blank pages. If you have set the permissions correctly for XOOPS folders and module folders (check the readme in each module) there are a number of factors that can cause problems:
* PHP and MySQL versions.
Many modules will simply not work with PHP 5 or MySQL 5. Your guess is as good as mine as to which ones do.
* PHP Register_globals.
It should be OFF for best security, but again some old modules may not work with this setting. You can overide with htaccess, but it's not advisable.
* Corrupt PHP files.
You should always use ASCII (text) mode to FTP PHP files. Some cheaper FTP apps auto-detect incorrectly and use binary mode. It shouldn't make a difference - but in my experience it can, especially if a module was developed using a UNIX or Mac text editor.
* Trailing spaces or line breaks.
A trailing space or line break after the closing PHP tag will cause the file to fail. A common problem if you're not careful when editing config files like mainfile.php, especially if you edit online using the CPanel or Plesk file editor.
* PHP Safe Mode.
This is nearly always ON by default. To be honest, this has never affected any XOOPS module in my experience (it's ON on my server) but I suppose it could.
To troubleshoot, enable debug in XOOPS admin and check the output. 'Undefined variable' notices could (not always) indicate that a module needs register_globals ON.
HTH
A thread is for life. Not just for Christmas.