Browser: Chrome 110 OS: macOS / Windows / Linux / etc. URL: Link to a page that illustrates this issue Video: Short screen recording that illustrates this issue (free tool: jam.dev)
if disable setting : COOKIE CONSENT
url after send site/page/?unapproved=26160&moderation-hash=0fc5af04ef0c7fe58c07e97d5979ee32#comment-26160
What is written above turned out to be WordPress behavior. But now it’s definitely a mistake. Checked!
If theme Bricks is enabled, the verification message is not displayed. Displayed in standard themes.
I either didn’t understand your report or I was unable to replicate your issue.
I created a single template with a comments element and then created a user with the role “subscriber” and I can see the “notice” when I submit a comment:
I just noticed that this report fell through the cracks, sorry about that! I was able to recreate the issue with logged-out users and added this to our internal bug tracker.
has this been fixed? i’m having the same issue. when not a non-logged in user submits a comment, the page reloads with /?unapproved=26160&moderation-hash=aflr but does not display a message that it’s awaiting moderation.
@charaf Hmm, I still don’t see any difference on 1.10.3, when a comment is submitted by a visitor that is not logged in and simply entering their name, email and comment, the page reloads with no indication the comment submission was successful and pending moderation, the only thing that I can see after a comment is that there is now a change to the URL e.g. #comment-68
Is there something that needs to be enabled/altered within the settings?
Can you maybe try temporarily disabling all plugins? If the issue persists, please share temporary admin access with a link to this forum thread to help@bricksbuilder.io so we can investigate why you’re still encountering the issue on your site.
yep, it still is, but only if there are no comments that are approved. As soon as there is at least one approved comment on a post, users can see their own unapproved ones.
We are working on a fix and we will update the topic that @HOSEIN linked once the issue is solved.