Akeeba DocImport requires the following server-side configuration:
Joomla!™ and PHP version compatibilities are detailed in our Version Compatibility matrix.
MySQL 5.5 or later. Earlier database server versions will not be supported. Do note that earlier releases of MySQL are obsolete and not supported any more by Oracle (the company who controls the development of MySQL).
As far as the browser is concerned, you can use any modern version (i.e. published within the last year) of Microsoft Edge, Safari, Opera, Firefox or Google Chrome. We no longer support Internet Explorer; our software will display incorrectly or not work at all on this old, buggy, and obsolete browser.
In any case, you must make sure that JavaScript is enabled on your browser for the administration interface to work. If you are using AVG Antivirus, please disable its Link Checker feature (and reboot your computer) as it is known to cause problems with several JavaScript-based web applications, including Akeeba Ticket System.
You are very strongly advised to disable or properly configure Internet firewalls, antivirus applications and browser extensions which interfere with the site's loading such as script blockers (such as NoScript) and ad blockers (such as AdBlockPlus) only for your site's domain to ensure that the administration interface (both in the backend and the frontend of the site, the latter if you are logged in as a ticket system staff member) is displayed correctly. Remember that these applications and browser extensions are designed to protect you against third party sites. As a result they are very aggressive and WILL break your own sites. We can't do anything about it: your computer and your browser are under your control alone.
Kindly note that our software is compatible with Joomla's caching. If you are using an external caching solution (such as LiteSpeed Cache, Varnish etc) or a CDN / third party service (such as CloudFlare) kindly note that we are not responsible if your site displays out of date information or otherwise misbehaves. Our responsibility ends at sending the correct HTTP headers to indicate that a page must not be cached and clearing Joomla's cache when information which can participate in a cached page is modified. What happens beyond that is objectively outside the scope of our software and into the configuration scope of the external caching / CDN / third party service you are using.
Every version of Akeeba Ticket System is only tested against, and only supports, a specific range of PHP and Joomla versions, as published on its download page. These version limits are actively enforced by the software itself, not just documented. This is part of our compliance with the European Union Cyber Resilience Act (EU CRA): we can only vouch for the security of our software, and honour our security risk assessment, within the specific PHP and Joomla versions it was designed for.
Depending on how you are using Akeeba Ticket System when the incompatibility is hit, you will see one of the following symptoms.
Using the component's backend or frontend interface. Akeeba Ticket System will refuse to run and will display a clear error message telling you whether you need to upgrade PHP, upgrade Joomla, or upgrade Akeeba Ticket System itself, and which versions are supported.
Using the CLI script or a Joomla CRON URL for automated tasks. If the site is running an incompatible version of PHP or Joomla, the plugins in the ats group, the Console — Akeeba Ticket System plugin included, will not load at all. Joomla itself has no way to tell you why a plugin did not load; instead the CLI script will report that the command you are trying to run does not exist, or the CRON URL will silently do nothing. Whenever you see either of these symptoms you should treat it as a possible PHP or Joomla version incompatibility and investigate as follows:
Log into your site's backend and go to , . If PHP or Joomla on your site is incompatible with this version of Akeeba Ticket System you will see the error message described above, telling you exactly what needs to be upgraded.
The PHP version used to run a CLI command can be different than the one your site runs under on the web server, e.g. because your host provides several PHP CLI binaries and your CRON job uses the wrong one, or an environment default was changed. To find out which PHP version is actually used when your CRON job runs, create a file called test.php inside your site's cli directory with this content:
<?php echo PHP_VERSION;
Then run it with the very same PHP binary and path you use in your CRON job, replacing joomla.php with argumentstest.php, for example:
/usr/local/bin/php /home/USER/webroot/cli/test.php
This will print the PHP version your CRON job actually runs under. If it is lower than the minimum, or equal to or higher than the maximum, PHP version supported by your version of Akeeba Ticket System you will need to adjust your CRON job to use a compatible PHP CLI binary. Remember to delete test.php once you are done; it is not part of Akeeba Ticket System and will not be removed automatically.
Using the Joomla API integration. If the site runs an incompatible version of PHP or Joomla, the Web Services — Akeeba Ticket System plugin will not load, and the API routes it registers will not be available. Client software will report a generic 404 Not Found response, indistinguishable from the plugin simply being unpublished, rather than a meaningful message about version compatibility. Whenever an API client suddenly stops working with an unclear error, treat it as a possible PHP or Joomla version incompatibility: log into the site's backend and go to , to see whether Akeeba Ticket System itself reports a PHP or Joomla version incompatibility error.
In every one of the above cases the underlying issue is the same: the site's PHP or Joomla version falls outside the range supported by the installed version of Akeeba Ticket System. The fix is always one of upgrading PHP, upgrading Joomla, or upgrading (or, rarely, downgrading) Akeeba Ticket System to a version whose supported range matches your server's PHP and Joomla versions — consult our Compatibility page to find a compatible combination.