The Problem:Currently, when a node is set to "Moderate new threads," a user who posts a new thread can see it immediately, marked with an "Awaiting approval" banner. However, this visibility relies on the session cache. Once the session expires, the user logs out, or the hourly cleanup task runs, the pending thread completely disappears from the author's view.
The UX Impact:This creates a significant usability issue and confusion. Users often log back in a few hours later to check if their thread was approved. When they don't see it, they naturally assume there was a technical error or that it was accidentally deleted. As a result, they post the exact same thread again. This leads to user frustration and creates unnecessary duplicate work for the moderation team.
The Proposed Solution:I suggest adding a core forum permission (e.g., "View own unapproved threads") or altering the default behavior so that authors can always see their pending threads permanently, regardless of the session state, until a moderator explicitly approves, rejects, or deletes them.
While I am aware there are third-party add-ons that address this specific issue, this fundamental user-experience behavior really belongs in the XenForo core.
The UX Impact:This creates a significant usability issue and confusion. Users often log back in a few hours later to check if their thread was approved. When they don't see it, they naturally assume there was a technical error or that it was accidentally deleted. As a result, they post the exact same thread again. This leads to user frustration and creates unnecessary duplicate work for the moderation team.
The Proposed Solution:I suggest adding a core forum permission (e.g., "View own unapproved threads") or altering the default behavior so that authors can always see their pending threads permanently, regardless of the session state, until a moderator explicitly approves, rejects, or deletes them.
While I am aware there are third-party add-ons that address this specific issue, this fundamental user-experience behavior really belongs in the XenForo core.
Upvote
7
