commentsystem is not have setPath | Community
Skip to main content
C
chandra_cq5
New Participant
October 16, 2015
Solved

commentsystem is not have setPath

  • October 16, 2015
  • 4 replies
  • 988 views

It is about customization for the blog comments .

So the comments.jsp from the path "/libs/collab/commons/components/comments/comments.jsp" from crxde was copied to eclipse  to "/apps/collab/commons/components/comments/comments.jsp".

It is throwing an error for the method setPath() .

In the pom.xml of the project I have already included the dependencies .

<dependency>

                                                <groupId>com.day.cq.collab</groupId>

                                                <artifactId>cq-collab-commons</artifactId>

                                                <version>5.5.2</version>

                                    </dependency>

                                    <dependency>

                                                <groupId>com.day.cq.collab</groupId>

                                                <artifactId>cq-collab-blog</artifactId>

                                                <version>5.5.2</version>

                                    </dependency>

                                    <dependency>

                                                <groupId>com.day.cq.collab</groupId>

                                                <artifactId>cq-collab-core</artifactId>

                                                <version>5.5.0</version>

                                    </dependency>

 

Please let me know if I have missed out anything 

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 smacdonald2008

I heard back from the Eng team about this. This is their advice:

If you're using CQ 5.5, you should consider upgrading to AEM 6.0, which better supports extensibility.

For AEM 6.0 communities client side customization, there is a tutorial :

  http://docs.adobe.com/docs/en/aem/6-0/develop/social-communities/tutorials/extend-comments.html

For AEM 6.0 communities server side customization, there is a github sample :

   https://github.com/Adobe-Marketing-Cloud/aem-scf-sample-components-customize

If you continue with CQ 5.5, then more information is needed, including the error log message.

4 replies

smacdonald2008
smacdonald2008
New Participant
October 16, 2015

What version of CQ are you using? 

smacdonald2008
smacdonald2008Accepted solution
New Participant
October 16, 2015

I heard back from the Eng team about this. This is their advice:

If you're using CQ 5.5, you should consider upgrading to AEM 6.0, which better supports extensibility.

For AEM 6.0 communities client side customization, there is a tutorial :

  http://docs.adobe.com/docs/en/aem/6-0/develop/social-communities/tutorials/extend-comments.html

For AEM 6.0 communities server side customization, there is a github sample :

   https://github.com/Adobe-Marketing-Cloud/aem-scf-sample-components-customize

If you continue with CQ 5.5, then more information is needed, including the error log message.

C
chandra_cq5Author
New Participant
October 16, 2015

Thanks for the input.

we are using CQ 5.6.1 and will not upgrading as off now.

The error that i see will building in ecllipse. Please let me know I could solve it

[ERROR] Failed to execute goal org.apache.sling:maven-jspc-plugin:2.0.4-incubator:jspc (compile-jsp) on project connect-app: Unable to compile class for JSP:
[ERROR] 
[ERROR] An error occurred at line: 63 in the jsp file: /apps/collab/commons/components/comments/comments.jsp
[ERROR] The method setPath(String) is undefined for the type CommentSystem
[ERROR] 60:
[ERROR] 61:     if(isRenderByForm ){
[ERROR] 62:
[ERROR] 63:         cs.setPath(CollabUtil.getPagePath(editComment));
[ERROR] 64:         request.setAttribute("isRenderByForm", isRenderByForm);
[ERROR] 65:         request.setAttribute("commentsRoot", childComment.getPath());
[ERROR] 66:     }

C
chandra_cq5Author
New Participant
October 16, 2015

added the same  versions from felix console the problem was solved. Thanks for looking into this.

Terms & ConditionsAccessibility statement

Loading footer...