Re: Important configuration files erased during upgrade

Hello again also :) ,

I also fully agree that an upgrade should not 
break an installation and/or erase existing 
configuration files, obviously if you had this 
issue it may be a bug and not a feature.

We normally make a backup of each and every file 
that is replaced during an upgrade procedure. For 
example, you should have in your WEB-INF 
directory a file web.xml_4_0_5, web.xml_4_0_6 and 
web.xml_4_0_6_01 . The web.xml_4_0_5 is the 
backup file made from the 4.0.5 Jahia install 
when applying the 4.0.6 patch. The same goes 
normally for the ldap configuration files or any othe replaced file.
Have you checked if these files were present ?
We unfortunately have currently no mechanism in 
our upgrade process to only modify the various 
configuration files, we hope to change that in the future.
In regards to this we normally add to each readme 
file for a patch a section pointing that out 
(like in the 4.0.5 upgrade readme 
http://www.jahia.net/download/jahia4/4_0/patch/README_4_0_5.html 
) , and if possible a diff file of all 
differences between the old and the new file to help merging changes.
Unfortunatley, it seems this part was not 
included in the 4.0.7_01 readme (but was still 
present in the previous one : 
http://www.jahia.net/download/jahia4/4_0/patch/README_4.0.6_01.html 
), we will correct this mistake.

Best regards,
Michel Romy



>Hello again,
>
>I would like to report a problem that occurred 
>during our upgrade from version 4.0.5 to version 
>4.0.7_01. When we upgraded our Jahia server from 
>version 4.0.5 to 4.0.7_01 the "web.xml" file was 
>replaced with a new one, erasing the changes we 
>made before. Our TEST web site was unavailable until we found the problem.
>
>We also lost all our LDAP configuration files 
>during the upgrade, we had to go back to the 
>backed up files and restore them manually.
>
>I hope this is not a feature of your upgrade 
>scripts, but only a bug. If this is a feature, 
>you should add a warning in the README file. I 
>think a serious software company should never 
>release a patch that breaks his own software...
>
>Thank you for listening,
>Pierre Lemieux, bibliothèque de l'Université Laval