- update to 1.8.7
  Compatibility-breaking changes
  * IMPORTANT: It is no longer possible to protect a group pad with a
    password. All API calls to setPassword or isPasswordProtected will fail.
    Existing group pads that were previously password protected will no longer be
    password protected. If you need fine-grained access control, you can restrict
    API session creation in your frontend service, or you can use plugins.
  * All workarounds for Microsoft Internet Explorer have been removed. IE might
    still work, but it is untested.
  * Plugin hook functions are now subject to new sanity checks. Buggy hook
    functions will cause an error message to be logged
  * Authorization failures now return 403 by default instead of 401
  * The authorize hook is now only called after successful authentication. Use
    the new preAuthorize hook if you need to bypass authentication
  * The authFailure hook is deprecated; use the new authnFailure and
    authzFailure hooks instead
  * The indexCustomInlineScripts hook was removed
  * The client context property for the handleMessage and
    handleMessageSecurity hooks has been renamed to socket (the old name is
    still usable but deprecated)
  * The aceAttribClasses hook functions are now called synchronously
  * The format of ENTER, CREATE, and LEAVE log messages has changed
  * Strings passed to $.gritter.add() are now expected to be plain text, not
    HTML. Use jQuery or DOM objects if you need formatting
  Notable new features
  * Users can now import without creating and editing the pad first
  * Added a new readOnly user setting that makes it possible to create users in
    settings.json that can read pads but not create or modify them
  * Added a new canCreate user setting that makes it possible to create users in
    settings.json that can modify pads but not create them

• Files Changed
• Browse Source