Record closed-by if opening a ticket with state closed

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

i18n: Fix display of language selection for new templates

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

ui: Implement "enable canned responses" config option

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

orgs: Add support for organization variables

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

i18n: Oops hide erroneous "published" status for internal FAQs

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

forms: Properly display staff/user field requirement

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

html2text: Avoid long, wrapped URLs in a tags

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

faq: Ensure consistent formatting for all

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

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>

This affects new ticket by staff as well as honoring the influence of ticket
filters on new ticket, where the status may be set to something other than
the system default. Even the system default may be influenced if it were set
to a closed state derivative.

So the concept is simple: the new status should be set using the standard
logic so that the closed_by staff member, date, events, and other
information is set as normally is when a ticket is closed.

This patch removes the selection of canned responses as well as the canned
responses navigation page from the ui when the canned responses feature is
disabled.

Allow usage of something like `%{ticket.user.organization.var}`

Faq articles should be viewed in the .thread-body div in the client portal
like they are in the staff portal.

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.