This fixes an issue where, when the mailfetch subsystem fetches more than
one email and one of them has a TNEF attachment; each message body after the
TNEF message will use the TNEF message body.

This patch fixes the issue by clearing the TNEF body in each cycle through
the message fetching and parsing loop.

search: Auto reindex when _search is created

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

This patch automatically configures reindexing of the search table when the
table is dropped and recreated.

variable: The HTML balancing system urlencodes @Hamsteren 

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

The DomDocument::saveHtml() method will properly urlencode() values in the
a[@href] attributes when saving. This patch allows for the sanitization
while also allowing the variable replacement system to work properly with
the sanitized values.

oops: Fix missing data from new form entries

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

cli: Fix incorrect option parsing

Peter Rotich <peter@osticket.com>

When using the php mail() function, the To: header encoded in the Mail_mime
library was not properly transferred to the $to variable passed to the mail
backend. The mail() function will add its own To: header which will
mimic the received destination address.

This patch ensures that the $to parameter is properly encoded.

Pass data to the callabale by reference

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

This fixes a regression in the option parsing where --setup would be
interpreted as --setup -e -t -u -p

Also, some parts of osTicket, like internationalization and plugins need
read access to a directory in order to get a list of installed plugins and
language packs.

When using call_user_func_array arguments should be passed by reference in order to allow callable receive them by reference (only defining callable to receive data by reference is not enough).

Fixes #2143

Ensure OoO message does not clear closing agent

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

This patch will help ensure that if a ticket is not reopened on a message
(perhaps because of a out-of-office auto-reply from an enduser), then the
closing agent on a closed ticket should not be cleared.

This fixes an issue where text scrubbed with the new balancing system would
receive a leading ' <div>' if the text started with a leading whitespace.

Thanks, @torohill

deploy: Add concept of a MANIFEST to the deployment process

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

This allows the MANIFEST to be hidden from HTTP requests since the entire
include/ folder is already denied for Apache.

This fixes a strange issue where the first field of a custom form stapled to
a ticket is not populated with data sourced from the API.

As an option, this will allow preventing deployment of files not tracked
with git. It's also about twice as fast as the PHP version.

This allows files which are edited on the fly during deployment to be
tracked so that they are not unnecessarily deployed again in the next
deployment run. It also allows for more creative deployment strategies using
something like `git ls-files -s`

html: Balancing is important

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

9ae01bf2 turned off HTML balancing, however,
quoted response removal will create unbalanced HTML. That HTML will be
stored unbalanced and will require extra processing when displayed on the
ticket thread.

This patch adds balancing support using libxml if enabled, which will
balance HTML without corrupting the HTML like htmLawed will with balancing
enabled.

forms: Fix fail getting value of password field

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

Force wrapping on long words e.g base64 encoded string

search: Fix several small issues with search indexing

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

* Reindexing did not properly flush the last batch of items to the search
  therefore reindexing would always miss the last few items.
* Creating a new html thread entry with inline images resulted in empty
  search content
* HTML tag stripping in HtmlThreadBody::getSearchable() would result in
  missing white space between some words, resulting in poor searchable
  content

Which seems to be used by recent versions of Andriod OS. It appears to be a
synonym of `multipart/related`