Back to page

− Links

 Print 

XOOPSCubeLegacy​/HowToUpgrade​/FromX2JP :: Web Application Platform

wiki:XOOPSCubeLegacy/HowToUpgrade/FromX2JP

XOOPSCubeLegacy​/HowToUpgrade[1]

Table of contents
  • How to upgrade from XOOPS 2.0.x JP
    • STEP 1 Preparation
    • STEP 2 Close site
    • STEP 3 File replace
    • STEP 4 Upgrade
    • STEP 5 Open site

How to upgrade from XOOPS 2.0.x JP anchor.png[2]

Try it first at home! Means that it's preferable to try the upgrade in a copy of your site, in your pc and then move it to the real world!

Page Top

STEP 1 Preparation anchor.png[3]

STEP1.png
  1. Check your server PHP[4] version. (PHP[4] >= 4.3.11)
  2. You have to upgrade first your XOOPS 2.0.x JP to the latest version --- XOOPS 2.0.16a JP
  3. Check the compatibility of your modules on this page[5]. And download the latest version or patch release.
  4. Check whether your modules require the system module for compatibility. And, if you need it, download the latest system module[6]
Page Top

STEP 2 Close site anchor.png[7]

STEP2.png
  1. Select 'default' theme. And, disable selectable themes.
  2. Close your site.
  3. Change the debug mode to : PHP[4] debug mode.
  4. Turn off your custom blocks which use PHP[4] content-type. (If the block depends on X2's global variables, expect that may not work perfectly)
  5. And, for more safety, turn off all of blocks, especially system blocks.
  6. Reset the start-module. If the start module is not compatible, it will break your site.
  7. Remove all your cache-settings, because Legacy provides a different cache concept from X2.
Page Top

STEP 3 File replace anchor.png[8]

STEP3.png
  1. Delete all of files, except mainfile.php and the following directories:
    • images
    • themes
    • uploads
    • modules
    • your XOOPS_TRUST_PATH
  1. Overwrite with the package. Do not write the "install" folder. Needed only in fresh installations.
  2. Replace all of your modules with their latest version and, or their patched version which you has gotten at STEP 1.
    1. You don't need to remove files from XOOPS_TRUST_PATH. Just update your D3-type modules to the latest version.
    2. Don't forget to copy the legacy modules to your modules folder!
    3. If you are using d3forum with comment integration don't forget to copy the 3 php files from "html/class/smarty/plugins" folder in the appropriate place.
Page Top

STEP 4 Upgrade anchor.png[9]

STEP4.png
  • Patch your mainfile.php.

How to patch your mainfile.php? It's very easy. Modify your mainfile.php with a text editor alike notepad as follow.

From:
if (!isset($xoopsOption['nocommon']) && XOOPS_ROOT_PATH != '') {
  include XOOPS_ROOT_PATH."/include/common.php";
}

To:
if (!defined('_LEGACY_PREVENT_LOAD_CORE_') && XOOPS_ROOT_PATH != '') {
  @include_once XOOPS_ROOT_PATH."/include/cubecore_init.php";
  if (!isset($xoopsOption['nocommon']) && !defined('_LEGACY_PREVENT_EXEC_COMMON_')) {
    include XOOPS_ROOT_PATH."/include/common.php";
  }
}

If you use XOOPS Protector, you adjust your mainfile.php more. Read 'About[10] mainfile.php' of this document[11].

Then chmod of templates_c and cache folder to 777. (uploads is already set)

Click 'Refresh' button of your browser.

  • Install required modules in the 2nd installer.
  • Go to the module management, and update all of your modules.
  • Copy XUpgrade directory in Archive(Package_Legacy/extras/XUpgrade) into your server's modules directory (XOOPS_ROOT_PATH/modules/).
  • Go to the module management and install XUpgrade. By XUpgrade installation, your System module's preferences can be succeeded to legacy base modules.
  • After installation, you may optionally uninstall XUpgrade.
Page Top

STEP 5 Open site anchor.png[12]

STEP5.png
  1. Update all of modules, and check their working.
  2. If you don't need the system module, uninstall it. And, delete the directory from your server.
  3. Install your blocks except the custom-block.
  4. Install your custom blocks using two windows. One window is for the homepage to check the custom block. Another window is for the control panel to uninstall trouble custom blocks.
  5. Recover all preferences.
  6. Open your site.
  7. After you have finished checking your site settings, change the debug mode to OFF.

Last-modified: 2007-09-14 (Fri) 12:55:13 (JST) (4473d) by Anonymous