I have a headache and I am upgrading a website from XOOPS 2.2 to 2.5.4. This website is also being moved from my own server to a shared web hosting account on another web host and for 2 days I was sure that this was the reason for my headache. No longer can I tail -f access_log or error_log to see what is going on because those files are not available to my userid. Also, I cannot modify httpd.conf to change the website home but I must use .htaccess instead. I am convinced this is a reason for my pain.
Or is it….
XOOPS (xXtensible Object Oriented Portal System) is written in PHP and uses MySQL and what was once merely a portal system in the earlier versions is not on the way to becoming a powerful content management system. It is flexible and lightweight with the extreme ease of adding, modifying, or disabling modules.
As I am moving this website I am learning more about this application. Some of the issues I am discovering are listed below (and my lack of knowledge of these I am sure was the cause of my headache) :
1. A blank page in the website can mean that the module being used is not compatible with the newest version of the software. Try deactivating each module one by one until the blank page is gone.
2. A blank page can also mean that you are on a PHP 5 web host and the module was written for PHP4. Again try deactivating each module until you determine the culprit. Then you can either find a compatible version or change the module yourself for PHP 5.
3. In the preferences section of the control panel it is possible to set debugging “on”. There are 3 levels of debugging that are possible. These are very useful in helping to track down any problems in modules and in the behavior of the website.
Stay tuned for more tips as I discover them.