Each of our extensions has a Version History page where you can see exactly what has changed in each version. Our Components have an About page, where you will find the version number of the version you are running, and a link to the relevant Version History page.

We don't support the idea of blindly installing updates just because a new version is available. If a new version has a fix or a new feature that you need, then install it. If not, there is no point.

In an ideal world, you should test all new versions of software on a test site before installing them on your live site. In practice, of course, many people don't do this, so we have adopted a simple policy: For minor version changes (like 5.09 to 5.10) it's likely that you can update without encountering any issues or significant changes to the front end of your site. For major version changes (like 5.10 to 6.00) you are strongly advised to study the product documentation for the new version, and consider installing it on a test site first.

Our versions follow the following convention:


XX is the major version number. This is incremented when the extension is substantially rewritten, or major new functionality is added, or upgrading to it requires some additional work on your part. When you upgrade an extension to a different major version, we recommend that you install it on a test site and check that the new version meets your requirements, before you install it on your live site. If you have customised the product css, you may have to re-implement your changes on the new version as the css class names and html structure might have changed.

YY is the minor version number. This is incremented for bug fixes, new functionality, and new language translations. You should be able to implement these straight onto your live site, although you should be able to reverse the upgrade if necessary.

ZZ is the sub version. This is incremented for minor cosmetic fixes, language file updates, or bug fixes to functions of little significance. These changes are not shown in our published version histories and you don't need to upgrade to them unless we specifically advise you to.