lock: Set ticket lock on ticket-view

Reviewed-By: Peter Rotich <peter@osticket.com>

Ensure case-insensitive file extension comparison

Reviewed-By: Peter Rotich <peter@osticket.com>

Do NOT reopen closed ticket on auto-reply

Reviewed-By: Jared Hancock <jared@osticket.com>

forms: Display current value if set to bool FALSE

Reviewed-By: Peter Rotich <peter@osticket.com>

createTicket respects alert/autorespond negatives

Reviewed-By: Peter Rotich <peter@osticket.com>

Since the automatic lock was being acquired but not passed to the autoLock
system, the automatically acquired lock was not being release on away
navigation.

This patch addresses the issue by passing the automatically acquired lock id
to the autoLock system on ticket-view page load and change the ::Init()
method so that the lock id is not cleared with the ::Init() method is called
by the page load.

Ensure that when generating the list of acceptable file extensions, that the list is lower cased, because the extension from the filename will be lower-cased before attempting to find the extension in the list of acceptable extensions.

Do not reopen closed ticket, if the system can reliably determine that the new message is an
auto-response/reply from the end user.

forms: Properly export choices lists

Reviewed-By: Peter Rotich <peter@osticket.com>

files: Avoid crash if `file info` extension missing

Reviewed-By: Peter Rotich <peter@osticket.com>

Disable auto-responses on staff created tickets

Reviewed-By: Jared Hancock <jared@osticket.com>

i18n: Clarify attachment settings labels

Reviewed-By: Peter Rotich <peter@osticket.com>

pdf: Fix invalid UTF-8 characters error message

Reviewed-By: Peter Rotich <peter@osticket.com>

- Allows the string "false" to be used in the XML payload as the documentation demonstrates, and have that be interpreted as a boolean false.
- Switching $alert/$autorespond to use isset(), and forcing those variables to be type-casted to booleans.

Take into consideration the auto-response settings when sending out new
ticket by staff notice to the end user.

i18n: Add a few forgotten strings #2

Reviewed-By: Peter Rotich <peter@osticket.com>

thread: Fix regex for ticket # in email subject

Reviewed-By: Peter Rotich <peter@osticket.com>

forms: Drop custom data when removing a user

Reviewed-By: Peter Rotich <peter@osticket.com>

The ticket number regex was changed with the advent of custom ticket
numbers, and it matches the closing punctuation in [#12345], that is, the
closing bracket would be included in the ticket number sought in the
database. Therefore, it would never match the ticket number properly.

The new regex attempts to match punctuation and non-punctuation groups so
that punctuation in the middle of the ticket number is matched; however,
punctuation at the end is not. So #12345+DEPT will match properly and will
ignore any trailing whitespace and punctuation.

bug: Check to make sure $ost is initialized

Reviewed-By: Jared Hancock <jared@osticket.com>

Previously, this was not ported properly now that multiple selections are
supported in the choice field and derivatives.

It was previously not possible to use the `alert` and `autorespond` flags in a negative way to prevent those two events, since the ternary operator would have used the `false` ternary value, which was `true`.  This corrects that by allowing the default of `true` to be used only when the `$data` array does not have the appropriate keys set.  Assigning `$data['source']` was altered to use the same formatting and caution against an undefined index error.

Fix subject display when a ChoiceField is used

Reviewed-By: Peter Rotich <peter@osticket.com>

There was a slight issue when transitioning from a short answer field to a
drop-down field, and when the CDATA table is dropped and rebuilt.

forms: Fix interpretation of custom list data

Reviewed-By: Peter Rotich <peter@osticket.com>

Rollback to auto commit, except for sequence  iteration

Reviewed-By: Peter Rotich <peter@osticket.com>