Add web.config for IIS to serve the API

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

Sanitize log entries

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

Inline Attachments

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

Properly escape HTML chars in text/plain email bodies

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

Only set "ft" field if requested

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

Add "Assigned To" and other fields to ticket export

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

Incoming messages with empty body and an inline attachment might not have
parts - depending on encoding used.

* Use "-" tag for emails with empty body/message

If there characters in the plain text body of the email that appear like
HTML tags, for instance

From: <sip:527772432@172.18.0.2>;tag=952422a9dd1ap1a6o1

The <sip...> part would be removed by the Format::striptags() call in
Format::sanitize().

The "ft" field does not exist when the attachment migration takes place.
Therefore, attachment migration will fail because the records cannot be
inserted into the database due to the missing "ft" field.

Addresses #589

Address lint testing regressions
Reviewed-By: Peter Rotich <peter@osticket.com>

Fix CSS style issues

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

Password reset feature

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

Only fetch client config on pages with file upload

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

Logo is not displayed in the offline page

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

The client and scp config ajax request only contain the settings for the
multi-file upload widget. So it doesn't need to be fetched unless the widget
exists on the page

  - Logo selection radio buttons not vertically centered (Firefox)
  - font-size value incorrect in login.css
  - Incorrect : placement in FAQ category edit
  - Incorrect block width declaration (700 vs 700px)
  - Browsers disagree on the placement of CSS3 outline properties
  - Correctly place check boxes and radio buttons

We should move initial data out of the install SQL file, which will make way
for a few things:

  * Internationalization -- which breaks the migrater model currently.
        Moving the data outside the install script makes it translatable
        without changing the SQL hash
  * Review -- Migrations which add more data don't highlight new features
        that need review to the adminsitrator

Uses a seven step procedure:
  1. (user) Fails to login twice or more
  2. Clicks the 'Forgot my password' link on the login form
  3. Submits the username or email address and triggers a password-reset
     email
  4. Clicks the link in the email and is directed back to the reset page
  5. Enters the username or email again and is logged in
  6. Password change is forced, but current password is not required
  7. Password is updated, user can continue the session without
     authenticating again

Use %config table by default for config classes

Add lastModified() method to retrieve the time of last modification for a
configuration key

Add $defaults to the specified on a subclass. The defaults remove the
necessity to specify a default value for each getter method, and, the
defaults are integrated into the array retrieved from getInfo()

Use mysql connection timing as the random seed, along with the microseconds
of the current time.

After merging the custom logo patch, the logo on the offline page
disappeared. This addresses the issue by exempting the logo.php script for
the offline redirect in client.inc.php

Allow custom logo integration on client site

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

Data migration tool

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

Allow authentication with email-address+password

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

Allow generation and serving of abritrary custom pages

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

Fallback to base64_decode if imap_base64 fails
Reviewed-By: Peter Rotich <peter@osticket.com>

Do numeric comparison on db versions

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

Administrators are allowed to upload one or more logos and then select from
the uploaded logos to set one for the client site. Logos can also be deleted
on settings->pages submission

Previously, username and password were required. With this patch, the
email address can be used to authenticate the user with the password