Workarounds for issues introduced by Joomla 4.1.1/4.1.2. A few things changed under the hood in Joomla 4.1.1, including the way the anti-CSRF token checks are performed. Unfortunately, this major change was introduced without prior warning or proper communication from the Joomla! Project in Joomla! 4.1.1. This caused several issues with frontend and backend features using GET requests throwing an invalid token error.
Bug fixes and minor improvements. Please take a look at the CHANGELOG below.
Due to the complete rewrite of Akeeba Ticket System you cannot just install the new version on top of an old major version (2 or 3) and have everything work trouble-free especially if you were using any of the following features:
Our documentation has migration instructions. We strongly recommend working on your migration on a dev site first and test thoroughly to ensure you are not missing anything important when you upgrade to Akeeba Ticket System 5.
If you are using an older version of Akeeba Ticket System please upgrade to each major version up to and including the latest Akeeba Ticket System 4 version before migrating your site to Joomla 4. After your site's migration to Joomla 4 upgrade to Akeeba Ticket System 5.
If you are already using Joomla 4.1 or later please keep in mind that you cannot install Akeeba Ticket System 4 afresh or updates to it. Instead, install Akeeba Ticket System 5 and follow the migration instructions in our documentation. You should do this as soon as possible. We will no longer provide a migration path from older versions of Akeeba Ticket System after August 17th, 2023 when we the long term support for ATS 4 comes to an end.
Please consult our Compatibility page. It explains our version support policy and lists which versions of our software are compatible with which versions of Joomla and PHP.