You can test with “old”
]]>The page I need help with: https://www.edenbaylee.com
The moderator at the WP forum said the following:
Moderatorbcworkz (@bcworkz)
Your comment form has no fields for non-logged-in users to say who they are. I’d expect such comments to show as anonymous. A typical non-logged-in comment form usually has at least username and email fields (and the comment field). Not sure why your form lacks such fields. It appears to be a Jetpack comment form.
++++
I was unaware my form does not have a fields for username and email (for non logged in WP users) and this is what I would like. Regardless of this however, something has happened to the functionality for WP logged-in users. Their comments show as ANONYMOUS with “0 approved” even though they’ve commented on my blog many times before.
Can you please offer some insight? Thank you, eden
]]>Regular weekly commenters (I don’t have many) are now showing up as ANONYMOUS; their names and avatars used to appear. I have not changed my settings in Discussion.
By searching my comments and filtering by IP address, I know these commenters are not new to me, though it shows them as having “O approved” comments. I’ve been able to edit the comments and add in their identification, but would like to fix this.
Can you please assist? Thank you!
]]>I’m trying to implement the Peer to Peer plugin.
The payment gateway is supported and working fine. But if I select Anonymous donor, still their name comes up in the donor wall of the P2P page.
When fetching donor wall thru the short code on any other page, then the Anonymous donations are marked as anonymous.
]]>Recently our event submission page stopped working, and a message like “Unauthorized Access – you don’t have permission to access this form” appeared instead of the shortcode [event_form]. We had “Allow anonymous event submissions?” set to YES. I created an Anonymous subscriber user with permissions to edit events, but that didn’t work.
The only thing that worked was changing “Allow anonymous event submissions?” to NO – the opposite of what it should be.
Is this a bug?
]]>Settings for name are like that:
Ask* Require* Show* all ON