Open nicoodakp opened 6 years ago
Hi @nicoodakp,
Yes... such a behavior is intentional. The code doesn't allow like/dislike, nor flagging, for non-registered users. Those actions use the CommentFlag
model from django-contrib-comments, which require a user.
To allow non-registered users flag and like/dislike comments you would need a new model to either register the user (in case the flagging comes from a registered user) or register the email address. You would also need to send an email to the user to confirm that she's flagging/liking/disliking the comment. At the time of showing the list of users who liked/disliked a comment, would you show the username, email address or complete name?
As a user I don't see myself confirming these operations by email. I think that might as well be the reason behind the decision to require a user in the original django-comments framework. If I put myself in the position of giving my email address to confirm a simple like/dislike operation I would suspect that the final intention of the website is to collect email addresses.
Thanks for your positive feedback! :)
thanks for the note, if I were only want to allow non-register customer to like/dislike, but only once for each ip address. what would be the best approach to this ? A new model ? a social-auth package ? or something else ? thanks
One proxy puts many users behind a single IP. Sorry, that's not a good solution.
Hi its me again,
I try to utilized the package with the like/dislike and flagging, I follow the comp example and doc to set up the setting.py and urls.py. but the liked and flagging only allow for authenticated user. (non-authenticated user redirect to my account/login page...)
If i were only using template tag the 'like' returns
'The current path, accounts/login/, didn't match any of these.'
I try to comment with a secondary email and then click liked, still have no luck. again the package is awesome, thanks a lot
urls.py
settings.py """