| Re: XOOPS 2.3.x Upgrade Notes (from 2.0.x) |
| by zzzzsg on 2009/5/26 19:28:54 thank you mboyden |
| Re: XOOPS 2.3.x Upgrade Notes (from 2.0.x) |
| by mboyden on 2009/5/23 23:59:49 zzzzsg wrote: Quote: what do you mean by "Merge Core/Module Modifications" ? A lot of site owners will make small modifications to the core or, more frequently, to the modules. At the very least, most change the language files. So, if you have made any "hacks" to either your modules or your core, then you need to compare them to the originals and then update as appropriate to make them work to your needs. Many programs exist to compare two folders and note the changes file-by-file for you. Quote: what do you mean by "Move new xoops_lib and xoops_data folders into XOOPS_TRUST directory" ? Correct that they both point to the same place, but it's not circular, actually. For Protector and AltSys (and previous related) modules, GIJoe introduced the XOOPS_TRUST_PATH that made core PHP code more secure stored outside the web document root and thus more unavailable. As XOOPS embraces more of this methodology and links it into the core, some backwards compatibility must exist. That's what is going on. So, after you upgrade and update, find a secure location and move them and update the mainfile.php to their new locations. Quote: what do you mean by "Delete and redirect cache and templates_c folders via symbolic link "? Reading the installation instructions might assist. This was more of a checklist than a full set of instructions. These folders are "deprecated"  . They are now (more securely) in the XOOPS_TRUST_PATH/xoops_data/caches/ folders. To make a symbolic link (Windoze calls them shortcuts), you use the 'ln' command: 'ln -s /path/to/new/folder linkname', thus 'ln -s /home/mylogin/xoops_trusted/xoops_data/caches/smarty_compile templates_c' and 'ln -s /home/mylogin/xoops_trusted/xoops_data/caches/smarty_cache cache'.Quote: "Update FCKeditor module-specific configurations in all modules (if any)" I do have a rather extensive posting on FCKeditor, too, but realize some modules may need changes as you update that editor. The calls and method for passing variables to FCKeditor has changed a little. Module-specific configurations are in three files in the root of each module that start with fckeditor in the filename. If they aren't in the module directory, they don't exist for that module and thus can be ignored. Some of these are more extensive than others. Note: as the title of my post says, this checklist is for 2.0.x to 2.3.x; unfortunately I never used the 2.2 branch, so your mileage may vary. Hope that helps. |
| Re: XOOPS 2.3.x Upgrade Notes (from 2.0.x) |
| by zzzzsg on 2009/5/23 21:38:30 i managed to fix it. turns out that the old news 1.4 is not compatible with XOOPS 2.3.3. i updated the news module to 1.6.3 and all is well now. and there is no need to modify /modules/news/include/functions.php the following is okay even though /class/fckeditor/formfckeditor.php does not exist! (it exists in /class/xoopseditor/fckeditor) case 'fckeditor': if ( is_readable(XOOPS_ROOT_PATH . '/class/fckeditor/formfckeditor.php')) { require_once(XOOPS_ROOT_PATH . '/class/fckeditor/formfckeditor.php'); |
| Re: XOOPS 2.3.x Upgrade Notes (from 2.0.x) |
| by zzzzsg on 2009/5/18 22:44:24 hi mboyden thank you for the detailed instructions. what do you mean by "Merge Core/Module Modifications" ? how do you do a merge? what do you mean by "Move new xoops_lib and xoops_data folders into XOOPS_TRUST directory" ? in the mainfile.php, XOOPS_TRUST_PATH is defined as the XOOPS_PATH and the XOOPS_PATH is the path of the xoops_lib folder. So "Move new xoops_lib ... into XOOPS_TRUST" is moving the xoops_lib back into itself. define("XOOPS_TRUST_PATH", XOOPS_PATH); what do you mean by "Delete and redirect cache and templates_c folders via symbolic link "? how do we delete a folder than the redirect it? redirect from where? "Update FCKeditor module-specific configurations in all modules (if any)" where are the module-specific configurations in all modules? my fckeditor is not working after upgrading XOOPS from 2.2 to 2.3.3. thank you once again. --- ok i went to change /modules/news/include/functions.php originally it was "/class/fckeditor/formfckeditor.php" and i changed it to "/class/xoopseditor/fckeditor/formfckeditor.php" case "fck":^M if(!$x22) {^M if ( is_readable(XOOPS_ROOT_PATH . "/class/xoopseditor/fckeditor/formfckeditor.php")) {^M include_once(XOOPS_ROOT_PATH . "/class/xoopseditor/fckeditor/formfckeditor.php");^M $editor = new XoopsFormFckeditor($caption, $name, $value);^M }^M } else {^M $editor = new XoopsFormEditor($caption, "fckeditor", $editor_configs);^M }^M now the fckeditor appears in Submit News, but when i submitted a news with some contents and images, the News article submitted is blank .... |
| Re: XOOPS 2.3.3 Upgrade Notes from 2.0.18.1 |
| by jph000 on 2009/5/12 21:56:12 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 2.0.18.2 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 define("XOOPS_PATH", ""); // Physical path to the XOOPS datafiles (writable) directory WITHOUT trailing slash define("XOOPS_VAR_PATH", ""); // Alias of XOOPS_PATH, for compatibility, temporary solution define("XOOPS_TRUST_PATH", XOOPS_PATH); 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: xoops/modules/system/templates/ xoops/modules/system/templates/blocks/ 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. |
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $15.00 |
| Due Date: | Jul 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $15.00 |
|
|