Tickets CAD v3.44.0 — Major Update Available for Testing on GitHub

13 views
Skip to first unread message

Eric Osterberg

unread,
Mar 14, 2026, 10:30:01 PM (4 days ago) Mar 14
to open-so...@googlegroups.com, openises...@lists.sourceforge.net, open-sourc...@googlegroups.com

Hi everyone,

We have a significant update to Tickets CAD available on GitHub and we're looking for testers. This is a great opportunity to support the project — we're all volunteers, and testing is one of the most valuable ways to contribute to this community. You don't need to be a developer to help. If you can install the software and click around, you're exactly who we need.

What's in this update:

  • Security hardening — SQL injection vulnerabilities have been fixed across 500+ files using prepared statements. This is the single largest change in this release and addresses a critical weakness in the codebase.
  • PHP 8.x compatibility — Numerous fixes for deprecation warnings, NULL handling, and function changes so Tickets CAD runs cleanly on PHP 8.2+.
  • Tile caching proxy — New tile source options on the Set Default Map page. You can now choose between Online Direct, Proxy Cache, or Offline Local tile modes. Proxy Cache is recommended for most installations as it reduces load on tile servers and improves performance.
  • Personnel/Member improvements — Click-to-set-location on member add/edit maps, photo upload fixes, and better form validation.
  • CSV report downloads — Reports can now be exported to CSV format.
  • Various bug fixes — Map position saving, search crashes, NULL value handling, mobile map popup errors, and more.

How to get the update:

The latest version is available on GitHub at:
https://github.com/openises/tickets

SourceForge will not be updated immediately. GitHub is the place to get the latest version.

Option 1: Download as a ZIP file (easiest)

If you're not comfortable with git commands, you can download the entire project as a ZIP file:

  1. Go to https://github.com/openises/tickets
  2. Click the green "Code" button near the top right
  3. Click "Download ZIP"
  4. Extract the ZIP and replace your existing tickets folder with the contents

Option 2: Using Git (recommended for ongoing updates, easiest to apply updates to)

If you have git installed (or want to try it), these commands will get you set up. Open a command prompt or terminal and run:

cd /path/to/your/webserver/htdocs
git clone https://github.com/openises/tickets.git

This creates a tickets folder with the latest code. If you've already cloned the repository previously, you can pull the latest changes instead:

cd /path/to/your/tickets
git pull origin main

That's it — two commands to stay current.

Back up first!

Before updating, please make a backup so you can easily revert if needed:

  1. Copy your existing tickets folder to a safe location — for example, rename it to tickets_backup_20260314 or copy it somewhere outside your web server directory.
  2. Back up your database using phpMyAdmin (Export) or from the command line:
    mysqldump -u your_username -p your_database_name > tickets_backup_20260314.sql
    
  3. Your incs/mysql.inc.php file contains your database connection settings. This file is not included in the repository, so it won't be overwritten — but it's good practice to back it up anyway.

To revert to the previous version:

If you run into problems, simply:

  1. Delete or rename the updated tickets folder
  2. Restore your backed-up tickets folder to its original location
  3. If needed, restore your database backup:
    mysql -u your_username -p your_database_name < tickets_backup_20260314.sql
    

How to report issues:

If you find a bug or something doesn't work right, please reply to this message with:

  • What you were doing when the problem occurred
  • The error message (if any) displayed on screen
  • Your PHP version and operating system (if known)

If things are working well, we'd love to hear that too — a quick "tested on PHP 8.x, looks good" is genuinely helpful.

Thank you for your time and for being part of this community.


Eric Osterberg


Reply all
Reply to author
Forward
0 new messages