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

santhoshsrg
santhoshsrg
Offline

Badges

Badges
18

Accepted Solutions

Accepted Solutions
2

Likes Received

Likes Received
28

Posts

Posts
63

Discussions

Discussions
9

Questions

Questions
54

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by santhoshsrg
Customize the badges you want to showcase on your profile
Re: AEM Cloud Inbox page Issue - Adobe Experience Manager 07-03-2022
We are also using AEM Cloud and have experienced no such issue, so I'm guessing this is not global.Can you check if you have made any overlays or customization to the AEM Inbox?

Views

264

Like

1

Replies

0
Re: Website Structure in AEM — Multi-Site Manager(MSM) | AEM Community Blog Seeding - Adobe Experience Manager 01-03-2022
Hi, I need guidance regarding Preview instance. In my project, we are following multi-tenant architecture. We have two sites - site1, site2. I am trying to move a site2 page to preview instance, the page is moving properly to site2 and is available in following URL https://preview.site2.com/content/site2/home/test.html, but in Preview Dialog (at the end of Manage Publication flow), preview URL is displayed incorrect, the preview URL is displayed with site1 domain like https://preview.site1.com/c...

Views

232

Likes

0

Replies

0
Re: AEM Page Editor error : Handler of component is invalid -> TypeError: Cannot read property 'flow' of undefined - Adobe Experience Manager 21-12-2021
Hi All To anyone who will face this issue in the future, please find below the details how this was fixed in my local. Root Cause : If you click on the last line where the error is occurring from the error trace , it will take you to a JS in the libs. Please check the below screenshots Click on Pretty Print and it will highlight the error lines If you hover on the clientlibs it will give you the path of the clientlibrary , which is at /libs/cq/gui/components/authoring/editors/clientlibs/core . I...

Views

2.7K

Likes

2

Replies

0
Re: Image - Lazy loading is not working in mobile screen - Adobe Experience Manager 12-10-2021
Thanks for your input! 🙂

Views

318

Like

1

Replies

0
Re: RTE Plugin source edit is not working for nested multifield - Adobe Experience Manager 06-10-2021
@santhoshsrg I think this should work.Please check the dialog structure properly. there might be issue with dialog structure. Are you using nested multifield(multifield inside multifield > richtext) right?? Thank You.

Views

261

Like

1

Replies

0
Re: RTE - Default Typography and Text Color - Adobe Experience Manager 06-04-2021
@santhoshsrg add externalStyleSheets property to RTE node and give css file path as value. Write css targeting cq-dialog class. Ex: .cq-dialog .coral-RichText-editable * { color: red; }

Views

260

Likes

2

Replies

0
Re: JcrPackageManager.listPackages(WorkspaceFilter) retur... - Adobe Experience Manager 21-08-2020
What values are you using for PAGE1_PATH, PAGE2_PATH

Views

357

Like

1

Replies

0
Re: Junit test case - Creating packages - Adobe Experience Manager 25-06-2020
Hi, I would like to help you but reproducing the error locally is going to be very time-consuming. Could you provide a Java class and test that emulate this issue that I can just copy-paste?

Views

554

Likes

0

Replies

0
Re: Packaging Junit - Adobe Experience Manager 22-06-2020
In the example https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/master/bundle/src/test/java/com/adobe/acs/commons/packaging/impl/AssetPackagerServletImplTest.java, they have used jcrPackageManager.create(groupName, name, version) which is also working for me. But methods mentioned below are not working. These are throwing exceptions in "org.apache.jackrabbit" classes. Methods not working:jcrPackageManager.create(rootNode, pkgName)jcrPackageManager.assemble(jcrPackage, listener)

Views

755

Likes

0

Replies

0
Re: Package is not getting completely generated - Adobe Experience Manager 11-06-2020
Hi santhoshsrg, You are trying to build the workflow which is still in running state. So you will not be able to get the complete package. All the workflow steps processed after the package was created will not be included as workflow is still in RUNNING state and transition nodes are still getting added under "history" for the respective workflow instance. For building up the entire workflow the process of creating the workflow should be executed once the entire workflow is completed. You can h...

Views

720

Likes

0

Replies

0