Change in "Comments" component between 5.6.1 and 6.1 | Community
Skip to main content
anilkum
anilkum
New Participant
March 25, 2016
Solved

Change in "Comments" component between 5.6.1 and 6.1

  • March 25, 2016
  • 3 replies
  • 924 views

Hi,

We have a requirement where we need to allow user to post comments without being logged in.

We have seen that this was possible in 5.6.1 where user could enter his comment, name, email , website (optional).

However 6.1 requires that the user be logged in to post comments.

I have seen this link - https://docs.adobe.com/docs/en/aem/6-1/release-notes/deprecated-removed-features.html - which gives the list of deprecated and removed features but I am not able to see this mentioned.

Any pointers on what is out of the box in 6.1 so that we can get back to the client.

Regards,

Anil

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by JK_Kendall

Hi Anil,

Use of AEM Communities features requires an additional license.

These are questions to ask your account representative.  

Depending on your deployment, JSRP may well be suitable.

- JK

3 replies

JK_Kendall
JK_KendallAccepted solution
New Participant
March 26, 2016

Hi Anil,

Use of AEM Communities features requires an additional license.

These are questions to ask your account representative.  

Depending on your deployment, JSRP may well be suitable.

- JK

anilkum
anilkumAuthor
New Participant
March 26, 2016

Thanks JK for you quick reply and conformation. But I am not sure if only extending the 6.1 comments component would be the only thing needed... The documentation talks about need for SRP. And this link also talks not using JSRP in production (https://docs.adobe.com/docs/en/aem/6-1/deploy/communities/topologies.html) . Is ASRP the only option for clients who dont have MongoDB? Does it involve licensing cost?

Thanks again for your help.

Regards,

Anil

JK_Kendall
JK_Kendall
New Participant
March 25, 2016

You're right, the change in behavior for communities features was not well documented.   But it is felt that the benefit of user generated comments is greatly enhanced by requiring site visitors to register and sign in before posting.  It also helps address the issue of spam, though not completely.

In AEM 6.1, it is not possible to ignore the login requirement as there are explicit checks on the server side in SCF that will reject anonymous comment attempts.

Using a “guest user” session that is always logged in and accepting “extra” parameters like “name” and “email” is a potential work around. 

I don't know of an example specific to 6.1, though.

- JK

Terms & ConditionsAccessibility statement

Loading footer...