We proud to announce that new build in currently stable branch is available for download - activeCollab 2.3.2. This is a bug fix release with many fixes that improves stability, usability and security of the product. Upgrade is recommended for all users.
activeCollab 2.3.2 is available for download from your activeCollab.com profile:
Please check release notes article for full list of changes.
Yes, you should do that if your FTP client works in replace mode (or you don't know in which mode it works) when uploading files and folders that already exist on the system.
Is there a recommended procedure for migrating modules? Uninstall then upgrade then reinstall? Or will installed modules persist, as long as all the required files stay in place?
If you have modules that are compatible with activeCollab 2, than you should simply leave them as is and make sure that you don't overwrite them when you upload new content. System will start to use them automatically, once the system is upgraded.
I don't know if this is specific to our company or 2.3.2 but after copying the files over /public/upgrade/ was silently failing. It would hang up on creating a backup. The error logs revealed that it was not able to allocate enough memory. I had to edit our php.ini and bump the limit from 128M to 256M. I've not had to do this before yet we have been getting backups done just fine. When I did /public/upgrade/ again it went through just fine. I checked the backup file it created in /work/backup/ and it was just over 100MB which was much larger than the daily backups. Maybe this is a full backup instead of an incremental?
activeCollab 2.3.2 is available for download from your activeCollab.com profile:
Please check release notes article for full list of changes.
Installation and upgrade instructions are also available.