community.aegirproject.org

The Aegir team is very pleased to announce the fourth release candidate of Aegir 1.0!

We have again found critical issues in rc3, detailed below, and a few key features that we wanted to slip into 1.0 that were just low-hanging fruits that deserved to be released. We hope this release candidate will be all shiny and without any critical issues so we can release it as 1.0.

Key changes in 1.0-rc4

• There is now a ~/clients directory in which symlink are automatically created to allow easy access to all your client sites (#1115960)
• A variable is now set in settings.php (aegir_api) to allow contrib modules to inspect what Aegir version they are dealing with, if any. The setting is removed on export, that is, if dbcloaking is off (#1027358
• We fixed a big regression where the mass migrate form stopped working in rc3 (#1111532)
• The private directory of Drupal 7 is now properly protected (#1108810)

New features

• #1115960: Moving a site between platforms causes confusion
• #1027358: Set a variable in settings.php so that modules can check whether the site is in Aegir
• #1111932: Move the suggestion of a client title into it's own function (for use when creating clients programatically)

Bug fixes

• #1111532: Mass Migrate fails in Aegir 1.0 RC3 - regression from rc2 caused by the security fix below
• #1117296: cross site request forgery issue in tasks - was fixed again due to the above regression
• #1108810: Files in sites/example.org/private are accessible.
• #1102620: provision-deploy fails silently on unavailable database
• #1111572: Undefined index: profiles deploy.provision.inc:84

Need help?

If you struggle to install or upgrade your Aegir system, you have a number of options available to you for getting help.

Consult this page for more information: http://community.aegirproject.org/help

Thanks to our awesome community for their help, support and encouragement as always! Enjoy the new release :)