CiviCRM Community Forums (archive)

As a matter of interest is there a reason why point upgrades (eg 2.2.7 to 2.2. which do not involve database schema changes require a complete uninstall and reinstall of the full package.

Wouldn't it be far simpler to have an upgrade package which just contained the changed files rather than overwriting everything?

Would mean we could have a much smaller install zip file and might be able to use the standard component installation.

Also looking in the package why do we end up with a second copy of TinyMCE when this is already included in Joomla. With a 12Mb zip file which has to be ftp'd up and then expanded to a 40Mb temp folder before the component installation makes a fresh copy of it in its final resting place you end up needing over 90Mb free disk space just to install. 'twould be neat if the install routine ended up by deleting the temporary unpackage (or at least giving you a message so that you don't forget). There seems to be quite a lot of possibly unnecessary stuff in there (is the joomla folder needed for drupal and vice versa?)

Guess who just ran out of disk space having forgotten to delete the unwanted stuff 

Ok, that makes perfect sense. Probably not worth the effort now for the 2.2.x series but it would be good to fix it for 3.0.x and beyond so I'll have a play around at some point.

The 'component' I produced to control profile access worked fine as an upgrade to an existing installation - overwrites files and creates new ones as required. It also worked on macosx (mysql running on my laptop, not server version), so maybe the problem has gone away with a recent Joomla update.

Keeping it simple across D,J and standalone is good reason, but I do find it scary every time having to uninstall and reinstall to upgrade - seems to work though.

Cheers
RogerCO