This addresses an issue where creating an advanced search with selection
field "does not have a value" throws a fatal error. This was due to an
improperly named search method "notset".

This addresses issue where upon deletion of a form field and all its
entry values, the field record wouldn't be deleted from the `form_field`
table. This links another issue where you can't delete a list if its
been a field before. This is due to the list delete() function that
checks for list field records in the `form_field` table.

When issue summary is disabled for a specific help topic, the system uses
help topic name as the subject line.

Due to validation error on disabled subject field the setValue fails to take
in the help topic. The change here allows for forced value set.

Set _value in DynamicFormEntryAnswer even when value is empty.

Add a preview tool tip to show list item properties on mouse-over.

This fixes an issue where the CDATA table is updated with the OLD version of
an answer after it is updated. That is, after an answer is updated, the
CDATA table is also updated to reflect the change; however, the old content
of the answer value is used when updating the CDATA value.

Previously, the create method was used to create a new instance of an orm
model (which would later result in an INSERT when persisted); however, some
classes require or utilize varying parameters to their create() method,
which PHP7 considers an error. Methods in subclasses must be defined with a
calling signature compatible with the parent class.

This patch shifts the concept of model creation to the constructor. Now, the
constructor of ORM models is required to be compatible with that of
ModelBase class. Now that most models do not define a constructor, this is
much easier to control, and much more logical.

Also, remove an issue where assignments on a relationship field to an
instance of a super class of the foreign model would raise an error. This
was previously addressed by re-classing the instance in the
ModelInstanceManager::getOrBuild(); however that design would create
multiple instances of the same object in memory, which defeats one of the
primary design concepts of the ORM. This patch addresses the issue by
allowing super-classes of the declared foreign model in relationship
assignments.

This commit attempts to remove all coding standard warnings emitted by PHP
7.0.

Strip tags on text input field to prevent potential XSS exploit.

This changes the storage model for datetime fields and stores them in the
same format as the MySQL `datetime` column type. This allows for the
searching code to be consistent when searching the database for
datetime custom form entry data.

Change orgs listing to ORM
Add cdata tables support for users and organizations

MySql 5.6 and MariaDB 10 will return affected_rows == 0 if updating a row to
its current values. Therefore, if an object is "edited", but none of the
CDATA is modified, then the CDATA table might be dropped and rebuilt.

Use `if not exists` in the create statement for the %cdata table so that, in
some race conditions, a MySQL slave would not be crashed because of an
already-existing table.

Also fix several javascript errors on ticket edit

This will allow for self filtering form based on options
Delegate form validation to Form instead of DynamicFormEntry

* Preserve external storage flag on field configuration
* User gridlayout to render task's forms
* Use new roles for task's nav

Credit: Jared Hancock <jared@osticket.com>

Allow fields without data to do house-cleaning on deletion.

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.

Support ability to include attachments to FreeTextField.

This adds ability to delete properties on list deletion

Also make forms deleteble by marking them as deleted and hiding them from
the form listing. This ensures that custom data always has a link back to
the form.

These fields have been consolidated into the `flags` column.

Also, fix roundtrip encryption if the form name changes (which is based on a
user's session), and avoid saving a NULL value if the password is not
changed when a form is updated.