ARN Smart Support
Language: English

Update Ticketix

Updated 19 Nov 2026 11 min read
Browse Ticketix articles

From version 2.0.2, Ticketix gets its updates from ARN with its licence. The Updates screen shows the installed version under Current Version and an available update. You can still update by hand with the official update package (the update ZIP), for example when the server cannot reach ARN.

Where to find it: Setup → System → Updates (administrators only). The version at the top of every administration page also opens it.

Update from the Updates screen

Ticketix asks ARN for updates every 12 hours: from the scheduled task, or when an administrator opens the administration area. You can also click Check for updates on the Updates screen.

  • When an update is available, the top bar shows Update and the new version. Updates shows the Latest version, the Package size, the Release notes and the Update type: Mandatory (installs itself) or Optional (waits for an administrator).
  • A mandatory update installs itself. Any other update waits until an administrator clicks Install version … and confirms.
  • Only administrators can install an update.

What happens during the update:

  1. Ticketix downloads the package from ARN over HTTPS and checks the signature of ARN, the checksum and the size. It checks the whole package before it changes anything. From Ticketix 2.3.0, a version that carries the publisher signature of ARN Smart is installed only when that signature matches the package; otherwise the update is refused with "The publisher signature of Ticketix … does not match the package".
  2. It backs up the database and the files that will change into storage/updates.
  3. It writes the new files. For about a minute, other pages show a short maintenance message.
  4. The next page runs the database upgrade of the new version.
  5. If the upgrade fails, Ticketix puts the previous files and database back, and Updates shows the reason. If it succeeds, Updates shows a line such as "Updated from 2.1.3 to 2.1.4 on …". The database backup is deleted; the files of the previous version stay in storage/updates until the next update, and Updates shows them under Previous version files.

config.php, config.local.php, the storage folder, .htaccess and setup.php are never changed. An update does not delete files that a new version no longer uses.

Important: Ticketix keeps no database backup after a successful update. Keep your own regular backups of the database, config.php and the storage folder, including storage/ai-secret.key.

For updates from ARN, the server needs the PHP ZIP and cURL extensions, HTTPS access to licence.arnsmart.com, and write access of PHP to the application folder and to storage. Updates warns when an extension is missing or PHP cannot write a folder; update by hand until it is fixed. It also warns when the scheduled task has not run for a day: without it, Ticketix checks for updates, and installs a mandatory update, only when an administrator opens the administration area. See Set up the scheduled task (cron).

Coming from 2.0.2, 2.1.0 or 2.1.1

The Updates screen of versions 2.0.2, 2.1.0 and 2.1.1 refuses packages that contain the api folder of the ticket API, with the message "The update package contains a file that is not allowed: api/ticket-create.php", before it writes anything. Update such an installation once by hand with the update ZIP of the current version (see below). From 2.1.2 on, later versions install from the Updates screen again.

Update by hand

Use the update ZIP when the server cannot reach ARN, and once for the update from 2.0.2, 2.1.0 or 2.1.1.

Before you start

  • Download the update ZIP of the new version from your ARN account and read its README.md.
  • Use the update ZIP, not the installation ZIP. The update ZIP contains no config.php, no storage folder and no customer data.
  • Check that the server still meets the requirements: PHP 8.3 or newer with the PDO, mbstring, OpenSSL, cURL, ZIP, fileinfo and Sodium extensions.
  • Be ready to request an ARNA activation code for this product and domain in case a new licence activation is needed.
  • Tell your team. Updating to Ticketix 2.0.1 or later from an earlier version asks every administrator and agent to set up two-factor authentication at their next sign-in.

Back up first

Make a full backup and store it outside the server:

  • the application files;
  • the database (for SQLite, the database file in the storage folder);
  • config.php (and config.local.php, if it exists);
  • the whole storage folder.

Important: Keep storage/ai-secret.key with your storage backups. It encrypts the stored AI provider keys and the authenticator secrets of two-factor authentication. Without it, the AI keys must be entered again, and authenticator and backup codes no longer work.

Apply the update

  1. Stop the scheduled task and, if you can, write traffic to the site (for example with a maintenance page on the web server).
  2. Extract the update ZIP over the existing application folder. The ZIP does not delete any file. From Ticketix 2.0.2, it does not contain setup.php; the database upgrade does not need it.
  3. Do not delete or change config.php, config.local.php, the storage folder, .env or server-specific access rules.
  4. The update ZIP does not change .htaccess. On Apache, make sure your existing rules still deny access to the configuration files and to the core, scripts, lang and storage folders. On Nginx, keep the equivalent rules and allow PHP in the api folder.
  5. Open the administration area. The first request runs the one-time database upgrade under a lock. Other requests wait for it.
  6. Complete the licence activation on the License screen if Ticketix asks for it.
  7. Check the administrator sign-in, existing tickets, settings and the mail connection.
  8. Turn the scheduled task and traffic back on.

Updating from a version before 2.0.0

Add the public address of the installation, including any subfolder, to config.php, without a trailing slash:

'app_url' => 'https://support.example.com/ticketix',

Without it, mails that the scheduled task sends (for example queued replies or the confirmation of a ticket created from incoming mail) contain only a path that cannot be opened from a mail client. New installations get app_url from setup.

If the update fails

Restore the old application files, the configuration files, the storage folder and the database backup together. Restoring only the old code is not enough.

Move from SQLite to MySQL

