- Dec 23, 2013
-
-
Jared Hancock authored
-
- Dec 17, 2013
-
-
Jared Hancock authored
-
- Dec 16, 2013
-
-
Jared Hancock authored
And define getInitials() function for %{ticket.name.initials}
-
Jared Hancock authored
-
Jared Hancock authored
This box shows if the ticket open page is shown without selecting a new user account. Autocorrect should be disabled on that box too.
-
Jared Hancock authored
-
Jared Hancock authored
HTML does not allow nested <p> tags. Therefore the user warning was not correctly hidden with the rest of the user change confirmation message.
-
Jared Hancock authored
Fixes a regression in 1.8 where user names and emails submitted via the web interface would not properly be detected by the filter system for rejection. References: http://osticket.com/forum/discussion/75456/v1-8-ticket-filter-for-banning-domain-doesn-t-work
-
- Dec 13, 2013
-
-
Peter Rotich authored
Starting with v1.8 osTicket will require mysqli extension.
-
Jared Hancock authored
This reverts commit e818fd2c.
-
Jared Hancock authored
-
Jared Hancock authored
-
Jared Hancock authored
Turns out that the query to fetch a "short" list from MySQL is slower than just running all the filter rules in PHP
-
- Dec 12, 2013
-
-
Jared Hancock authored
-
- Dec 11, 2013
-
-
Jared Hancock authored
-
Peter Rotich authored
Replace phone number on ticket owner update
-
Jared Hancock authored
Displaying field values on various pages and dialogs could result in cross site scripting exploits. Fixes osTicket/osTicket-1.8#296
-
Jared Hancock authored
Previously only the name, email, and phone number would be displayed on the pop up dialog
-
Jared Hancock authored
Otherwise, you can't click on the custom form in the table view in order to manage it. Fixes osTicket/osTicket-1.8#276
-
Jared Hancock authored
Previously, the user information could only be modified on the ticket-view page. For instance, if creating a new ticket for a user, no new information could be added or modified on the user until after the ticket was created Fixes osTicket/osTicket-1.8#281
-
Jared Hancock authored
Previously, advanced search was bugged in such a way that the advanced search on a field without a `name` value would result in a hit of all the tickets. Fixes osTicket/osTicket-1.8#288
-
Jared Hancock authored
-
- Dec 10, 2013
-
-
Jared Hancock authored
The check in DynamicFormEntry::getAnswers() will use the cached _values array if it is not set to null. Previously, the ::save() method would set it to an empty array.
-
Jared Hancock authored
Previously, new fields would never show up on the company info page
-
Jared Hancock authored
Change thread entry title bar to use more flexible layout using div's and span's in hopes of avoiding unnecessary wrapping -- especially in the poster name column..
-
Jared Hancock authored
-
Peter Rotich authored
-
- Dec 09, 2013
-
-
Jared Hancock authored
Fixes #262
-
Jared Hancock authored
Again, fix issue where multiple mails fetched in the same fetch run will set the user of each of the mails to the user of the first email fetched. The previous patch neglected to pass the new $cache argument through the inherited UserForm::getFields() function.
-
Jared Hancock authored
-
- Dec 05, 2013
-
-
Jared Hancock authored
If two emails were fetched in the same timeframe, they may both be assigned to the same user account.
-
- Dec 01, 2013
-
-
Jared Hancock authored
Fixes oversize image display to be resized in both the ticket thread and the redactor editor in (at least) * Ticket-view boxes * Client new-ticket form * Staff new ticket * Page add/edit * FAQ add/edit * Canned response add/edit Fixes osTicket/osTicket-1.8#247
-
- Nov 30, 2013
-
-
Jared Hancock authored
Previously, due to a bug in Ticket::getPhone(), the first digit of the formatted phone number was displayed only. This patch will allow display of the entire formatted phone number. Fixes osTicket/osTicket-1.8#248
-
Jared Hancock authored
'where 1' and 'where 1=1' gives me hives...
-
Eivind Ravndal authored
-
- Nov 27, 2013
-
-
Jared Hancock authored
If a ticket is currently unassigned and your respond to it, it's yours. If a ticket is closed and later reopened due to a new message, the last respondent will always be assigned if available at the time.
-
Jared Hancock authored
-
Peter Rotich authored
-
Peter Rotich authored
-
Jared Hancock authored
-