This patch introduces an automatic materialized view to speed database
performance when querying and displaying the ticket views. This can
eventually be extended to the search and advanced search features to speed
them as well.

The data from the dynamic form entries related to ticket details is copied
to a %ticket__cdata table. The %ticket__cdata table is then joined directly
to the other tables in the query for the ticket view. MySQL is magically
and dramatically faster using this method.

The downside is that the disk usage for the custom data is doubled, and the
time needed to update the dynamic data is at least doubled as the form
entries and the materialized view must both be updated.

This method should also extend well to other database platforms in the
future. It will be likely that most other database query optimizers will
have difficulty joining, scanning, and sorting the table models we have for
custom data fields.

Fixes #356

Otherwise the <img> doesn't get the correct uri for the image.

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

Update ajax.php

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

Ensure aquireLock doesn't interfere with renew/release

orm: Fix serious logic issue in the save() method

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

names: Add option for original name

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

And define getInitials() function for %{ticket.name.initials}

ui: Remove autocorrect from the user lookup dialog

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

Fix UI bug where user change warning always showed

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

forms: Allow user name and email to be blocked

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

This box shows if the ticket open page is shown without selecting a new user
account. Autocorrect should be disabled on that box too.

HTML does not allow nested <p> tags. Therefore the user warning was not
correctly hidden with the rest of the user change confirmation message.

Fixes a regression in 1.8 where user names and emails submitted via the web
interface would not properly be detected by the filter system for rejection.

References:
http://osticket.com/forum/discussion/75456/v1-8-ticket-filter-for-banning-domain-doesn-t-work

Drop support for mysql extension (deprecated as of PHP 5.5.0)
Here goes nothin!

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

Starting with v1.8 osTicket will require mysqli extension.

Fix regression displaying errors on ticket form

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

This reverts commit e818fd2c.

performance: Improve performance of ticket queue pages

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

filters: Handle all filter rules in PHP

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

Turns out that the query to fetch a "short" list from MySQL is slower than
just running all the filter rules in PHP

User: Ticket owner update

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

Replace phone number on ticket owner update

forms: Fixup possible XSS exploit

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

Displaying field values on various pages and dialogs could result in cross
site scripting exploits.

Fixes osTicket/osTicket-1.8#296

Previously only the name, email, and phone number would be displayed on the
pop up dialog

forms: Require `title` for all custom forms

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

Allow edit of user on ticket-edit page

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

forms: Fix advanced search on fields without a `name`

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