From Ticketix 2.3.1, new installations use MySQL. An installation that runs on SQLite keeps working after the update, and every administration page shows "This site still runs on SQLite" with Move to MySQL until its data is in MySQL.

  1. Create an empty MySQL database (utf8mb4) and a user with full rights on it. Ticketix refuses a database that already contains Ticketix tables; it never overwrites one.
  2. As an administrator, click Move to MySQL. On the Database screen, enter the host, port, database name, user and password, and click Move to MySQL. A large installation may need some minutes; the result stays on the screen after a reload.
  3. While the data is copied, the site can be read, but changes such as new tickets, replies and settings are refused with a request to try again in a minute, and the scheduled task skips its run.
  4. Before anything is copied, every value is checked against its MySQL column. A text longer than its column, a number the column cannot hold, or two values that MySQL takes for the same (it does not tell upper and lower case apart) stop the move, and the screen lists the table, column and row to correct. Nothing is shortened. Invalid UTF-8 characters are replaced and listed.
  5. Every table is copied with its ids and compared. Only when every table matches does Ticketix write the new database details to config.php and use MySQL; the previous file is kept as storage/backups/config-before-mysql-….php. If anything fails or does not match, the site keeps running on SQLite.
  6. The SQLite file (storage/support.db unless config.php names another file) is never changed or deleted; keep it as a backup. Then check the administrator sign-in, a few tickets with their attachments and the Knowledge Base.

To go back to SQLite, put the previous config.php back and delete storage/database-move.json. Changes made after the move exist only in MySQL.

After the update

  • Open Updates and check Current Version.
  • Every administrator and agent sets up two-factor authentication at the next sign-in if they have not done so. See Two-factor authentication and password reset.
  • If you use AI, open the AI settings, test each connection and check the model of each task. See Connect AI and set AI limits.
  • After updating to 2.0.2 or later from an earlier version: each logo is stored in its own file. If the portal or administration logo shows another logo, upload it again under Setup → Portal → General.

After updating from 2.0.2 to 2.1 or later

  • The administration menu moves into the groups Work, Content, Insights and Setup. Export and Updates are under Setup → System, and your profile is in the user menu at the top right. Menu links you added yourself stay.
  • New community topics and replies of guests wait for approval under Content → Community, Moderation queue, instead of appearing at once. Choose Sign-in required under Setup → Portal → General if guests should only read. Posts written before the update stay as they are.
  • A "Guest ticket verification" template that you edited earlier keeps its {{verify_link}}. Add {{ticket_link}} to use the new link that opens the ticket directly. See Email templates and the ticket-closed email.
  • Files of earlier versions that 2.1 no longer uses stay on the server; they are harmless. The README.md of the update ZIP lists them if you want to delete them.
  • Tickets opened from email before 2.1.4 keep the channel Portal and their saved text; customers created from email before 2.1.3 keep the name they were saved with. Change a name on the customer page.

After updating to 2.2.0

  • AI reply drafts use the Knowledge Base articles of the ticket's product when its top-level category has the product key as its address. Check the addresses of your product categories under Content → Knowledge Base, tab Categories; the keys are listed under Setup → Support → Products. See Use the AI assistant and triage on tickets.

After updating to 2.2.1 or 2.3.0

  • Nothing to change: 2.2.1 and 2.3.0 change no data and no settings. 2.3.0 adds the publisher signature check described above.
  • From 2.2.1, the full staff search opens from All results in the search window and, for administrators, from Setup → Portal → Search; the ticket list has an Export button; the channel of a ticket shows in the language of the interface. See Portal search and staff search and Create, organize and close tickets.

After updating to 2.3.1

  • Versions 2.1.2 to 2.3.0 install 2.3.1 from the Updates screen.
  • An installation on SQLite moves its data to MySQL as described in "Move from SQLite to MySQL" above.
  • The database upgrade gives every article, community topic and search entry a language, and builds the search index again once, so Arabic, Cyrillic and other non-Latin texts are found. From then on the scheduled task writes new and changed articles, topics and replies into the search index; keep it running.
  • Existing articles and topics get the site's Default language. If your articles are in English but the default language is Turkish or Arabic, select them in the article list and use Change language.
  • The portal can also be shown in Japanese and German. Since 2.3.2 the update turns them on for most sites; see "After updating to 2.3.2" below.
  • Only an administrator deletes a customer message or a sent reply; an agent deletes only their own internal notes. See Reply, add notes and work together on a ticket.
  • A reply email is added to a ticket only when it comes from the ticket owner or a contact of the same customer, or keeps the ticket's [ARN:…] reference in its subject. A colleague who answers from another address without it opens a new ticket. See Email to ticket, mailboxes and the Mail Center.

After updating to 2.3.2

  • Versions 2.1.2 to 2.3.1 install 2.3.2 from the Updates screen. Nothing to change in the configuration.
  • The language links at the top of the portal become one language menu (🌐 and the current language). See Languages and translated content.
  • If the saved Portal languages of the site had English, Turkish and Arabic, the update adds 日本語 and Deutsch once. If one of these three was hidden, the list stays as it is and Setup → Portal → General shows "New visitor languages are available" until the page is saved; turn the languages on there if you want them. A language you remove later stays removed.
On this page

Submit a ticket

Create a new support request without needing a portal account.

Priority
Attachments
Only you and our staff see a ticket. Never send passwords or licence codes.

Track a ticket

Use the ticket number and password from your confirmation email.

The number and the password are in your confirmation email.

Sign in

Access your support portal account.

New here?

Create account

Create your support portal account.

Already have an account?

Forgot password?

We email you a link to choose a new password.

Conversation

Was this helpful?
Open full article
↑ ↓ to moveEnter to openEsc to close