Support

Unfortunately you cannot do this any more. Before version 3.11.x we were using our own update solution, Akeeba Live Update, which among other things allowed you to select the minimum release stability for updates. The only drawback was that the available updates did not show in the Joomla! Extensions Manager's Update page and the Joomla! Control Panel. There were A LOT of very vocal users demanding us to use the integrated Joomla! extensions update for this reason. We were explaining that this is a lousy idea. Nobody would have any of that, they just wanted us to use the Joomla! extensions updater. So we did.

Problems experienced so far:

• The update cache gets stuck and doesn't let you know there's an update.
• Joomla! does not apply the update source on updates, it only does that on installation.
• Joomla! 3 and Joomla! 2.5 use different ways to provide the download ID, sometimes leading to download failure of updates.
• Joomla! 2.5.18 and earlier do not support updates for commercial software, leading to download failure of updates.
• Third party plugins can interfere with the download ID provisioning, leading to download failure of updates.
• Joomla! ships with a problematic cacert.pem file making it impossible to get data or download files from HTTPS update sources on servers which do not have a system-wide cacert.pem file. This leads to download failures of updates.
• Joomla! has no way to provide two update streams, one for stable and one for testing releases. Moreover it is unable to understand the difference between a stable and an alpha/beta/rc release even when we use the PHP versioning standard Joomla! requires its extensions to use anyway.

But since this is what our clients were demanding, very loudly, of us and all the problems have to do with Joomla! core code we can't do anything. We did send patches for most of those issues. The new Joomla! 3.4 version which includes them is still not released.

So, our compromise was to test 4.1.0.rc1 for two and a half weeks across all versions of Operating Systems, PHP and Joomla! we could get our hands on, using all combinations of features we could think of. We could have called it 4.1.0 stable, if it weren't for the fact that experience has taught us that major changes in the backup engine always lead to problems you can't catch with testing, no matter how thorough you are (they depend on the server environment, a missing documentation page or a pesky little bug triggered in some special conditions). That's why we called it 4.1.0.rc1.

You're welcome, Tim.