is there a secure scenario for updating an exisiting 3.4.b instaltion to 3.4.c ? Maybe file patches and sql commands? I think a new installation of alresco every time an update comes up is a bit un-handy, isn't it?
No need for that. Just follow the normal upgrade instructions.
But the normal upgrade instructions say that "The recommended process for upgrading involves a new installation of the Alfresco binaries and configuration and an in-place upgrade of a copy of the repository" Do you have something simpler?
i subscribe to tearalongs view. There must be a simpler way to perform an uprade instead of doing a new installation. Or are there other update instructions anywhere in the alfresco docs which we didn't find yet?
Meanwhile i've read about some issues with the german language installation within 3.4.c so i have to cancel this update and wait till 3.4.d will be released (any release dates yet?) but this will lead to the same question: What's the update scenario from 3.4.b to 3.4.d …
delete in webapps: alfresco/, alfresco.war, share/, share.war
download war-bundles from sourceforge containing alfresco.war, share.war
copy war files to webapps dir in tomcat
cross fingers
restart
read carfuly the catalina.out in tomcat/logs for any errors
If you allready have a running Alfresco you shouln't have any problems based on the language file issue since this error only occurs during the very first start of alfresco when the base respository entries are created.
thanks for your upgrade-scenario tip. Of course a "cross fingers"-patch is not what a production upgrade should be, but better than a complete reinstallation. Are there any considerations within the alfresco team about using a "svn" command to upgrade the alfresco files?
