0.10.2

• fix getAttribute return value

0.10.1

• fix empty author, email and website values when writing a comment

Also a new release is required for the source distribution, since 0.10 has been uploaded previously and can no longer be re-uploaded on PyPi (see pypa/packaging-problems#75).

0.10

• add new configuration section for hash handling.

  [hash]
  salt = Eech7co8Ohloopo9Ol6baimi
  algorithm = pbkdf2

  You can customize the salt, choose different hash functions and tweak the parameters for PBKDF2.

• Python 3.4+ validate TLS connections against the system's CA. Previously no validation was in place, see PEP-446 for details.

• add fenced_code and no_intra_emphasis to default configuration.

  Fenced code allows to write code without indentation using ~~~ delimiters (optionally with language identifier).

  Intra emphasis would compile foo_bar_baz to foobarbaz. This behavior is very confusing for users not knowing the Markdown spec in detail.

• new configuration to require an email when submitting comments, #199. Set

    [guard]
    require-email = true

  and use data-isso-require-email="true" to enable this feature. Disabled by default.

• new Bulgarian translation by sahwar, new Swedish translation by Gustav Näslund – #143, new Vietnamese translation by Đinh Xuân Sâm, new Croatian translation by streger, new Czech translation by Jan Chren

• fix SMTP setup without credentials, #174

• version pin Misaka to 1.x, html5lib to 0.9999999

0.9.10

Fix #174.

0.9.9

• several Python 3.x related bugfixes
• don't lose comment form if the server rejected the POST request, #144
• add localStorage fallback if QUOTA_EXCEEDED_ERR is thrown (e.g. Safari private browsing)
• add '--empty-id' flag to Disqus import, because Disqus' export sucks
• (re)gain compatibility with Werkzeug 0.8 and really old html5lib versions available in Debian Squeeze, #170 & #168
• add User-Agent when Isso requests the URL, an alternate way to #151 (add 'X-Isso' when requesting).

0.9.6

• remember name, email and website in localStorage, #119

• add option to hide voting feature, #115

  data-isso-vote="true|false"

• remove email field from JSON responses

  This is a quite serious issue. For the identicon, an expensive hash is used to avoid the leakage of personal information like a real email address. A git blame reveals, the email has been unintenionally exposed since the very first release of Isso :-/

  The testsuite now contains a dedicated test to prevent this error in the future.

0.9.5

• prevent no-break space ( ) insertion to enable manual line breaks using two trailing spaces (as per Markdown convention), #112

• limit request size to 256 kb, #107

  Previously unlimited or limited by proxy server). 256 kb is a rough approximation of the next database schema with comments limited to 65535 characters and additional fields.

• add support for logging to file, #103

  [general]
  log-file =

• show timestamp when hovering , #104

• fix a regression when editing comments with multiple paragraphs introduced in 0.9.3 which would HTML escape manually inserted linebreaks.

0.9.3

• remove scrollIntoView while expanding further comments if a fragment is used (e.g. #isso-thread brought you back to the top, unexpectedly)
• implement a custom Markdown renderer to support multi-line code listings. The extension "fenced_code" is now enabled by default and generates HTML compatible with Highlight.js.
• escape HTML entities when editing a comment with raw HTML
• fix CSS for input
• remove isso.css from binary distribution to avoid confusion (it's still there from the very first release, but modifications do not work)

0.9.2

Add translation for Esperanto

0.9

• comment pagination by Srijan Choudhary, #15

  Isso can now limit the amount of comments shown by default and add link to show more. By default, all top-level comments are shown but only 5 nested comments (per reply). You can override the settings:

  isso-data-max-comments-top="N" isso-data-max-comments-nested="N"
  

  Where N is a number from 0 to infinity ("inf"). If you limit the amount of shown top level comments, the overall comment count may be incorrect and a known issue.

  You can also configure the amount of comments shown per click (5 by default):

  isso-data-reveal-on-click="N"
  

  This feature also required a change in the comment structure. Previously, all comments are stored tree-like but shown linearly. To ease the implementation of pagination, the comment tree is now limited to a maximum depth of one. Jeff Atwood explains, why discussions are flat by design.

  When you upgrade, Isso will automatically normalize the tree and some information gets lost. All new replies to a comment are now automatically a direct child of the top-level comment.

• style improvements by William Dorffer, #39, #84 #90 and #91

  Isso now longer uses a fat SCSS library, but plain CSS instead. The design is now responsive and no longer sets global CSS rules.

• experimental WordPress import, #75

  Isso should be able to import WXR 1.0-1.2 exports. The import code is based on two WXR dumps I found (and created) and may not work for you. Please report any failure.

• avatar changes, #49

  You can now configure the client to not show avatars:

  data-isso-avatar="false"
  

  Also there is no longer an avatar shown next to the comment box. This is due to the new CSS and removes two runtime dependencies.

• you may now set a full From header, #87

  [smtp]
  from = Foo Bar <spam@local>
  

• SMTP (all caps) is now recognized for notifications, #95

• Isso now ships a small demo site at /demo, #44

• a few bugfixes: Disqus import now anonymizes IP addresses, uWSGI spooling for Python 3, HTTP-Referer fallback for HTTP-Origin

• remove Django's PBKDF2 implementation in favour of the PBKDF2 function available in werkzeug 0.9 or higher. If you're still using werkzeug 0.8, Isso imports passlib as fallback (if available).

This release also features a new templating engine Jade which replaces Markup.js. Jade can compile directly to JavaScript with a tiny runtime module on the client. Along with the removal of sha1.js and pbkdf2.js and a few build optimizations, the JS client now weighs only 40kb (12kb gzipped) – 52kb resp. 17kb before.