Upgrade with Minimal Downtime

lucapost Pro

Jul 8. 2011. 5:35 am

I understand such things are outside the control of the activeCollab team; but given such modules are listed on the official site they get purchased... that's when one realizes that they spread modifications all around the core directories!

Aside from these worries about managing updates, my activeCollab installation is still running very stable 'despite' 6 3rd-party extra modules installed (ShadowViewer, Tabsorter, Tabinator, Confidential, Reports, BruteForceLoginManager) !

ciao

Nirav M. Dev

Jul 14. 2011. 2:14 am

#12

I guess another option is to upgrade activeCollab only after the modules you are using are made compatible with the latest release. ;-)

In our case, we do have modules that modify core files. We consciously avoid doing this, but where we think it will be best for performance and feature implementation, we do modify core files.

And frankly, a new activeCollab release may require updating a third party module, even if it does not modify core files. Some internal code in activeCollab may change and that may require updating a module.

We update our modules every time there is a new version of activeCollab. And that too as quickly as we can. I am not aware of release cycles of other developers, but I am sure they work hard on making their modules compatible with newer releases as well.

Customers purchase third party modules because they add value to their activeCollab experience. I think it would be ok to wait for a reasonable time so that third party developers update their modules for latest version compatibility.

Again, with the introduction of activeCollab developer program, this wait time may reduce even further since developers will get early access to new activeCollab versions.

HTH.

:Nirav

Discover a new high in team productivity with our Best Selling & Most Loved activeCollab Extensions

lucapost Pro

Jul 14. 2011. 4:58 am

#13

Thanks Nirav that is definetely the safest way!

I believe a wordPress-like 'disable All' modules before performing updates would be useful to avoid disservices to users in the interval of time between uploading the updated core files and uploading the modules files.

btw is it safe to put the site in maintenance mode while upgrading?!

Nirav M. Dev

Jul 14. 2011. 5:26 am

#14

I think "disable modules" must be on aC's list as well, and we hope to see that in aC 3.0.

As for maintenance mode: Yes, I recommend you put aC in maintenance mode every time you do an upgrade. That will stop users from getting in and making changes.

:Nirav

Discover a new high in team productivity with our Best Selling & Most Loved activeCollab Extensions

Oliver Maksimović Staff

Jul 16. 2011. 7:17 am

#15

"Disable Modules" sounds okay but, in case that someone may want to do it manually for 3rd-party modules (at least right now with aC 2.x) by uninstalling third-party modules prior to doing an upgrade, don't forget that uninstalling a module can actually lead to losing all data that has been entered using it (depending on developer(s) and what they've put into uninstall method of their module).

activeCollab dev / tech support

activeCollab

Demo

Tools

Community

Getting Started

Documentation

My activeCollab

Try activeCollab free for 30 days, No credit card required!