Recent Posts

Welcome.

Seems like you'd just need to comment out one line calling the routine.

There's a subroutine called "transfernotice" in the TTXTicket.pm module.  Comment out the line that calls it.  Do a text search... there's only one line around 1487.

Not sure if anything else calls it but you can search the other modules for that.

G'day all,

This is my first post, so please be gentle with me...

I would like to stop receiving the ticket Transfer emails, but continue to receive all the other emails.
Can anyone help with a mod that might fix this for me. I have implemented other mods sucessfully so I dont think I will have trouble doing this.

We are using TTX v3.0

Thanks...
Darren Crick

Sorry I was vague...

We have other systems (where I work) that force requests to pass through an approval track (meaning a number of people must approve the request in sequence) before it becomes a formal work item and then passes on to operators for completion.

This is probably beyond the scope and design of ttx.  I was just wondering if anyone had considered or developed something like this within ttx.

Fixed!  For some reason, it seems, you have to configure SMTP through IIS 6 Manager, even though IIS 7 is installed . . . . . 

I've just moved TTX to a Windows 2008 IIS 7 Server.  After a lot of problems, I finally got it working except for two things:

Having problems with the SMTP settings getting it to send through Google Apps
Its VERY slow.  Like when I fill in a new ticket, it takes between 5 and 10 minutes before the confimation page comes up.
Similarly, logged in as an operator, it takes the same length of time when assigning a ticket to another operator.

Any ideas gratefully recieved 

We would like to be able to force submitted tickets to move through an approval track before final processing by operator.  Anyone doing that or looked into it?

What does "move through an approval track" mean?

We would like to be able to force submitted tickets to move through an approval track before final processing by operator.  Anyone doing that or looked into it?

From http://troubleticketexpress.com/

Access code (a.k.a. captcha) to prevent ticket submissions by spambots

I had the same issue ...the captcha resolved them .....

The spam is coming from form submissions. 

Several years ago I copied the ticket submission html code and imbeded the code in our primary web server.  Our Primary Web server was from a hosting company and our site is CMS based so adding ttx to that site was not an option.  This has served us well, and now allowed me to stop a spammer who has been submitting tickets.

All the new spam tickets had a file attached.  I never upgraded my primary server page to enable file submission so I know the tickets were being created from my TTX site.  To stop the spam I modified the newticket.html file in the data/template folder by removing all the code and entering the text "Not Available".  As I never refer anyone to create a ticket from my TTX site this change will have no effect on ticket submissions.  New tickets can continue to be submitted via the custom HTML code on my primary web site. 

Granted this fix will only hold until someone finds the new ticket submission form on our primary server, but it is holding for now.

Actually, we use the group feature to group each individual 'customer' into  Companies.  Because our Customer is the company.  So sorting by group would be even better.

You can do that.  Just modify the query string in the URL code to use the group instead of the email.  I think the new variable would look like $t->{group}