07 December 2011 Last updated on 16 January 2012

Akeeba Subscriptions 2.0.RC1 just released.

We are pleased to announce the immediate availability of Akeeba Subscriptions 2.0.RC1, a maintenance release.

Akeeba Release System 2.0.RC1 is the near-stable release candidate release of Akeeba Subscription, our easy to use subscription management system. It introduces the final batch of features for the 2.0.x series and brings the component just one step before being declared stable. Moreover, this release adds full compatibility with Joomla! 2.5, the upcoming long-term support release of the Joomla! CMS. 

Release Candidate releases are believed to be of production quality and have undergone extensive testing before release. However, we strongly recommend using and testing them on a development site before deploying them on your live site.

Getting Akeeba Subscriptions and receiving support

As always, Akeeba Subscriptions is available free of charge from our Downloads page. If you have an older version installed, you can simply use the integrated Live Update feature to upgrade to the new version painlessly.

While the software is free, its support is not. If you wish to receive support for the software, you will need to buy a FORUMACCESS subscription at 7.79 Euros for an 8-day pass to our dedicated forum section. Alternatively, if you are a subscriber to AKEEBADELUXE or SUPPORT you can request support either through the dedicated support forum section or by submitting a private support ticket.

Supported versions

Our support policy is to provide support only to the latest published stable release of Akeeba Subscriptions, as well as to the latest published preview (alpha, beta or release candidate) release, if one is available. As an exception to this policy, Akeeba Subscriptions 1.0.x is no longer supported, despite being labelled "stable", due to the use of an unstable third-party framework which compromises its stability. Therefore, we had to drop support for version 1.0.x in order to create a rewritten, very high quality component using our own, very stable framework which is build on top of the tested, rock solid Joomla! Framework.

Moreover, we only support the Joomla! versions officially supported by the Joomla! project. Due to the plethora of active Joomla! versions, we have consolidated the support terms for different Akeeba Subscriptions and Joomla! version combinations in the table below:

 

J! 1.5

J! 1.6

J! 1.7

J! 2.5

AS 2.0.RC1 *

Until April 1st, 2012

Not supported

Until February 15th, 2012

Until August 2013 **

Older releases

No longer supported

* Only the latest Akeeba Subscriptions 2.0.x release is supported.

** If a new Akeeba Subscriptions series (i.e. 2.1) is released before August 2013, Akeeba Subscriptions 2.0.x will cease being supported, per our support policy stated above.

Changelog

New features

  • #40 You can now view and edit custom user fields in the back-end user editor view
  • You can now view and edit per-user notes in the back-end user editor view
  • #43 uPay payment gateway integration
  • #42 MoIP payment gateway integration
  • Allow third party software to fetch the subscriptions list remotely (sending the Super Administrator username/password in the request)
  • A plugin to send emails to affiliates when a new subscription is created using their affiliate ID

Miscellaneous modifications

  • The button in the subscription page is not a button element instead of a submit input element
  • Full support for all subscription merge tags in the subscription and administrator email plugins

Bug fixes

  • The title of the component in Live Update showed as the generic "Foobar Component for Joomla!"
  • Missing translation in the menu view
  • Publishing one of the front-end modules on an Akeeba Subscriptions page would cause inability to submit any form (e.g. the subscription form)
  • The j16compat.js file is not needed and causes a JS error
  • JS error thrown in the control panel page if no subscriptions exist
  • The State field in the subscription page would show up in a very confusing place
  • Invalid characters were allowed in the Subscription Levels' slugs
  • The "Administrator Emails" plugin was broken (thanks Paven!)