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: Vanity URL working inconsistently - Adobe Experience Manager 17-08-2020
request is reaching publisher

Views

402

Likes

0

Replies

0
Re: Vanity url is not working with dispatcher in AEM 6.4 - Adobe Experience Manager 17-08-2020
@Anderson_Hamer : We are also facing the same issue. What changes you have done in apache config which fixed the issue

Views

2.0K

Likes

0

Replies

0
Re: thanks for the reply. but how do I put address object in... - Adobe Experience Manager 26-07-2020
Hi @Venkatasainath ,you can paas the latitude and longitude value using servlet to a backend service. Backend service will use any api like google reverse geocoding to give you address object in your format. You can persist the address in contexthub localstorage which will resolve your segment. You can also check if reverse geocoding is available in any web sdk then backend is not needed. It will be faster.

Views

480

Likes

0

Replies

0
Re: ContextHub doesn't show location value as part of CentextHubPersistence Local storage in publisher - Adobe Experience Manager 26-07-2020
hey @Venkatasainath : Reverse geocoding is no more available OOTB feature in AEM. Only available in author for demo purpose with limit to number of requests.You need to use any reverse geocoding api service to get the location for eg:-google api from the latitude and longitude to locate the address.

Views

497

Likes

0

Replies

2
Re: Unable to edit any components - Adobe Experience Manager 27-05-2020
@samr99530769 : were you able to fix this issue. We are also experiencing the same issue after inplace upgrade from 6.3 to 6.5

Views

11.6K

Like

1

Replies

0
Unable to edit components once targeting is enabled - Adobe Experience Manager 22-05-2020
Hi All,We are using contexthub on our website. We are experiencing issue, after the component is edited in target mode. We are unable to edit the targeted component in edit mode. Edit behaviour is only available in target mode. Is this expected behaviour?unable to edit component in edit mode after targetting@kautuk_sahni

Views

3.5K

Like

1

Replies

3
Re: Issue with context hub in AEM 6.5 - Adobe Experience Manager 12-05-2020
adding read permission to the contexthub-conf-reader user didn't helped

Views

3.8K

Likes

0

Replies

0
Issue with context hub in AEM 6.5 - Adobe Experience Manager 11-05-2020
Hi All,I am trying to use content hub for my website. The context hub throws below error while loading the page in the debugger console and causing issues.contexthub:473 Store "granite.emulators" ( ƒ (b,a){this.config=g.extend(!0,{},l,a);a=this.getSupportedEmulators();g.extend(!0,this.config,{initialValues:{devices:a,currentDeviceId:a[0].id,orientations:[{id:"landscape",title:"Landscape"},{id:"p… ) could not be initialized: TypeError: Cannot read property '3' of nullat contexthub:420at Array.map...

Views

3.9K

Likes

0

Replies

2
Re: AEM upgrade from 6.3 to 6.5 issue - Adobe Experience Manager 16-04-2020
the issue is fixed. got an updated package of gigya on request which supports encapsulated token

Views

3.3K

Likes

0

Replies

0
Re: AEM upgrade from 6.3 to 6.5 issue - Adobe Experience Manager 16-04-2020
issue solved

Views

3.3K

Likes

0

Replies

0