LetoDMS Community Forum
Upgrade from 1.7.2 to 3.2.1 - Printable Version

+- LetoDMS Community Forum (https://community.letodms.com)
+-- Forum: LetoDMS Support (https://community.letodms.com/forumdisplay.php?fid=4)
+--- Forum: Installation Problems (https://community.letodms.com/forumdisplay.php?fid=9)
+--- Thread: Upgrade from 1.7.2 to 3.2.1 (/showthread.php?tid=404)



Upgrade from 1.7.2 to 3.2.1 - Ernesto - 12-01-2011

Hi Gurus,
I need to upgrade my letodms from 1.7.2 version to 3.2.1 version.
I have seen the upgrade URL (http://www.letodms.com/doc/doku.php?id=install:upgrade) but it has been unusefull.
I followed this steps:

01) I have created an archive of our installation folder (tar xvf mydms_1.7.2.tar /PATH-MYDMS/mydms_1.7.2)
02) I make an archive of our data folder where the documents are stored (the content directory on /PATH-MYDMS/mydms_1.7.2)
03) I created the dump our current DB by mysqldump command of "mydms_1.7.2" database
04) I create the new database called mydms_3.2.1 on MySQL server
05) I restored the mydms_1.7.2 dump on the new database (mydms_3.2.1)
05) I downloaded LetoDMS-3.2.1.tar.gz
06) I unzip and untar the LetoDMS-3.2.1.tar.gz on /PATH-MYDMS/mydms_3.2.1
07) Copied the content directory of /PATH-MYDMS/mydms_1.7.2 on /PATH-MYDMS/mydms_3.2.1 with "cp -Rp" command in order to maintain the permissions
08) Modified the /PATH-MYDMS/mydms_3.2.1/inc/inc.Settings.php file in order to satisfy the new PATH e the new Database precisely:
- var $_rootDir
- var $_httpRoot
- var $_contentDir
- var $_ADOdbPath
- var $_dbHostname
- var $_dbDatabase
- var $_dbUser
- var $_dbPass
09) I have executed from my browser all "update.php" files and from my phpmydmin the "update.sql" contained on /PATH-MYDMS/mydms_3.2.1 precisely:
UPDATE-v1.8.1/ UPDATE-v1.9/ UPDATE-v2.0.1/ UPDATE-v3.0.0/ UPDATE-v3.1.0/ UPDATE-v3.2.0/
10) When I open the URL I have this error:
This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying.
For more information about HTTP errors, see Help.

What's the right flow to upgrade the mydms?
Thanks in advance.
BR.
Ernesto



RE: Upgrade from 1.7.2 to 3.2.1 - steinm - 12-01-2011

(12-01-2011, 02:42 PM)Ernesto Wrote: Hi Gurus,
I need to upgrade my letodms from 1.7.2 version to 3.2.1 version.
I have seen the upgrade URL (http://www.letodms.com/doc/doku.php?id=install:upgrade) but it has been unusefull.
I followed this steps:

01) I have created an archive of our installation folder (tar xvf mydms_1.7.2.tar /PATH-MYDMS/mydms_1.7.2)
02) I make an archive of our data folder where the documents are stored (the content directory on /PATH-MYDMS/mydms_1.7.2)
03) I created the dump our current DB by mysqldump command of "mydms_1.7.2" database
04) I create the new database called mydms_3.2.1 on MySQL server
05) I restored the mydms_1.7.2 dump on the new database (mydms_3.2.1)
05) I downloaded LetoDMS-3.2.1.tar.gz
06) I unzip and untar the LetoDMS-3.2.1.tar.gz on /PATH-MYDMS/mydms_3.2.1
07) Copied the content directory of /PATH-MYDMS/mydms_1.7.2 on /PATH-MYDMS/mydms_3.2.1 with "cp -Rp" command in order to maintain the permissions
08) Modified the /PATH-MYDMS/mydms_3.2.1/inc/inc.Settings.php file in order to satisfy the new PATH e the new Database precisely:
- var $_rootDir
- var $_httpRoot
- var $_contentDir
- var $_ADOdbPath
- var $_dbHostname
- var $_dbDatabase
- var $_dbUser
- var $_dbPass
09) I have executed from my browser all "update.php" files and from my phpmydmin the "update.sql" contained on /PATH-MYDMS/mydms_3.2.1 precisely:
UPDATE-v1.8.1/ UPDATE-v1.9/ UPDATE-v2.0.1/ UPDATE-v3.0.0/ UPDATE-v3.1.0/ UPDATE-v3.2.0/
10) When I open the URL I have this error:
This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying.
For more information about HTTP errors, see Help.

What's the right flow to upgrade the mydms?

Most of what you have done is ok, but there might be some missing pieces. Did you install LetoDMS_Core? You should not modify inc.Settings.php. The configuration is now in settings.xml.

Is there any error in your apache error log?

Uwe