Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

premchandr61956
premchandr61956
Offline

Badges

Badges
13

Accepted Solutions

Accepted Solutions
2

Likes

Likes
17

Posts

Posts
25

Discussions

Discussions
16

Questions

Questions
9

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by premchandr61956
Customize the badges you want to showcase on your profile
Re: How to create node for directly included resources in component html via data-sly-resource? - Adobe Experience Manager 15-06-2018
himanshusinghal​ Did you get any fix for this issue?

Views

2.4K

Likes

0

Replies

1
Re: AEM 6.2 required richtext (RTE) on page creation - cannot enter data - Adobe Experience Manager 22-05-2018
Facing the same issue in AEM 6.4 as well any solution for this issue?

Views

1.8K

Likes

0

Replies

0
HtmlLibraryManager cannot be resolved to a type - Adobe Experience Manager 30-03-2018
We have custom implementation to find the pages / assets which do not have jcr:content. It was working fine AEM 6.0 version but we are migrating to AEM 6,3 now and we are facing the below error when we open the pageError during include of component '/apps/misc-tools/components/missingNode'Error Message:org.apache.sling.api.scripting.ScriptEvaluationException: org.apache.sling.scripting.jsp.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 20 in the generated jav...

Views

3.9K

Likes

2

Replies

4
Re: @ format in sightly working differently in AEM 6.1 and AEM 6.3 - Adobe Experience Manager 11-01-2018
When I cheked with one of my collegue who is also using AEM 6.3 CFP2 he doesn't see index value added at the end of node name. My instance is AEM 6.3 SP1 CFP1.

Views

3.2K

Likes

0

Replies

1
Re: @ format in sightly working differently in AEM 6.1 and AEM 6.3 - Adobe Experience Manager 11-01-2018
We are using the above line of code to add an index dynamically to the names for tabs, for example, written_by0, written_by1, and written_by2 in order to avoid duplication of the same node and so on. This did not work in our 6.1 environments so we just had dialog validation restricting authors to avoid duplication but then we did not remove this code to append "@ format= {itemList.index}" for the node name.But when compared to 6.3 we are not able to fetch content from the node written-by because...

Views

3.2K

Likes

0

Replies

2
Re: @ format in sightly working differently in AEM 6.1 and AEM 6.3 - Adobe Experience Manager 11-01-2018
Yes the above code doesn't add index values to node in 6.3 but nor in 6.1

Views

3.2K

Likes

0

Replies

4
@ format in sightly working differently in AEM 6.1 and AEM 6.3 - Adobe Experience Manager 11-01-2018
Hi,We have a component where for creating multiple tabs on the page which has code snippet as below.The "tab.token" will be a value that we give in the component dialog as tab name, for example, tab1 and tab2. The above code appends an index 0,1 and so on for each node created in AEM 6.3 but doesn't add the index in AEM 6.1.This issue is reproducible in AEM 6.3 SP1 CFP1.Thanks,Prem

Views

5.0K

Likes

0

Replies

8
Re: Issues with AEM 6.3 SP1 Upgrade - Adobe Experience Manager 23-11-2017
Hey Kiran,We also have installed SP1 in our AEM 6.3 instance and not facing any issue accessing the URL: <>/mnt/overlay/dam/gui/content/assetsrouter.html it redirects to this URL:<>/assets.html/content/dam.Try it on a fresh instance and if its reproducible.Thanks,Prem

Views

2.3K

Likes

0

Replies

0
Re: Error when attempting to delete a "launch" in 6.3 - Adobe Experience Manager 23-11-2017
Can you add the screenshot of complete node structure of the launch you are trying to delete?

Views

865

Likes

0

Replies

0
Re: Error while replicating few pages in AEM 6.3 - Adobe Experience Manager 03-11-2017
Yes, I raised a support ticket. This is acknowledged as product bug and fix is included in AEM 6.3 SP1 CFP1 which might release in late November.Adobe provided a workaround for this :- Go to http://host:port/system/console/components- Look for com.adobe.granite.comments.internal.CommentReplicationContentFilterFactory- Click on StopThis resolved our issue.

Views

4.5K

Likes

6

Replies

2