I have a site hosted with a provider that doesn't allow access below documentroot, but after doing a quick-install to upgrade to 2.3.3 I'm getting the familiar red warning boxes in administrator. I've searched and see lots of recommendations to move and/or rename these directories, but other than modifying mainfile.php I haven't seen any other suggestions.

Renaming the directories and modifying the paths in mainfile.php renders the site unreachable, so I named them back to what they were before for now.

What procedure is required to rename these directories and have XOOPS recognize the changes?

Thanks.

Quote:
This should not be a problem.
Check that the XOOPS_PATH and XOOPS_VAR_PATH have the correct definition (uppercase - lowercase!)
Check the file permissions are still correct for the directories after the rename.
Check that the Protector includes at the bottom use the correct path.
Don't forget to alter your mainfile.php its permission before and after altering.

I had some similar experiences reported here.

I didn't end up getting to the bottom of it.

ghia,

I'm not sure what I did wrong the first 2 or 3 times I tried, but it worked fine this time. Thanks.

I think this is a fix but Im no php expert...
Open admin.php find lines 60-68 and replace the code with the following..

if (strpos(XOOPS_PATH, XOOPS_ROOT_PATH . '/xoops_lib') !== false || strpos(XOOPS_PATH, $_SERVER['DOCUMENT_ROOT'] . '/xoops_lib') !== false) {
xoops_error(sprintf(_AD_WARNINGXOOPSLIBINSIDE, XOOPS_PATH));
echo '<br />';
}

if (strpos(XOOPS_VAR_PATH, XOOPS_ROOT_PATH . '/xoops_data') !== false || strpos(XOOPS_VAR_PATH, $_SERVER['DOCUMENT_ROOT'] . '/xoops_data') !== false) {
xoops_error(sprintf(_AD_WARNINGXOOPSLIBINSIDE, XOOPS_VAR_PATH));
echo '<br />';
}

During installation if you created a directory and renamed your files you dont need to do the following...just the above

save the file back to your server... create a new directory and name it whatever and place your xoops_data and xoops_lib inside your new directory....okay open up mainfile.php and find line 27 should look like this...
define( 'XOOPS_PATH', '/home/content/h/l/t/poopy/html/your new directory name goes here/xoops_lib' );

now find line 29 and do the same thing....save your file back to your server...and change the file permissions to 444...go to your admin page and see if the messages are gone you may have to change the file permissions for your xoops_data directory too.