Here is the output from /admin.php with debug_mode=1
--
None All errors (0) queries (8) blocks (0) extra (2) timers (3)
Errors
Notice: Use of undefined constant E_STRICT - assumed 'E_STRICT' in file /class/logger/render.php line 98
Queries
SET NAMES 'utf8'
SELECT * FROM config WHERE (conf_modid = '0' AND conf_catid = '1') ORDER BY conf_order ASC
SELECT sess_data, sess_ip FROM session WHERE sess_id = '82e3ead0a2baafd24362c509e9ebd53f'
SELECT * FROM users WHERE uid = '1'
SELECT * FROM group_permission WHERE (gperm_name = 'module_admin' AND gperm_modid = '1' AND (gperm_groupid = '1' OR gperm_groupid = '2'))
SELECT * FROM modules WHERE (hasadmin = '1' AND isactive = '1') ORDER BY weight ASC, mid ASC
SELECT * FROM content WHERE parent_id=0 ORDER BY blockid
SELECT catid,title FROM content_cat
Total: 8 queries
Blocks
Total: 0 blocks
Extra
Included files: 48 files
Memory usage: 2168680 bytes
Timers
XOOPS took 0.079 seconds to load.
XOOPS Boot took 0.040 seconds to load.
Module init took 0.039 seconds to load.

Humm, I see you have PHP 4.
Which modules do you use?
Some might expect PHP 5 and calling a PHP 5 function might terminate your script.

Good suggestion. However ...

(a) release notes say: Any PHP version >= 4.3 is supported by XOOPS 2.3.3. My server is using 4.3.9

(b) it's the main admin.php page that is returning blank.

(c) the only modules I have installed are News and TinyContent. To my knowledge, neither require PHP 5.

--

That said, it still may be that PHP5 would solve my problems, but the analysis doesn't lead me to PHP5 as a requirement.

I would upgrade the server except that it's running a production site with LOTS of activity and I can't risk the downtime.

--

I've been a XOOPS admin and site builder since 2004. What is baffling here is that ALL of the site modules and pages work with the exception of the admin sections. Moreover, nothing I've tried is giving me any feedback or errors; just blank pages.

When I turned debug_mode on (conf_value = 1) I got some feedback (see earlier post) but it didn't provide any useful information regarding the error.

This server is CentOS. Is there a way to output these php errors to a log file? Other suggestions?

BTW ... how did you know the server is using PHP4?

I think because E_STRICT error level is not supported by php 4 and in your debug it shows up not defined.

if you use news 1.63 it requirer php 5 and MySQL >= 3.23

read here http://xoops.instant-zero.com/modules/repository/product.php?prod_id=1

Quote:Only PHP 5 knows what the value of E_STRICT is.
Quote:You are right: XOOPS should be compatible with PHP 4. However 2.3.3 is the last version, from then 5.2 or something will be the minimum.
But sometimes something creeps in, as this E_STRICT.
Quote:Yes, but this page works close with the modules present and executes code of them. So a bad module can cripple its functionality.
Quote:
News 1.63 does require PHP 5.

Is it possible to upgrade to PHP 5?