Threadmarks Pro 2.24.7

• Fix pushing threadmark reactions to the thread's reaction totals would be reset when the first post was reacted to
• Fix "Add threadmark with backdate" permission not being respected when rendering the 'add threadmark' dialog. This permission was respected when actually adding the threadmark.

• Fix merging threads did not reliably update all threadmark positions as expected, and didn't correctly merge the thread's threadmark last read tracking

• Fix support for merging posts via inline moderation tools

• Fix merge/move post inline moderation action would fail to update the source thread metadata.
• Reduce redundant work done when using inline moderation tools for post copy/merge/move and thread merge.

• Fix new threadmark alerts where being triggered for edits

• When using the "Mark threadmarks read" thread action, now marks any alerts linked to those threadmarks as read as well
• Avoid showing duplicate title when viewing a threadmark list for a thread
• Add "read thread" link for non-embeded views of the threadmark index
• Add Per-category flag for whether all threadmarked posts are added to the first post info
• Fix edge case where threads without threadmarks which had a header attached would lose the threadmark header and now allow another to be added
• Fix case where threadmark notifications did not trigger when editing a post (requires Thread starter alerts to be usable)

• 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