Despite mainfile.php pointing to the new path, some file seems to be looking for the old path.

Permission was 755 for one parent directory, but changing to 777 has not resolved it.

Here is the complete error:
Error: Smarty error: the $compile_dir '/xxxxoops_data/caches/smarty_compile' does not exist, or is not a directory.
Backtrace:
/class/smarty/Smarty.class.php (1092)
/class/smarty/internals/core.write_compiled_resource.php (20)
/class/smarty/Smarty.class.php (1430)
/class/smarty/Smarty.class.php (1260)
/class/theme_blocks.php (141)
/class/theme_blocks.php (92)
/class/theme_blocks.php (36)
/class/theme.php (243)
/class/theme.php (73)
/header.php (66)
/index.php (77)

I moved the contents of the xoops_data folders from one location to another. Should I delete the files in any of the directories under xoops_data?

Here is what the mainfile.php looks like now however if I remove the old xoops_data folder from the root directory, the site fails with the error noted above.

// For forward compatibility
// Physical path to the XOOPS library directory WITHOUT trailing slash
define( 'XOOPS_PATH', '/home2/mysite/newfolder/xoops_lib' );
// Physical path to the XOOPS datafiles (writable) directory WITHOUT trailing slash
define( 'XOOPS_VAR_PATH', '/home2/mysite/newfolder/xoops_data' );
// Alias of XOOPS_PATH, for compatibility, temporary solution
define("XOOPS_TRUST_PATH", XOOPS_PATH);

Smarty compile permissions are wide open, 777.

I have an installation where I changed the names of the xoops_lib and xoops_data folders but located them in the root folder.

I want to move them out of the root folder but after doing so and editing mainfile.php to reference the new locations, I get the following error:

Error: Smarty error: the $compile_dir '/xxxxx_data/caches/smarty_compile' does not exist, or is not a directory.

Apparently I am missing something. What are the proper steps to moving the xoops_lib and xoops_data folders?

Thanks.
I think I'm getting it now.
I found this information helpful for my level.

I've inquired with my host company to see if there are any issues with the use of .htaccess. Hopefully tomorrow this will all be sorted.

I hadn't noticed it before but there is a php.ini file in the root folder. All it says is register_globals = Off.

Is this the file to be copied to the directories?

I've read the .htaccess threads but don't understand that quite frankly. I'm not there yet.

Yes,

I did notice that my site is running on PHP 4.4.4 whether that matters or not.

The Control Panel Homepage has a little red x beside register_globals.

Accessing phpinfo in the root folder indicates that register_globals is off.

Accessing phpinfo in the /modules/protector folder indicates that register_globals is "on" for both the Local value and the Master value.

Protector Security Advisor indicates that register_globals is "on".

This makes sense to me that Protector gets the same result. Now the question is whether there is something needing to be done about it?

Thanks.

Protector still indicates that it is on but the summary your file returns shows that it is off.

I have the latest Protector installed and it seems to be working with the exception that in the Security Advisory it is telling me that Register Globals is "on".

I have asked the hosting company about this and been provided with a link to my phpinfo. That link indicates that the configuration of the PHP Core is set for both Local Value and Master Value of Register_Globals is "off".

Does this suggest a vulnerability here or perhaps that I have erred somehow in installing Protector?

What XOOPS version, what file did you modify?

Thanks.
I misread your post and changed the block_type from 'C' to 'H' and then back again.
The c_type is 'S'.
I tried editing it and it showed up but now seems to be missing again. All very interesting to me.
That was the last custom block from the 2.2.4 days. The new ones seem to behave properly.

Do you suggest that I install the latest Altsys as noted in the post you mentioned or am I likely out of the woods if I don't have a need for the Custom Blocks created with 2.2.4?