Easy migration

[counterpoint]

The initial 1.9 version of aTicket will provide for easy migration from the eTicket or osTicketsupport help desk ticket systems. Modifications to the code have avoided the problem of settings being overwritten by a new version. Default settings are now kept in different files, and transferred as part of the installation process.

Version 1.9 of aTicket may be unsuitable for migration of a busy, live eTicket installation as it will effectively be beta code. But every effort will be made to quickly resolve any bugs that are found. It is quite likely that there will be a series of minor releases to handle this cleanly.

It will help the aTicket project greatly if people who do have busy eTicket systems can run a trial of aTicket as the feedback of live problem will enhance the development process for everyone.

Any conversion problems, experiences or tips for moving from eTicket to aTicket are welcome in this forum.

[JasonRobinson]

I have been locked down on my current server by a php restriction which forbids my eTicket installs from interfacing with the email system due to restrictions on the "escapeshellcmd" or "escapecmdshell" (one of the two) function.

This specifically relates to email piping to create new tickets from incoming messages. How does aTicket implement mail pipes?