Conflicts:
	js/osticket.js

Add database name and schema signature to the system info page

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

Improve info display & formatting
Only show 8 chars of the last commit

redactor: Add right-to-left support

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

forms: Support non-US locale on client portal

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

The staff portal has a feature where the date fields are converted to
YYYY-MM-DD prior to form submission. However, this code was not ported to
the client portal. Therefore, for non-US date formats (d/m/Y for instance)
would not be processed properly by the server and would be nulled prior to
validation.

bug: Add ticket status properties field exist before loading initial data

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

Add ticket status properties field before loading init data.

Dependent fields

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

Ticket statuses revisited

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

Fix #1302.

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

Hide multi selection option for typeahead selections

Consider current status settings to determine if a ticket is reopen-able
Show a warning on staff's ticket view if the ticket is not reopen-able

This will allow administrator to indicate if end users are allowed to reopen
tickets in a particular closed status.

Hiding a field triggers visibility check on dependent fields
Use jQuery specific value getters

This will be useful for maintaining arbitrary list of items. ListObject
should be used in the place of ArrayObject

file: Propery support IE10 for file uploads

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

Use data view for ticket table client side

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

pages: Fix incorrect lookup of inline images

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

Fix issue that fails for get names on incorrect formats. Ex: J.Everybody

This is necessary to avoid confusion vs. closed state.

Also fix crash if the [name] of a widget element started with a digit
character.

This allows administrators to define a regular expression to filter content
entered into short answer fields by agents and endusers. With the new
visibility feature, the regular expression input is only shown if the
regular expression validator is selected.

This allows fields to specify a visibility constraint that will be evaluated
in real time in the browser to automatically show and hide fields that
should be hidden based on values of other fields in the same form.

Validation is not performed on fields server-side if they are considered
invisible when submitted.

bug: Fix status display on client interface

Shameless-Self-Merge: <peter@osticket.com>