New API enhancements for Sidenotes, Chat, Comments, Live Blog, and Reviews
Production Release 1/22/15
- API: Added a new parameter for the Sidenotes ConvConfig object which allows you to specify the location for the note.
inlineThreads (optional) Boolean: If true, Sidenote threads are inserted directly after the block with which they are associated. Default is false.
- API: Added a new HTTP API endpoint: Most Votes. Use this endpoint to get the 25 pieces of Sidenotes or Reviews content in a Collection with the most Votes.
For more information, see Most Votes.
- API: Added an optional new ConvConfig parameter, which allows you to disable Livefyre’s default shiv in IE8. This parameter is available for Chat, Comments, and Live Blog.
disableIE8Shim (optional) Boolean: Disables the default shiv used by Livefyre to polyfill Internet Explorer 8 so that HTML5 elements are supported. Livefyre uses the following project: https://github.com/aFarkas/html5shiv. Default is false.
Note: If this value is false, polyfill of some sort must be used before Livefyre Comments is invoked for Internet Explorer 8 support.
- Studio: Fixed a bug which prevented site-defined Premoderation rules from being applied to Curate Rules by default. Curate Rules will now inherit their Site’s Settings > Network Configuration > Premoderation setting.
UAT Release 1/23/15
- Unified Login is now available to all enterprise customers on UAT. Unified Login allows Site and Network Owners and Moderators to access Studio using a Studio account. Users with Moderator access to multiple networks will be able to manage these networks from a single Studio account.
For more information, see Accounts and Moving to Unified Login.
Livefyre Maps SDK
StreamHub v1.3.2 (Jan 21)
- Maps will now properly attribute the amazing OpenStreetMap team for the data that Maps renders using MapBox tiling. We sincerely regret releasing v1 of this project without it.
- Tile image requests will now use HTTPS, rather than HTTP.
- The broken image request handler will now be more lenient on the structure of Content being rendered. This helps avoid some uncaught exceptions in the /examples/.