Articles now open even when engagement storage is unavailable
The Development Article reader has been hardened so article content is no longer dependent on the comments and reactions database tables being available.
Previously, an unavailable database connection or missing article-engagement migration could trigger an HTTP 500 error while opening an article. The page now loads the article normally and temporarily disables engagement controls until the database is ready.
What changed
Article content always remains readable.
Database failures no longer crash the public article route.
Reactions display safe zero counts when unavailable.
Comment submission is temporarily disabled with a clear status message.
Server logs retain the underlying database error for staff diagnostics.
Existing approved comments and reaction behavior resume automatically once storage is available.
Installer requirement
The Installer remains responsible for applying the article engagement migration. This reliability layer protects the public website while installation, repair, upgrade, or downgrade operations are in progress.
Leave a comment
Comments are reviewed before appearing publicly.
Approved comments