Just to give some context into what I've been looking at to solve the issue:I have been looking at the journal (blog) component as it has comments (well a comment component anyways), but the supertype of the Journal component's comment component is social/forum/components/hbs/post. The Journal's com...

We have some content pages that we have put a comments component at the bottom of (/libs/social/commons/components/hbs/comments). The commenting works great and is stored properly, but the comments are never added to the activity stream.  We'd like to leverage the comments component to allow comment...

One thing that is interesting is that I am seeing a reference to CommentUtil, but I don't see that documented in the 6.2 docs. I only see it in the 6.1 docs.

I tried following the documentation (link below) and have not been successful with our own app or with the We Retail app. Does anyone know how to actually set up ASRP with AEM 6.2? The documentation looks to be outdated based on some of the directions being slightly off (where to find the replicatio...

So, something like that could work for us. However, what happens is that the qnaforum-top will render inside the scf component. As an example, our qnaforum-top contains a column with filters that will change what is displayed in the qnaforum social component. If we were to move the qnaforum-top insi...

We are experimenting with making the authorizableId and principalName the "username" and keeping the e-mail on the profile. Then, we'd maybe need to create some kind of custom auth handler that will translate the e-mail address to a username and log in. We made a servlet that will do just that and u...

We currently have an issue with how the out of the box login and profile link work. Ideally, we'd like to log in with an e-mail address which is perfect because that is out of box. The problem is that we'd like the user profile URL to not contain the e-mail address like it does out of box. We'd also...

Sent you a PM. Thank you for checking that out for us!

So, qnaforum-top doesn't use anything from the QnA components. The reason we included it the way we did is we wanted the contents of qnaforum-top to not be included when a topic was being displayed. Anything in the QnA is replaced by the Topic contents if you click on a topic from the list. We could...

Here is an example of one of the components we have. We have a few different ones we are including, but this is the first one in our overlaid social component:qna-index (jcr:primaryType = cq:Page)    jcr:content (cq:template = /apps/foo/templates/qnaindex-template)        global-header (our header) ...