CiviCRM Community Forums (archive)

It would be very useful to have a quick upgrade guide for a minor version revision posted here as a sticky topic. (Joomla and Drupal versions)

I guess that in principle there should be no database schema changes involved in revision (2.0.x -> 2.0.y) upgrades, or if there are they can be provided as a .sql script.

As far as I can see you have to download the whole package and reinstall from scratch - is this really correct? Would it not be possible just to make an upgrade package of all the changed and added files and copy those across the top of an existing installation. If necessary making database changes by importing a script into phpMyAdmin or whatever.

Maybe this is how it is done but I can't find any upgrade package files or instructions - can someone point me at an upgrading guide for minor increments. I have read the 'Upgrade Joomla Sites to 2.0' section in the docs but it seems OTT for a minor step. There is a section called 'Upgrading to a new CiviCRM Revision on Drupal' which implies you can simply overwrite the whole civicrm filespace but again it seems OTT to have to upload and unzip 7Mb plus, and what about the files that don't live in the administrator/components/com_civicrm/civicrm folder (the front end component files).

Immediate question - if I simply copy across all of the files with a later date than the previous version should that work?

RogerCO

hey roger:

yes, it is a bit OTT to upgrade on Joomla. However note the installs are done via the component installer and hence the file permissions / ownerships are on the web server, which makes it a bit difficult for folks to overwrite files.

In drupal all files are under one directory (civicrm) and hence overwriting works quite nicely without any changes. Our svn structure matches how drupal expects things to be laid out (it does not impose any constrains on directory layout)

joomla has files stored across different directory trees and does not match how we store things in svn. so a simple overwrite wont work

we change a fair number of files and just exposing a patch set seems more work to us, so it highly unlikely we'll start doing this. bandwidth is relatively cheap these days

lobo

I downlaoded the 2.1 Alpha 3 and deleted the Alpha 2 installation on drupal 6.4
Somehow civicrm changed the ownership and I can not delete civicrm.settings.php

It did the same on the first upgrade, but since I was doing a 6.4 upgrade on Drupal I simple deleted both databases and both installs and started fresh with Drupal 6.4 and civicrm 2.1 Alpha 2. The upgrade to 2.1 Alpha 3 is a different story. I really don't want to install the entire site again.

Any suggesttion?

Is there any to chown these files at domain level or to creat this in the setup files?

Jim