1
starstuff
Upgrading from XOOPS 2.3.x and 2.4.x
  • 2010/3/7 13:12

  • starstuff

  • Just popping in

  • Posts: 10

  • Since: 2006/9/23


"Upgrading from a previous version
-----------------------------------

Upgrading from XOOPS 2.3.x and 2.4.x(easy way)
1. Get the right update package from the sourceforge file repository
2. Overwrite files in XOOPS directory on your server with the content of /htdocs
* make sure that you copy the content of /xoops_lib to whatever directory you keep it on the server now (it should be your current XOOPS_TRUST_PATH directory), then delete the /xoops_lib directory. There can NOT be two directories with the content of /xoops_lib
3. If you have Protector previously installed, open the "mainfile.php" file , and remove the Pre-check and Post-check lines (if they exist):

include XOOPS_TRUST_PATH.'/modules/protector/include/precheck.inc.php' ;
include XOOPS_TRUST_PATH.'/modules/protector/include/postcheck.inc.php' ;

4. If you're upgrading from XOOPS 2.4.x, make the file /include/license.php writeable (permission 0777 on Linux)
5. Access <your.site.url>/upgrade/ with a browser, and follow the instructions
6. Follow the instructions to update your database
7. Delete the "upgrade" folder from your server
8. Update the "system" module from the modules administration interface. Other modules, especially "Profile" and "Protector" are recommended to update as well"


Make sure you do #3 correctly or your upgrade may fail to process.
I got a successfully loaded blank page when I tried to run the upgrade and lost all access to my website because of an extra "/" in the mainfile.php script.
(my error I'm sure but it happened and took me two agonizing
days to find)


"3. If you have Protector previously installed, open the "mainfile.php" file , and remove the Pre-check and Post-check lines (if they exist):

include XOOPS_TRUST_PATH.'/modules/protector/include/precheck.inc.php' ;
include XOOPS_TRUST_PATH.'/modules/protector/include/postcheck.inc.php' "



if ( !empty($ENABLE_PROTECTOR) ) {
//comment out or delete-
// @include XOOPS_TRUST_PATH . '/modules/protector/include/precheck.inc.php';
}
if (!isset($xoopsOption["nocommon"]) && XOOPS_ROOT_PATH != "") {
include XOOPS_ROOT_PATH."/include/common.php";
}
if ( !empty($ENABLE_PROTECTOR) ) {
//comment out or delete-
// @include XOOPS_TRUST_PATH . '/modules/protector/include/postcheck.inc.php';
}


Crazy stuff can happen but I have found that it is almost always my error.
Go Xoops!



2
lazyd
Re: Upgrading from XOOPS 2.3.x and 2.4.x
  • 2010/3/16 0:41

  • lazyd

  • Just popping in

  • Posts: 27

  • Since: 2003/8/20


Quote:
4. If you're upgrading from XOOPS 2.4.x, make the file /include/license.php writeable (permission 0777 on Linux)



Do you have to change this permission after you have finished your install/upgrade?

Login

Who's Online

205 user(s) are online (127 user(s) are browsing Support Forums)


Members: 0


Guests: 205


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits