Re: XOOPS 2.3.3 Upgrade Notes from 184.108.40.206
My installation notes and suggestions follow the standard, supplied upgrade instructions below.
Upgrading from XOOPS 2.0.* above 2.0.14 and 2.2.* (using the full package)
1. Move the "upgrade" folder inside the "htdocs" folder (it's been kept out as it's not needed for full installs) on your local machine
2. Delete htdocs/mainfile.php, htdocs/install/, htdocs/cache/, htdocs/extras/, htdocs/template_c/, htdocs/themes/ and htdocs/uploads/ from the "htdocs" folder on your LOCAL machine
3. Upload the content of the htdocs folder on your LOCAL machine over your existing files on your server
4. For security considerations, you are encouraged to move directories xoops_lib (for XOOPS libraries) and xoops_data (for XOOPS data) out of document root, or even change the folder names.
5. Make the directory of xoops_data/ writable; Create and make the directories of xoops_data/caches/, xoops_data/caches/xoops_cache/, xoops_data/caches/smarty_cache/ and xoops_data/caches/smarty_compile/ writable.
6. Ensure the server can write to mainfile.php
7. Access <your.site.url>/upgrade/ with a browser, and follow the instructions
8. Follow the instructions to update your database
9. Write-protect mainfile.php again
10. Delete the upgrade folder from your server
11. Update the "system" module from the modules administration interface, other modules are recommended to update as well
Following the above instructions, Step #7 resulted in an error:
"This page cannot be displayed due to an internal error. You can provide the following information to the administrators of this site to help them solve the problem:
Error: Smarty error: the $compile_dir 'XOOPS_VAR_PATH/caches/smarty_compile' does not exist, or is not a directory."
Well ... on a hunch (having gone through the 220.127.116.11 to 2.3 and 2.3.2b to 2.3.3 upgrades on a PHP5 Test Site, I edited the mainfile.php file (which originally came from version 2.0.6). These lines were added, with values (in the same location as in the mainfile.dist.php file):
// For forward compatibility
// Physical path to the XOOPS library directory WITHOUT trailing slash
// Physical path to the XOOPS datafiles (writable) directory WITHOUT trailing slash
// Alias of XOOPS_PATH, for compatibility, temporary solution
After Step #11, go to the Template Set Manager and check for new System templates to generate -- there was 1 new one, making a total of 28.
Do Step #4, which also requires editing the mainfile.php file.
Also, when the tar.gz file is created under Mac OS X, watch out for all the "._" files, in particular in the directories:
as the Template Set Manager will show these Mac files as templates to generate. Remove them before updating System theme template files!
The structure and (some) content of the new xoops/themes/default/style.css may need to be edited into your custom theme file, e.g., themes/mytheme/style.css.