Additions:
If you upgrade using the mysql command line and your webERP database is called "weberp", add the line at the top of each upgrade script.
There is an upgrade script for Z_Upgrade_3.01-3.02.php that is required to be run - this converts the database tables and also applies necessary alterations to existing data. This should be run in preference to the manual approach discussed here for the step between 3.01 and 3.02.
Deletions:
If you upgrade using the mysql command line and your webERP database is called "weberp", add the line at the top of each upgrade script
Edited on 2008-01-01 16:02:38 by PhilDaintree
Additions:
There are three steps to Upgrading webERP
Download the latest version of webERP∞
Deletions:
Three steps to Upgrading webERP
Edited on 2008-01-01 16:01:14 by PhilDaintree
Additions:
~-Backup the existing scripts and copy over the new scripts
- Upgrade your database(s) so your existing data work with the new scripts
Deletions:
~-Backup the existing scripts and
Edited on 2008-01-01 15:59:46 by PhilDaintree
Additions:
replace path_to_old_webERP_scripts and path_to_new_webERP_scripts with the actual paths! Obviously, this could be more easily acheived using a graphical file manger. The aim is to copy all the company specific files such as logo and part pictures etc over to the new upgraded installation.
Deletions:
replace path_to_old_webERP_scripts and path_to_new_webERP_scripts with the actual paths!
this will copy all the company specific files such as logo and part pictures etc over to the new upgraded installation
Edited on 2008-01-01 15:58:22 by PhilDaintree
Additions:
cp -R /path_to_old_webERP_scripts/companies /path_to_new_webERP_scripts/companies
replace path_to_old_webERP_scripts and path_to_new_webERP_scripts with the actual paths!
follow the prompts to perform the database changes - any changes required to the data structure will also be performed using these scripts.
then ...
That's it!
If you have a version of webERP before 3.05 then you will need to run the sql to upgrade the database manually either using the mysql command line or phpMyAdmin (or other mysql client)
The step above is not necessary if you run the sql upgrade scripts from phpMyAdmin as you select the database using the GUI - simply go into the SQL tab of phpMyAdmin and load each upgrade script (see below) required in turn.
Be warned that whilst the code in webERP is mature and large changes are unlikely - it is certainly possible that some new code could cause the system to become unstable and therefore running off the CVS code has risks and is not recommended. However.....
you can then copy these scripts
Deletions:
cp -R /path_to_old_webERP_scripts/companies /path_to_new_webERP_scripts/companies
replace path_to_old_webERP_scripts and path_to_new_webERP_scripts with the actual paths!
This step is not necessary if you run the sql upgrade scripts from phpMyAdmin - simply go into the SQL tab of phpMyAdmin and load each upgrade script (see below) required in turn.
Edited on 2008-01-01 15:51:47 by PhilDaintree
Additions:
Three steps to Upgrading webERP
- Backup the database
- Backup the existing scripts and
Backup
Upgrade the Scripts
Whenever you modify scripts in webERP you should copy these outside the webERP directory tree - these will provide the checklist of the functionality you need to rework with the new database structure of the upgraded database. Ultimately it could well save you effort if you wish to stay current with the latest webERP scripts to consider contributing your modifications where they are done in a generic way back to the webERP project so they get incorporated in the next release. It is not a bad idea to also copy your config.php file as well as this contains the connection information for your installation.Extracting the archive of the new version under your web-server's root directory will create a webERP directory with all the new scripts in it.
If your installation is not under the webERP directory of your web-server then you will now need to copy the new webERP scripts over the old scripts using you favourite graphical file manager (or the command line if necessary).
Edit the new config.php file and set the variables - in particular the database user and password, the company selection choices, note that the database name is no longer required since this is now determined by the company directory - there must exist a company directory (under webERP/companies/ ) that is also the name of the mysql database. Don't forget also the demo mode - shows the user name and password to login as for the demo and is not appropriate in a live install. Since all the system configuration has been moved into the database the modifications required in config.php file are now minimal. All the files specific to the company installation are held under the companies directory - you will need to copy all directories under your old companies directory over to your new companies directory.
cp -R /path_to_old_webERP_scripts/companies /path_to_new_webERP_scripts/companies
replace path_to_old_webERP_scripts and path_to_new_webERP_scripts with the actual paths!
this will copy all the company specific files such as logo and part pictures etc over to the new upgraded installation
Upgrading the Database to Run with the New Scripts
Log in to your new system with a system administrator login and password.From version 3.04 there has been automated scripts that perform the upgrade to the database automatically. You must run each of these scripts in turn - by entering the URL directly in your browser's "location"/navigation bar.
Z_Upgrade_3.04-3.05.php
Z_Upgrade_3.05-3.06.php
Z_Upgrade_3.06-3.07.php
Z_Upgrade_3.07-3.08.php
etc...
You will need to do this process for each company you run webERP on.
Deletions:
Note there are notes specific to different versions: Upgrading to 3.05 see: to305
Whenever you modify scripts in webERP you should copy these outside the webERP directory tree -these will provide the checklist of the functionality you need to rework with the new database structure of the upgraded database. Ultimately it could well save you effort if you wish to stay current with the latest webERP scripts to consider contributing your modifications where they are done in a generic way back to the webERP project so they get incorporated in the next release.
Now copy the new WebERP scripts over the old scripts, eg.
cp newcvs_erp/* /var/www/html/current_erp/ -Rf
Edit the new config.php file and set the variables - in particular the database user and password, the company selection choices, note that the database name is no longer required since this is now determined by the company directory - there must exist a company directory (under webERP/companies/ ) that is also the name of the mysql database. Don't forget also the demo mode - shows the user name and password to login as for the demo and is not appropriate in a live install.
cp companies/weberp companies/yourdatabase -R
copy from the backup directory, your logo.jpg file into companies/yourdatabase/
cp part_pics/* companies/yourdatabase/part_pics -Rf
Copy over any customised PDF or Report templates from your script backup (ie. invoices, packing slips etc)
chown apache.apache current_erp/* -R
Remove any existing session files ( for example from /tmp/.current_erp_sessions/ )
Log in to your new system
Run the Z_Upgrade_3.01-3.02.php script (as of 28/1/06 the script may not exit cleanly, but the changes are made correctly)
Go to Setup and check your Company Preferences, there will be some changes to options that you may need to update.
Note the Address fields have changed.
If you are in Australia, and had Australian GST setup OK in 3.00, you must go to Tax Group Maintenance, Edit Default Tax Group, and Add the Australian GST to the Assigned Taxes Tax Group.
A bug from CVS versions before 24/1/2006, led that a field needs to be added to the table "config, add field
'SO_AllowSameItemMultipleTimes' with value '1'. Fixed in post 28/1/2006 versions.
Edited on 2008-01-01 15:28:46 by PhilDaintree
No differences.
Edited on 2008-01-01 15:27:36 by PhilDaintree
Additions:
Deletions:
Edited on 2008-01-01 15:27:02 by PhilDaintree
Additions:
Change the "weberp" above to the name of your database if it is not called weberp.
If you are running a multi-company setup, the upgrade scripts must be run against all company databases you run. Each company has a separate database under webERP.
Deletions:
Change the "weberp" to the name of your database if it is not called weberp.
Edited on 2008-01-01 15:23:20 by PhilDaintree
Additions:
Backup your MySQL database with whichever tool you understand and know how to restore a backup with.
where weberp_db_user is the mysql user name that has access to the weberp database, weberp_db_pwd is the user's password and weberp is the name of the weberp database. A new file containing the sql statements necessary to restore the database will be created called weberp.sql under the current directory. Keep this weberp.sql file as your backup of all your data prior to the upgrade.
The Easy Way to Backup
If you prefer to use a GUI to backup then phpMyAdmin∞ offers a convenient way to do this using the export tab - see below - by default from the main database view - the export tab selects all tables to be exported as SQL - clicking GO produces a DB dump to a file that you can specify - this saves having to use the command line
If you upgrade using the mysql command line and your webERP database is called "weberp", add the line at the top of each upgrade script
This step is not necessary if you run the sql upgrade scripts from phpMyAdmin - simply go into the SQL tab of phpMyAdmin and load each upgrade script (see below) required in turn.
Upgrading to the Latest CVS version
This will retrieve all the latest scripts to your new /tmp/weberp-cvs directory/folder
Deletions:
General Upgrading
This is an example from 3.0 to latest CVS version of 3.04/05
Backup your MySQL database with whichever tool you understand and know how to restore a backup with.
where weberp_db_user is the mysql user name that has access to the weberp database, weberp_db_pwd is the user's password and weberp is the name of the weberp database. A new file containing the sql statements necessary to restore the database will be created called weberp.sql under the current directory.
If your webERP database is called "weberp", add the line at the top of each upgrade script
Edited on 2007-12-01 15:50:20 by PhilDaintree
Additions:
Edit the new config.php file and set the variables - in particular the database user and password, the company selection choices, note that the database name is no longer required since this is now determined by the company directory - there must exist a company directory (under webERP/companies/ ) that is also the name of the mysql database. Don't forget also the demo mode - shows the user name and password to login as for the demo and is not appropriate in a live install.
Deletions:
Edit the new config.php file and set the variables.
Edited on 2007-12-01 15:46:58 by PhilDaintree
Additions:
Using mysqldump :
#mysqldump -u weberp_db_user - p weberp_db_pwd weberp > weberp.sql
where weberp_db_user is the mysql user name that has access to the weberp database, weberp_db_pwd is the user's password and weberp is the name of the weberp database. A new file containing the sql statements necessary to restore the database will be created called weberp.sql under the current directory.
If your webERP database is called "weberp", add the line at the top of each upgrade script
Change the "weberp" to the name of your database if it is not called weberp.
With each new version the necessary changes to the database are contained in sql scripts under the sql/mysql directory of the format
upgradeX.XX_Y.YY.sql
where X.XX is the version to upgrade from and Y.YY is the version to upgrade to.
Repeat the command using each upgrade script in sequence - starting from your current version of webERP.
Whenever you modify scripts in webERP you should copy these outside the webERP directory tree -these will provide the checklist of the functionality you need to rework with the new database structure of the upgraded database. Ultimately it could well save you effort if you wish to stay current with the latest webERP scripts to consider contributing your modifications where they are done in a generic way back to the webERP project so they get incorporated in the next release.
Deletions:
Add the line at the top of each upgrade script
Where weberp is the name of your database.
Repeat the command using each upgrade script in sequence.
Edited on 2007-10-12 02:37:00 by PhilDaintree
Deletions:
eltour
Edited on 2007-10-11 21:08:23 by CodarLilib
Additions:
eltour
Edited on 2007-10-05 11:47:28 by PhilDaintree
Additions:
Guide to Upgrading
Deletions:
==Guide to Upgrading==
Oldest known version of this page was edited on 2007-02-16 11:16:18 by EmDee []
Page view:
==Guide to Upgrading== **Note there are notes specific to different versions: Upgrading to 3.05 see: [[to305]] ** **General Upgrading ** This is an example from 3.0 to latest CVS version of 3.04/05 Assuming your on a linux system and have CVS installed. mkdir /tmp/weberp-cvs cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/web-erp login cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/web-erp co -P webERP cvs -z3 update -d -P Backup your MySQL database with whichever tool you understand and know how to restore a backup with. Add the line at the top of each upgrade script use weberp; Where weberp is the name of your database. The command to upgrade the database is as follows: mysql -uUSER -pPWD < path_to_upgraded_webERP_install/sql/mysql/upgradeXX.X-YY.Y.sql Repeat the command using each upgrade script in sequence. There should be no errors, if there are, stop now and investigate as the new scripts will not work if errors were returned. !** Backup the old weberp script directories. **! Now copy the new WebERP scripts over the old scripts, eg. cp newcvs_erp/* /var/www/html/current_erp/ -Rf Edit the new config.php file and set the variables. cp companies/weberp companies/yourdatabase -R copy from the backup directory, your logo.jpg file into companies/yourdatabase/ cp part_pics/* companies/yourdatabase/part_pics -Rf Copy over any customised PDF or Report templates from your script backup (ie. invoices, packing slips etc) chown apache.apache current_erp/* -R Remove any existing session files ( for example from /tmp/.current_erp_sessions/ ) Log in to your new system Run the Z_Upgrade_3.01-3.02.php script (as of 28/1/06 the script may not exit cleanly, but the changes are made correctly) Go to Setup and check your Company Preferences, there will be some changes to options that you may need to update. Note the Address fields have changed. If you are in Australia, and had Australian GST setup OK in 3.00, you must go to Tax Group Maintenance, Edit Default Tax Group, and Add the Australian GST to the Assigned Taxes Tax Group. A bug from CVS versions before 24/1/2006, led that a field needs to be added to the table "config, add field 'SO_AllowSameItemMultipleTimes' with value '1'. Fixed in post 28/1/2006 versions. !** Backup the new database before entering any transactions, if you have made a mistake, then you can fix it and reload the database**!