Upgrading From 3.1: Difference between revisions

From IHRIS Wiki
Line 7: Line 7:
We should back up the database.  Go into phpmyadmin, select your database, click on operations, and copy the  
We should back up the database.  Go into phpmyadmin, select your database, click on operations, and copy the  
database to a new name '''[database_name]'''.
database to a new name '''[database_name]'''.
==Creating the New Site==
==config.values.php==
===config.values.php===
Copy the existing site directory over to a new directory and update the '''config.values.php''' to:
Copy the existing site directory over to a new directory and update the '''config.values.php''' to:
*set the ''$i2ce_site_database'' to '''[database_name]''', the name of the new database  
*set the ''$i2ce_site_database'' to '''[database_name]''', the name of the new database  
*set  ''$i2ce_site_i2ce_path'' to '''[base_path]/i2ce''', the directory where the new version of I2CE is located
*set  ''$i2ce_site_i2ce_path'' to '''[base_path]/i2ce''', the directory where the new version of I2CE is located
==Site Configuration File==
==Site Configuration File==
===Versions===
===Versions===

Revision as of 13:20, 2 June 2009

These are directions for upgrading iHRIS Manage from version 3.1 under Ubuntu.

First Steps

Get The Source Code

You can either get the released or the development code. Suppose that [base_path] is the directory which contains i2ce, common, manage etc.

Backup Database

We should back up the database. Go into phpmyadmin, select your database, click on operations, and copy the database to a new name [database_name].

config.values.php

Copy the existing site directory over to a new directory and update the config.values.php to:

  • set the $i2ce_site_database to [database_name], the name of the new database
  • set $i2ce_site_i2ce_path to [base_path]/i2ce, the directory where the new version of I2CE is located

Site Configuration File

Versions

We need to go through your site configuration (XML) file and look for any conflicts and any requirements with version info from 3.1 and update them to the new version. For example, if you have something that looks like:

<requirement name='ihris-manage'>
  <atLeast version='3.1'/>
  <lessThan version='3.2'/>
</requirement>

it should be, for the 3.2 development version:

<requirement name='ihris-manage'>
  <atLeast version='3.2'/>
  <lessThan version='3.3'/>
</requirement>

or for the 4.0 release version:

<requirement name='ihris-manage'>
  <atLeast version='4.0'/>
  <lessThan version='4.1'/>
</requirement>

for the release version.

Modules

There were new modules created in the 3.2/4.0 code base for iHRIS Manage. Here are modules that did not exist in 3.1 which you probably want to enable in 3.2 or 4.0:

<enable name='PersonContact'/>
<enable name='ihris-manage-PersonDemographic'/>
<enable name='PersonEducation'/>
<enable name='PersonEmployment'/>
<enable name='PersonID'/>
<enable name='PersonLanguage'/>
<enable name='PersonNotes'/>