This will hopefully remove some of the confusion from the repeated
names in the various initial data

Include changes made just before 1.7.3 release

Conflicts:
	include/ajax.config.php
	include/class.ticket.php

Use seemingly-random form input names

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

Add %{ticket.user} to ticket template variables

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

Fix oops in text email conversion

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

Provide fallback functions for mbstring module

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

Advertise new prerequisites on install and upgrade

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

Make cacheable more portable

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

Start translatable help popup "tips"

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

Remove <![if !mso]> tags and friends

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

Allow internal, required fields

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

In some edge cases, priority may not be set for a ticket

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

Add long lost kb category listing background

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

Add --clean option to deploy script

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

Use system date format for date picker

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

Previously the American date format (m/d/Y) was used exclusively for
formatting dates in the datepicker widget. This patch enables the widget to
be formatted based on the format set in the admin panel.

Fixes #829

Content disposition parameters are optional

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

If a Content-Disposition header exists for an attachments, it isn't required
to have any parameters (like a file name)

Overhaul the popup tips from the installer to make them translatable and
work toward popovers for all the admin and staff panel settings.

Also remove CSS properties from the style attribute that are browser
specific (like -webkit-* and such)

Previously, clients would not be able to create tickets if an internal,
required field existed on any of the forms presented to the user. Instead,
they would be stuck at permanent validation failure because there was no
data for a required field not shown.

This patch adds a feature to the form and dynamicFormEntry objects'
isValid() method to receive a callable to filter which fields' errors should
be added to the form's errors list. This allows for more complex validation
where in some cases, validation errors should not be considered on some
fields.

Fixes #45

Fixes #40

Move the cacheable code to the Http class and allow the client configuration
to be cached in the browser

Better email headers for In-Reply-To and References

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

Which will help fight off spammers. This should be coupled with logic that
will add some enticing fields, like 'email' and 'name' to invite bot input.
Then, on the form processing side, a spam submission can be detected and
handled differently from human submissions. This should lessen reliance on
CAPTCHA only as spam detection.

Make captcha text case-insensitive

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

Previous the options defined for the Mailer::send() function were confusing
when sending an In-Reply-To header

Previously, the References header emitted by the system for new thread
entry auto-responses and alerts included the message-id for which the email
was a reply in the `References` header. This patch corrects the issue by
placing the reply message-id in the In-Reply-To header, and constructs a
correct References header.

That is, if available, the References header received in the email that was
used to create the thread entry is appended to the message-id the email is
actually in reply to. This is the expected usage of the References header.

Allows the deploy script to remove files in the target that are not preset
in the current repository. This patch assumes pure stock osTicket
deployments -or- that the files deployed in the target are also present in
the local repository.