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

Umesh_Thakur
Umesh_Thakur
Offline

Badges

Badges
32

Accepted Solutions

Accepted Solutions
69

Likes Received

Likes Received
228

Posts

Posts
225

Discussions

Discussions
25

Questions

Questions
200

Ideas

Ideas
0

Blog Posts

Blog Posts
2
Top badges earned by Umesh_Thakur
Customize the badges you want to showcase on your profile
Re: Using AEM as a Frontend with a REST API - Adobe Experience Manager 18-05-2020
One solution can work in your scenario:1. Use AEM only as CMS not for the frontend. From AEM side make API call to get the vary little data to be consumed by the server side and for the rest of the data, provide required information in the form of window object to frontend.2. Use React to make the API call based on the data provided by AEM to generate the look and fill of the frontend.Serverside call is expensive. You can use some middle ware like APIGEE accomplish your API security needs.

Views

2.5K

Like

1

Replies

0
Re: Getting 404 when try to add some fragment in the deployed package - Adobe Experience Manager 18-05-2020
There is a workaround for this mentioned on the below link:https://helpx.adobe.com/in/experience-manager/kb/URLs-with-encoded-slashes-do-not-work-in-AEM.html

Views

14.1K

Like

1

Replies

2
Suggestion: Content Structure for experience fragment. - Adobe Experience Manager 18-05-2020
Dear Members,We are introducing experience fragment for the first time in our project for that we have maintained the same site structure like:/content/experience-fragments/project-name/language-masters/en_us/……for language-masters and /content/experience-fragments/project-name/us/en_us/…… for live copies. But the problem with this approach is while crating a live copy of a pages from language-master, we are have a option to select the target but while creating live copy variation of the XF we d...

Views

2.4K

Likes

0

Replies

1
Re: Even after clearing the dispatcher cache query parame... - Adobe Experience Manager 06-05-2020
It was resolved.Issue was with the SDI, that we use for XF caching, when SDI was enable it was adding one CSS file in the page source for XF component so this CSS file was altering the page's look and fill but when I was using query parameter, it was skipping the SDI as well as dispatcher so getting the actual content as it was there on the publisher server. Thanks all for your suggestions on this topic.

Views

2.4K

Like

1

Replies

0
Re: Even after clearing the dispatcher cache query parame... - Adobe Experience Manager 05-05-2020
I am using chrome's incognito only. It is related to SDI(sling dynamic include) it seems.

Views

4.2K

Likes

0

Replies

0
Re: Even after clearing the dispatcher cache query parame... - Adobe Experience Manager 05-05-2020
I using chrome's incognito only.

Views

4.2K

Likes

0

Replies

0
Even after clearing the dispatcher cache query parameter is required to get the updated content from publisher. - Adobe Experience Manager 04-05-2020
Dear Members,I am facing one different kind of issue,After clearing the dispatcher cache multiple times, still query parameter is required to show the actual content from the publisher in incognito of the chrome browser\\. Some more point:1.There is some anomaly in the author and publisher content.2.I am using SDI to cache the experience fragment component on the page.3.Experience fragment is being used for header and footer. can anyone has faced such an issue ? Please suggest what should be don...

Views

6.4K

Likes

0

Replies

7
Getting 404 when try to add some fragment in the deployed package - Adobe Experience Manager 30-04-2020
Hi Members,I have created one package of experience fragment content and deployed it in another environment, when I try to create some more experience fragment in the deployed package in another environment, on click on the OPEN button after creation, it gives sometime 404 error. But when click on DONE button then open it for editing it works fine.If anyone can share some idea what may be causing the issue?Both of the environment is having AEM 6.4 with service pack 6.4.6.ThanksUmesh Thakur

Views

15.9K

Likes

0

Replies

8
Re: NO components in AEM 6.4 - Adobe Experience Manager 20-04-2020
Policy needs to be updated for that particular Template:Steps:1. click on Page Information( Mid option on the top left corner of the same page)2. select Edit Template3. on the template editor page click on the container layout box and select the policy icon.4. From the left box's first drop down select one existing policy and save it.5. else you can create a new one by writing name in the second box and select the component category from the right pan.6. save and re-fresh the page hope this will...

Views

2.7K

Like

1

Replies

0
Template Policy is not deploying with different naming convention - Adobe Experience Manager 20-04-2020
Hi Members,In my current project template policies are named like policy_ but I have created one template policy with different naming convention like in below image with RED underlined, when I deploy the code with -PautoInstallPackage maven profile it does not deploy that policy with different naming convention.So my question is that is there any place where I need to make this policy or naming convention enable to be picked up by Maven ? Looking for your kindly response.ThanksUmesh Thakur

Views

2.4K

Likes

0

Replies

2