Review QCLF Topic and Message Revision History
QCLF preserves the version that existed immediately before each Topic or Message edit. Revision history is displayed only to the content author or a moderator for that Category.
The revision list supports accountability without making inaccessible forum content public.
What Is Preserved
| Revision type | Stored history |
|---|---|
| Topic revision | Previous title, previous rich HTML/text, editing user, optional reason, timestamp. |
| Message revision | Previous rich HTML/text, editing user, optional reason, timestamp. |
How History Is Created
When an authorized edit is submitted, QCLF writes the current version to the appropriate revision table before updating the live Topic or Message. That means each revision entry represents the version being replaced, not a duplicate of the newly-saved version.
Who Can See It
The frontend renders revision history only when the current signed-in user is the original author or is a QCLF moderator for the Category. Other readers do not receive the revision panel.
Normal Topic/Category access is checked before the page itself is available, so revision history is not a separate route that bypasses forum visibility.
How Much History Is Shown
QCLF loads the newest revision entries first and currently renders up to 20 Topic revisions or 20 Message revisions in the frontend history panel. Each entry identifies the edit time and editor name, with the optional edit reason when supplied.
Deleted Content
A soft-deleted Message does not render its attachment/revision panel in the normal Topic view. A soft-deleted Topic is removed from the ordinary Topic loader entirely until restored by an authorized moderator.
Permanent purge removes the Topic/Message revision rows with the rest of that Topic-owned data.
Community Discussion
Want to compare forum workflows, share practical QCLF tips, or discuss how other Joomla site owners use this feature? Visit the QC Live Forum Community. For private support, bug reports, account-specific entitlement problems, or feature requests, use the QuantaCade support system.