2.0.11
Security + performance hardening from a code audit. Recommended update — especially for forums with hidden / tag-restricted discussions or a non-public user list.
Security (server-rendered meta tags)
- Discussion and profile meta tags are now scoped to the requesting visitor's visibility. Previously, guessing the URL of a hidden, tag-restricted or soft-deleted discussion (or a hidden user's profile) returned its title/description (and a user's bio/counts/avatar) in the server-rendered
og:/twitter:/<meta name=description>tags — content the API would refuse to serve to that visitor. Crawlers and anonymous visitors no longer receive it.
Performance
- The Q&A (best-answer) JSON-LD no longer pulls every reply into memory: suggested answers are capped (200) and the accepted answer is fetched by id, so a thread with thousands of replies can't OOM the render that Google's crawler hammers.
- Discussion / Post / Tag event handling no longer constructs the heavy PageListener on every event — the pure content helpers moved to a stateless
SeoContentUtils.
Other
- Expose the social-media image on the forum payload (admin) via the normal serialization path instead of mutating the model data bag; small cleanups.
No migrations.