6
Mamba,
/xoops-data (called xoops-data23 on my installation) is outside the root and it and all folders are set to 777
I have cleaned out caches/smarty_compile multiple times as I worked on changes. I just emptied xoops_cache too. templates_c is also empty. The problem persists.
Here is now my XOOPS_TRUST_PATH is set in mainfile.php:
// For forward compatibility
// Physical path to the XOOPS library directory WITHOUT trailing slash
define( 'XOOPS_PATH', '/home1/public_html/xoops_lib23' );
// Physical path to the XOOPS datafiles (writable) directory WITHOUT trailing slash
define( 'XOOPS_VAR_PATH', '/home1/akassoc/xoops_data23' );
// Alias of XOOPS_PATH, for compatibility, temporary solution
define("XOOPS_TRUST_PATH", XOOPS_PATH);
I am getting pretty frustrated. I had a second instllation of 2.3.3 that did show the uninstalled modules. It was minimally developed, so I copied files from my problem installation to it and copied the database tables also. Now I have the same problem there. Obviously some file, either in the XOOPS installation or in the db is causing this, but I can't figure out which.
Regarding the protector module, it apparently was not installed in this XOOPS installation, even though I thought I did. Possibly I made a mistake there. mainfile.dist.php does not contain the protector statements and I have set:
$ENABLE_PROTECTOR = false;
in mainfile.php.
I would be happy to give you temporary admin access if you want to look at it. The 2.3.3 site is not live yet as I'm still working on it.
Server details are:
Linux, php 5.2.9, mySQL 5.0.75
An help will be greatly appreciated. I don't particularly want to have to rebuild this whole thing again.
Barry Cooper
Barry Cooper
Sweet Home, Oregon
