Threadmarks Pro

Threadmarks Pro 2.14.1

No permission to buy ($40.00)
  • Fix merging threads would not merge threadmarks from source threads into the target thread in a predictable way.
  • Harden threadmark index handling of threads which were unexpectedly hard-deleted
  • Fix "Error rendering widget: ...setContentFromAlias(): Argument #1 must be of type string, null given"
  • Fix edge case where the content for a threadmark could be loaded twice
  • Harden notification code paths to better handle sending large number of alerts
    • Requires Thread starter alerts v2.5.0+ add-on to actually use
  • Fix rounding for word-count in threadmark rss feed
  • Add support for upcoming Thread starter alerts v2.5.0+
    • It will adds "threadmark alerts", not just "thread starter alerts".
  • Add image dimensions and mark as lazy loading for a thread's threadmark index icon
  • Update per-forum option "Use threadmark index icon instead of a user avatar in the thread-list" to "Use threadmark index icon instead of a user avatar"
    Supports [searchcontent] bb-code from Advanced BbCodes pack, and autocomplete from ElasticSearch Essentials.
  • Update to better support new "INP" or "Interaction to Next Paint" by avoiding triggering repaint/reflow of content on threadview due to attempting to fit too many categories inline with the top page nav controls
  • When sorting threadmarks by category, display the threadmark's content creation date
  • Add sort-threadmark link per recent threadmark list if the user can sort threadmarks
  • Fix "SV\Threadmarks\Job\Cache::getNextIds(): Return value must be of type array, null returned" error generated when installing add-on.
    This did not block the installer or cause the add-on to fail, but could cause repeated errors if the site was in debug mode.
  • Fix edge case with installer when the add-on is deleted and re-installed when extended by other add-ons
  • Fix not syncing the threadmark state when the post state changes (ie deleted)
  • Fix various numerical admincp options which did not step in the incremental values as intended, while allowing arbitrary values in the range to be entered
Back
Top Bottom