prepare for release of 2.0.18 | package party
prepare for release of 2.1.0 | package party
Roll back to JwPlayer 6.5

6.6 added skins for mobile devices, which are poor performing, and can have leaky css. Use the latest version prior to mobile skins until they add the ability to turn mobile skinning off.
call SwatForm::clearAuthenticationToken correctly.

It is a public static method, so call appropriately.
Add optional support for google display advertising tracking to analytics.

Display advertising lets sites turn on interest and demographic reports as well
as leverage marketing and display network impression tracking.
https://support.google.com/analytics/answer/2444872

This is off by default as it requires privacy policy changes to turn on.
https://support.google.com/analytics/answer/2700409
Update docs to use a simplier version of the support url.
consistent spacing for the analytics config definitions.
Merge pull request #40 from isaacgrant/clear-auth-token-cleanup

call SwatForm::clearAuthenticationToken correctly.
Merge pull request #42 from isaacgrant/display-network-analytics

Add optional support for google display advertising tracking to analytics.
Fix seeking on Android.

Seeking on Android is broken in the same manner as iOS. So you need to start the video, and then seek to the position, otherwise playback starts at the beginning.
Merge pull request #38 from isaacgrant/jwplayer-6.5

Roll back to JwPlayer 6.5
prepare for release of 2.1.1 | package party
Fix SiteComment AjaxServer comment saving.

This was updated to call SiteComment's internal cache clearing back in r76399 / 60a314ea38c8956878fd840c6a8329cfde00b93e but marking comments as spam/not spam wasn't correctly updated. Looks like we never noticed this as most spam was caused by Akismit. Calls to mark spam without this just hang.

I also took the liberty of updating postSave() to always call clearCache() to simplfy our calls.
Merge pull request #43 from isaacgrant/comment-saving

Fix SiteComment AjaxServer comment saving.
I don't see why we need to limit this to non-instance sites
make it easy to subclass login page on failure
null => SiteInstance
Merge pull request #46 from nburka/remove-limitation-of-config-settings

I don't see why we need to limit this to non-instance sites
Merge pull request #47 from nburka/handle-error-on-login

make it easy to subclass login page on failure