fix broken error message, failure to complete email verification is not a hard error, but a warning.  closes #455

Consolidating the code we used to store off which site the email address was staged for.

Updating #origin to be .website to go along with the verify user.

Updating tests.

issue #349

issue #349

When verifying an email address, show the address that was verified and the site for which it was created.

issue #349

Only send messages to the hub if it exists.

close #477

in addEmail, save off the originating origin.

in verifyEmail, use the saved off originating origin for the returned info.  Always call onSuccess with an object, if token is valid, valid will be true, if token invalid, valid will be false.

This is going to be used to simplify the logic for client pages when they want to verify an email.

issue #349

issue #488.

The body's opacity was being set to 0.5 even with the error.  No bueno.

issue #448

A huge reduction of duplicate test code for checking notifications and whether the failure callback was called.

Made a get function to pass all the get requests through.

simplifying the code by removing most of the deferred callback code, only doing this in "get" and "post"

Going through all the user api and making sure all async functions have onFailure callbacks.

Adding tests for the user api to make sure that xhr failures cascade up.

Adding more messages to error-messages.

making sure the controllers are displaying error messages appropriately.

issue #448

Adding tests for all network calls to check whether they handle ajax errors correctly.  This includes network disconnection, server error codes, etc.

Fixing several calls that did not handle this appropriately.

issue #448

issue #448

Fixing the unit tests, by adding the new origin check, we broke two other tests.  Setting the origin to the expected value.

close #469

include full origin (inc. scheme) in generated assertions.  closes #82

Add's to Lloyd's pull request by keeping the extra info from being displayed to the user.

issue #82

close #447

There were some <div>s inside of <p>s

close #468

include full origin (inc. scheme) in generated assertions.  To preserve compatibility, allow the rp to omit scheme in post data, and subsequent to verification, return whatever the rp sent us.  issue #82