If the text does not match the value on record in the custom list, then the
value entered in the field cannot be accepted.

NOTE: This may have unintended i18n consequences, where there are varying
ways to write a letter in Unicode which may be rendered the same but will
not be correct with a string ==.

If a dynamic list is displayed as a typeahead box, the value, when saved,
will be confused with the corresponding ID field for the list. MySQL
supports numeric comparison between the INT id column and the textual value
column. Therefore, if a typeahead field has the value of '01 - GooGoo', then
record will match the ListItem<id=1>, regardless of which list the item is
defined for.

This patch resolves the issue by submitting the ID number of the list
selection in the HTTP form.

If the entry answer being updated does not affect the ticket details form
(with type=T), then the updates do not need to be applied to the
ticket__cdata table.

Several database performance tweaks

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

This is instead of optimizing the lock table for every cron run, which
wastes a lot of db server io

And deadband session token updates to 1 per 30 seconds

Drop the data table on field type change

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

If a field on the ticket details form changes type, recreate the cdata table

Use config URL instead of THISPAGE

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

THISPAGE is unreliable for CLI cron calls. It was historically used so the
admin could figure out which file/page generated the error. But with
backtrace support we no longer need it.

This is necessary because the system depends ticket priority to sort and
display ticket data.

Allow autocomplete on email address

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

Show extra forms for help topic first

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

Fix subject ticket number matcher (again)

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

Use case-insensitive matching on email address

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

This patch addresses an issue where a client may have upper-case letters in
their email address. When visiting the client portal to check the ticket
status, previously, the exact same case would be required in the 'Email
Address' box.

This patch remove the case sensitivity for email logins.

No longer require a priority for help topics

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

Pre-select default priority

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

Extra forms associated with the help topic are now shown above the ticket
details form on both the staff and client interfaces.

Fixes #390

For use in the materialized view column names

Fix possible serious errors in dynamic form fields

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

Fix ticket queue counts for limited users

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

Fix dropping of materialized view when variable name is changed

Ensure view exists before merging updates

Prevent possible sql injection error in field name used in the materialized
view.

Prevent possible xss error in the display of the field label and variable
name in the admin panel.

Ensure form for fields created during install

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

Conflicts:
	include/class.http.php
	include/mysqli.php

email: (Almost) always convert html on text body

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