8000 Comments for registered users · Issue #549 · getk2/k2 · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Comments for registered users #549

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
jameswadsworth opened this issue Feb 17, 2022 · 3 comments
Open

Comments for registered users #549

jameswadsworth opened this issue Feb 17, 2022 · 3 comments

Comments

@jameswadsworth
Copy link
jameswadsworth commented Feb 17, 2022 •
edited
Loading

We have been testing where in the comments settings comments are set to "Enabled for everyone". We have found a behaviour that we believe is inconsistent. If a user is already registered with the website, they are unable to leave a message, without logging in, and they receive a message "The Name or Email Address you typed is already in use!" Instead an unregistered user can leave a message without any problem. Worse if a person has a common name like James Smith, or Ali Mohamed if a person has registered with the same name they are unable to leave a comment. The check on the name is superfluous for leaving a comment when "Enabled for everyone"

Surely it would be better that both registered and unregistered users can leave comments in exactly the same way, without the registered user having a take extra steps of logging in and losing the comment they have left.
@fevangelou
Copy link
Member

The behaviour is correct and has worked just fine for a long time.

And it's all about content attribution and user protection. Imagine if some user posted a comment on behalf of someone else, using their email address. Sure, we could do user verification by email but this complicates things further.

If you want anyone to comment, I would recommend something like Disqus or Facebook comments. They are dead simple to integrate either way, exclusively in your K2 template overrides.

However, if you're building a community of users, it's not unheard of to require a user to be logged in to post comments. And if you improve the message users see from "The Name or Email Address you typed is already in use!" to something like "The Name or Email Address you typed is already in use! If you're a member of the site, please log in here...", I believe it'll be plain and clear to anyone using your comments setup.

@jameswadsworth
Copy link
Author

Ok I understand your point about the check on the email address to avoid a guest posting comments as user who has already registered.

However it does not seem necessary that the commenter has a unique name. Can the check of the name be disabled?

@fevangelou
Copy link
Member

For which ones? Registered or guests? I lost you...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fevangelou @jameswadsworth
0