- Jan 27, 2014
-
-
Jared Hancock authored
If the mail received into the system has a content type of 'message/rfc822', then unwrap the inner message and use it as the parsed email. Effectively, assume the email was forwarded as an message/rfc822 attachment.
-
Jared Hancock authored
Previously, the subject was duplicated, which is really confusing
-
- Jan 24, 2014
-
-
Peter Rotich authored
Handle email bounce notifications Reviewed-By:
Peter Rotich <peter@osticket.com>
-
Jared Hancock authored
-
Jared Hancock authored
Timeout after max timeout while fetching emails Reviewed-By:
Jared Hancock <jared@osticket.com> Reviewed-By: Alan Wilkes
-
Jared Hancock authored
Hide close/hide dialog when esc key is pressed fixes issue #441 Reviewed-By:
Jared Hancock <jared@osticket.com>
-
Peter Rotich authored
forms: Fix ticket submission if already logged in Reviewed-By:
Peter Rotich <peter@osticket.com>
-
Jared Hancock authored
If a client is already logged into the client portal and attempts to submit a new ticket, the ticket will be rejected if the contact-information form has a required field other than `name` and `email`. This patch fixes `class Client` so that the user-id is fetched from the database and made available via the `::getUserId()` method. This was already corrected in the `develop-next` branch for v1.8.1. The `uid` field is passed into `Ticket::create()` so the user form validation is bypassed. This commit should be ignored when merged into the 1.8.1 codebase.
-
Peter Rotich authored
Processing fetching in ASC order of the last fetch time Remove LIMIT of 10 emails per fetch Flush the buffer and terminate the request cleanly on autocron
-
slm4996 authored
-
- Jan 23, 2014
-
-
Jared Hancock authored
-
Jared Hancock authored
-
Jared Hancock authored
This allows the email system to detect something like a bounce mail and specify that the associated message should be an internal note.
-
Jared Hancock authored
-
Jared Hancock authored
Previously, the mail parsing and fetching system would recurse unbounded searching for bodies by content-type
-
Jared Hancock authored
If a custom list item were added to an email template, and there is no data for the field (ie. the field is not required) when the template is rendered, the system would crash. toString() is required to return a string, no matter what. This patch cascades the (string) coercion to the current value of the list field if it is not an instance of a DynamicListItem
-
Peter Rotich authored
Fix display of priority field in queue export Reviewed-By:
Peter Rotich <peter@osticket.com>
-
- Jan 22, 2014
-
-
Jared Hancock authored
Also removes the fetching of priorities separately and addresses sorting of priorities by the ID field rather than the urgency field.
-
- Jan 21, 2014
-
-
Peter Rotich authored
Fixup querying drop-down lists via advanced search Reviewed-By:
Peter Rotich <peter@osticket.com>
-
Jared Hancock authored
It turns out that the _id field was not added to the cdata table when it was created for SelectionField items, because the ::hasIdValue() method was not implemented. This patch correctly searches SelectionFields via advanced search.
-
- Jan 20, 2014
-
-
Peter Rotich authored
forms: Fix ambiguous id / value for typeahead Reviewed-By:
Peter Rotich <peter@osticket.com>
-
Peter Rotich authored
Log password reset attempts Reviewed-By:
Peter Rotich <peter@osticket.com>
-
Jared Hancock authored
If the text does not match the value on record in the custom list, then the value entered in the field cannot be accepted. NOTE: This may have unintended i18n consequences, where there are varying ways to write a letter in Unicode which may be rendered the same but will not be correct with a string ==.
-
Jared Hancock authored
-
Jared Hancock authored
If something fishy, like an Array is received into the password reset system or any part of the Staff management system, it should be rejected. References: http://osticket.com/forum/discussion/76003/sql-attack
-
Jared Hancock authored
Conflicts: include/mysqli.php
-
Jared Hancock authored
-
Jared Hancock authored
Allow staff to cancel user lookup popup when creating a new ticket Reviewed-By:
Jared Hancock <jared@osticket.com>
-
Peter Rotich authored
Make using `realpath` safer Reviewed-By:
Peter Rotich <peter@osticket.com>
-
Peter Rotich authored
The change will allows staff to open a new ticket without going through the "forced" user lookup popup. On cancel the staff is presented with a simplified user info form with email and name being the only fields required.
-
- Jan 19, 2014
-
-
Peter Rotich authored
Revisit template management page Reviewed-By:
Peter Rotich <peter@osticket.com>
-
Peter Rotich authored
forms: Allow decl of prompt and default for choices Reviewed-By:
Peter Rotich <peter@osticket.com>
-
- Jan 18, 2014
-
-
Peter Rotich authored
Fix parameter count to TicketLock::lookup Reviewed-By:
Peter Rotich <peter@osticket.com>
-
Jared Hancock authored
Required for PHP 5.5 compatibility
-
- Jan 17, 2014
-
-
Peter Rotich authored
Ensure a ROOT_PATH is defined for CLI apps Reviewed-By:
Peter Rotich <peter@osticket.com>
-
Jared Hancock authored
Allow the administrator to enter a prompt to be shown in the choices drop-down for choice fields. Also add the option of selecting a default value from the list initially rather than displaying a prompt.
-
Peter Rotich authored
filters: Unpack the user information before filter Reviewed-By:
Peter Rotich <peter@osticket.com>
-
clonemeagain authored
Missed one.. :-(
-
clonemeagain authored
Couldn't find the rebase to this.. actually, I didn't look, I'm still struggling with git and eclipse, would probably have been easier with vim! Anyway, rewrote changes for 1.7.
-
Jared Hancock authored
If a user is created / selected before opening a ticket (very likely the case in the SCP), the email address and name should be unpacked into the $vars dictionary prior to creating and processing ticket filters
-