Dear Froxlor Community,

we are proud to announce the release of our next major release candidate 0.9.31-rc1.
 
With this release the old PHP-MySQL extension was replaced with PDO-MySQL. Due to this move all queries have been touched and converted to prepared statements, preventing SQL-injections in the future. This also means, that there may be SQL errors we didn't catch.
 
In addition to that we have implemented an (optional) error-reporting which will email us any occuring SQL errors. You will see a preview of what exactly is being sent before anything leaves your system - no E.T.-phone-home! Also, this is currently only enabled for admins - but you can optionally allow your customers to send reports too (please watch out for any personal/private data!). In the final release of course, the error-reporting will be off by default for both, admins and customers.

This will be the first of at least two planned release-candidates due to the heavy changes all-over the code so please test and report any issues.

Changes in 0.9.31-rc1:

+ Completely redesigned dashboard in Sparkle-theme

+ #729: Usage of an activation code instead of password reset

+ #1051: Enable usage of php-slowlog for FPM users

+ #1287: Switch database implementation to PDO

+ #1297: Standard subdomains do not appear in a customers domain list


~ #1277: Traffic data - different values

~ #1300: Make FastCgiIpcDir configurable (important for php-fpm)

~ #1309: Nginx cron doesn't merge locations correctly

You can see all changes in our bugtracker at http://redmine.froxlor.org/versions/45

Download: 0.9.31-rc1

Note: As this is a release candidate, there will be no Debian packages. Gentoo users might use the testing ebuild (froxlor-9999).

Visit http://www.froxlor.org or join our IRC channel #froxlor on irc.freenode.net.
 
Thank you,
d00p

Hey d00p, why it's APS, Backup and Autoresponder deprecated?

Because we decided it that way. More information about that will be available in the announcement of 0.9.31 final. So until 0.9.32 these features are still present.

Is there a possibility to activate it again? Let's say via Plugin or API (Later at Version 1.00).

No decision about this yet. Please wait for more information later.