Communities Comments Component Edit/Delete displayed for all users

Avatar

Avatar

snbaem

Avatar

snbaem

snbaem

05-01-2017

Hello All,

I

I have been looking into the social communities comments component that is available OOTB and learning its behavior as I comment as different users. 

When I comment as user1 (with no moderation or admin rights) and then login as user2 (with no moderation or admin rights), user2 seems to have ability to Edit, Delete the user1's comment.

I tried making few more comments and it is consistent. I just want to check if someone can tell if this is intended behavior? (i.e any user with minimum priviliges being able to edit or delete any ones comment)

If not - Is there any hotfix package I might be missing?

 

II

On sides I have been trying to use extended comments component as well. Another thing I noticed is, if I drag and drop the communities comment component the 'comments' node in the jcr will have the default properties available. But if I include the same in my page template JSP, the properties are not shown unless I go to the author instance open the component dialog and click 'Ok'. So basically if I extend the comments component and want the allow replies property to be true as default, its not picked up directly on page load but I need to go to each page based on the template where the component is included and open dialog and press 'Ok' (I could see the Allow Reply check box as true, but just not set in jcr node when included useing cq:include tag in template JSP)

 

Please share your thoughts or any suggestions on the above mentioned issues..

Thanks & Regards..

 

Update:

Sorry to not mention the version I tried this on. I have used AEM 6.2 and have also installed "cq-socialcommunities-pkg-1.10.111.zip"

View Entire Topic

Avatar

Avatar

snbaem

Avatar

snbaem

snbaem

06-11-2019

We didn't face any issue while creating calendar event I think. From what I remember, once a user becomes a member the "write" access is provided to the group that gets created for the community. As Arun has mentioned above, this will have to do with user privileges, please check around that.

For the given user try to see what rights they have for nodes a and under "/content/project/en/communities/communityA" for example.