Here are some interesting Joomla blog posts I found during week 28, 2013:
- 3.1.2, 3.1.3, 3.1.4 What is going on?
- Update on 2.5.12 and 3.1.2 Releases
Written by Elin Waring
The numbering of the CMS version 3 releases that are coming in the next day or so is going to be a bit surprising. Maybe not as strange as going from 1.7 to 2.5, but let’s take a closer look so everyone understands what is going on. As previously posted, the plan was for a release of 3.1.2 early this week. However some people automatically updated prior to the release due to receiving premature notification of the release while final testing of the release packages by the Joomla! Bug Squad was beginning. When they updated they found that, in fact, there was a problem with the packages. That problem caused their updates to fail, breaking their sites.
After several intense days of investigation, it was determined that the failure was due to changes to a key file (restore.php) in the update component itself. This caused the updates to fail before completing. Once the cause of the problem was identified, a solution was sought. Although it seems as though a limited number of sites were impacted by this change, it is important to provide them with a way to update successfully using the automatic updater, which the corrupted file would prevent.
Written by Michael Babker
On Sunday evening, the PLT began its pre-release procedure in preparation of the upcoming 2.5.12 and 3.1.2 releases, originally scheduled for release today. During this procedure, pre-release packages are posted to Joomlacode and made available to the Joomla Bug Squad for final testing. Typically, these packages are not visible to everyone. However, since there are no security issues included in this release, these pre-release packages were not hidden.
This caused third party update services such as Akeeba Admin Tools to erroneously report that these releases were available and as such several hundred sites were updated before the packages were hidden on Monday morning. In the time since then, additional bug fixes needed to be merged to the code base, causing a need for the release packages to be rebuilt. Unfortunately, there have been technical issues during this process, causing unexpected delays in testing and release of these packages.