The phpMyFAQ Team wishes everyone a happy new year 2010! Since today, the only supported versions are phpMyFAQ 2.5 and the upcoming phpMyFAQ 2.6 release. We don’t support any PHP 4 based of phpMyFAQ anymore.
I’m ill at home for one week now and I even cannot develop anything. Until now I didn’t get any feedback from the RC release but I’ll prepare a second RC for the next week. So 2.6.0 will be a 2010 release like the 2.5.6 release which will be the last 2.5 release. Please don’t forget that the support for phpMyFAQ 2.0 ends in 17 days…
The phpMyFAQ Team would like to announce the availability of phpMyFAQ 2.5.2, the “Engelbert Humperdinck” release. This release fixes a IE6/7 only XSS vulnerability. All users of affected phpMyFAQ versions are encouraged to upgrade as soon as possible to this latest versions! A detailed security advisory is available. We also updated the Polish and Chinese language file, and fixed a problem with Czech translation.
The phpMyFAQ Team is pleased to announce phpMyFAQ 2.0.17, the “Cable Car San Francisco” release. This release fixes a IE6/7 only XSS vulnerability. All users of affected phpMyFAQ versions are encouraged to upgrade as soon as possible to this latest versions! A detailed security advisory is available.
The phpMyFAQ Team would like to announce the availability of phpMyFAQ 2.5.1, the “Otto Lilienthal” release. We added support for LDAP-datamapping, e.g. against an Active Directory Server, support for multi-domain-authentication, e.g. against an ADS-Global Catalog, support for PHP LDAP options, and a Lithuanian translation. We fixed LDAP and some Oracle issues, and improved our svn2package script. Beside that many minor bugfixes were made.
We would like to announce the availability of phpMyFAQ 2.0.16, the “Isaac Hayes” release. We updated the French translation and fixed a lot of minor bugs. This is the final release for the 2.0.x series. Only critical security issues will be fixed.
Today I received a great patch from Lars Scheithauer with some LDAP fixes and some great additions for our LDAP support. With Lars’ patch it’s now possible to authenticate against an Active Directory from Microsoft, using multiple domains in your Actice Directory, and he also added support for the PHP LDAP options. Thank you very much, Lars!
I added all these enhancements to phpMyFAQ 2.5.1 and 2.6.0-alpha. We also fixed some issues in all three supported branches. I think you can expect a release of 2.0.16 and 2.5.1 next week.
Wow, we got some quite good feedback from our users after the 2.5 release yesterday. We also got some bug reports and we’re already fixed some minor issues. So expect a version 2.5.1 in August. In July we’ll release a maintainance release for phpMyFAQ 2.0. And we’re starting to merge the code of our UTF-8 branch back into the trunk for phpMyFAQ 2.6.
Today we merged another two new features into phpMyFAQ 2.5: The folder for the attachments is now configurable so that you can upload the attachments outside of the webroot. We also added the permission to approve new FAQ entries and we fixed some bugs. phpMyFAQ 2.0.16 has one open bug before we can release the probably last 2.0.x release…
If everything works fine PHP 5.3 will be released at the end of this month. PHP 5.3 will be a big step further after the 5.2 release more than two years ago. The phpMyFAQ team did some testing with the last release candidates of PHP 5.3 and already fixed some issues we found. phpMyFAQ 2.0.15 and the upcoming phpMyFAQ 2.5.0-RC will run without any problems on PHP 5.3.
The phpMyFAQ Team is pleased to announce phpMyFAQ 2.0.15, the “Benno Ohnesorg” release. This release fixes a XSS vulnerability. All users of affected phpMyFAQ versions are encouraged to upgrade as soon as possible to this latest versions! A detailed security advisory is available. phpMyFAQ 2.5 and 2.6 are not vulnerable!
The phpMyFAQ Team would like to announce the availability of phpMyFAQ 2.0.14, the “Andrei Sakharov” release. This release updates the Vietnames translation, improves the tagging implementation, and fixes a authentication bypass. The content type for the RSS feeds are now correct. It also fixes minor issues.