topic-map v0.2.1
Fixed
The topic map returned a 500 on every discussion, on any forum installed with a database table prefix.
The Top Replies query built its SELECT and ORDER BY as raw SQL, and raw SQL is handed to the database verbatim — the query builder cannot prefix what it cannot parse. Every other call in that query is prefix-aware, which is exactly why the two raw fragments were easy to miss. On a prefixed install the query asked xyz_posts for a column called posts.id:
SQLSTATE[42S22]: Unknown column 'posts.id' in 'SELECT'
And because the controller builds the whole map in one pass, this did not degrade the Top Replies panel — it took the entire topic map down, on every discussion, for the life of the extension on that forum.
Only the aggregate genuinely needs raw SQL, so it now carries the prefixed table name explicitly and the four columns go through the builder.
Verified against a forum that runs a prefix on purpose: the endpoint went 500 → 200, Top Replies lists its ranked replies with like counts, and a discussion with no likes returns an empty list rather than an error. Forums without a prefix were never affected and see no change.
Also in this release
- The release announcer renders its Markdown instead of posting the raw source, and can be triggered manually.
View release on GitHub
