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

subrato_kha
subrato_kha
Online

Badges

Badges
22

Accepted Solutions

Accepted Solutions
3

Likes Received

Likes Received
20

Posts

Posts
59

Discussions

Discussions
25

Questions

Questions
34

Ideas

Ideas
0

Blog Posts

Blog Posts
1
Top badges earned by subrato_kha
Customize the badges you want to showcase on your profile
Re: AEM translations issues - Adobe Experience Manager 09-04-2020
i have removed the properties from translation_rules.xml but still they are getting updated in the component. We want different content in the component in language version. For Example : English will have different version and Chinese will have different version.

Views

2.9K

Likes

0

Replies

0
AEM upgrade from 6.3 to 6.5 issue - Adobe Experience Manager 07-04-2020
Hi All, We are trying to upgrade from AEM 6.3 to 6.5. After the upgrade we noticed that gigya cloud configuration stopped working causing error in the jsp of gigya. On further investigation we found out that com.day.crx.security.token.impl.impl.TokenAuthenticationHandler in OSGI have Enable encapsulated token support checkbox. Once we disable it , Gigya starts working and keeping it enabled causing gigya to fail. This work in 6.3 and we never faced issue. On further findings I found that once I ...

Views

3.4K

Likes

0

Replies

3
AEM translations issues - Adobe Experience Manager 07-04-2020
Hi All, We have a requirement that we don't want to translate/update translated content on a component in language copies. We have in the past send the english page(containing the component) for translations and now want to keep separate content in language copies. But when ever we send the english page for translations it updates the language copy. I have removed the property from translation_rules.xml file still facing the same issue. @kautuk_sahni

Views

2.9K

Likes

0

Replies

2
Re: AEM 6.3.3 - Adobe Experience Manager 29-11-2019
I am using AEM core components text component. I am on AEM 6.3.3 with CFP 6. I am using static templates.For me there is no root query param. Is there a way to configure the root path for RTE?

Views

5.1K

Likes

0

Replies

0
AEM 6.3.3 - Adobe Experience Manager 29-11-2019
Hi All,I am facing one issue with RTE component. My AEM version is 6.3.3.when i am trying to create a hyperlink it starts the view from Root and not from /content.is there any way we can configure the path so that it starts from /content

Views

5.3K

Likes

0

Replies

2
Re: org.eclipse.jetty.io.EofException in AEM 6.3.3.5 - Adobe Experience Manager 10-10-2019
what should be the ideal configuration? I have not done any customisation

Views

5.7K

Like

1

Replies

0
Re: [New] Welcome to AEM Community! Please Introduce Yourself - Adobe Experience Manager 03-09-2019
Hi All,This is Subrato, I am an AEM developer working with AEM from 6+ years.Glad to be part of this communityThanks,Subrato

Views

27.9K

Likes

2
org.eclipse.jetty.io.EofException in AEM 6.3.3.5 - Adobe Experience Manager 28-08-2019
Hi All,I am getting below error after installing Cumulative Fix Pack 6.3.3.5 . Has any one faced this issue please help.org.apache.sling.engine.impl.DefaultErrorHandler Error handler failed:java.io.IOExceptionjava.io.IOException: Error handler failed: org.apache.sling.api.scripting.ScriptEvaluationException at org.apache.sling.servlets.resolver.internal.SlingServletResolver.handleError(SlingServletResolver.java:800) at org.apache.sling.servlets.resolver.internal.SlingServletResolver.handleError(...

Views

5.9K

Likes

0

Replies

2
Pathfield component sorts the pages in view - Adobe Experience Manager 26-08-2019
Hi All,We have an issue that when we use pathfield component the pages/folders are sorted alphabetically by default. We want the view to be identical to sites.html view so that it's easy for content authors to use.for example: sites.html viewpathfield view : As you can notice that About us page is moved to top because it is sorted. We don't want this behaviour or how to control this behaviour. please suggest some solution

Views

1.0K

Likes

0

Replies

1
Re: Rollout config with property cq:trigger not working as expected - Adobe Experience Manager 17-07-2019
removing this property will not trigger rollout

Views

1.9K

Likes

0

Replies

0