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

Pavan_kalyan
Pavan_kalyan
Online

Badges

Badges
19

Accepted Solutions

Accepted Solutions
7

Likes Received

Likes Received
38

Posts

Posts
31

Discussions

Discussions
6

Questions

Questions
26

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by Pavan_kalyan
Customize the badges you want to showcase on your profile
Re: Workflow migration for 6.5 upgrade - Adobe Experience Manager 24-01-2022
Hi @Alisahali Thanks for sharing the answer.I was away for a while and haven't been on this blog so replying late.

Views

300

Like

1

Replies

1
Re: how to configure npm run live to test the styling for ame - Adobe Experience Manager 22-12-2021
Thank you @arunpatidar 

Views

127

Like

1

Replies

0
how to configure npm run live to test the styling for ame - Adobe Experience Manager 21-12-2021
I am working on a project which have frontend as react.I want to test the styling for that components by running it live and see the changes as I change them.I have see a video on not aware how to add that to my project.thanks in advance.

Views

137

Likes

0

Replies

2
Re: SDK local instance - Restart - Error 503 authentication - Adobe Experience Manager 16-12-2021
do you see any error message in your error.logs file.? (located in quickstart/logs/error.logs file),this might give us the reason for this issue.!if not just delete your quickstart and do a fresh install

Views

7.5K

Like

1

Replies

2
Re: SDK local instance - Restart - Error 503 authentication - Adobe Experience Manager 16-12-2021
Hi @ana_belen_cano_ The 503 error Basically Indicates sling not able to connect to repository. It may be corruption Or last install broke it.try these stepstry accessing your crx/de if that redirection works login there check if any package is showing an errorgo to your system/console/bundles and see if all your bundles are in active state.if you don't find any issues anywhere there must be a mismatch in the versions you are using (eg: using java 11 for aem 6.4) .if your a backup of your project...

Views

7.5K

Likes

3

Replies

4
Re: json exporter - Filter allowed components aem 6.5 - Adobe Experience Manager 16-12-2021
AEM Tutorial #19 | Jackson exporter in AEM | Sling Model Exporter using Jackson Exporter in aem - YouTuberefer to this video you will see it in action.

Views

173

Like

1

Replies

0
Re: Manipulate string within the author dialog window - Adobe Experience Manager 16-12-2021
Hi @JAI_AEM you can add the .com using sling model in the getter method but it is only displayed in the component property. but you can't see the google+.com in your dialog. I remains the same (google) in your dialog.thanks.

Views

142

Like

1

Replies

0
Re: json exporter - Filter allowed components aem 6.5 - Adobe Experience Manager 16-12-2021
Hi @sathya_prakasha their is an annotation called @JsonIgnore which is used to hide the unwanted elements in your sling model.add this annotation to the elements which you don't want to expose.thanks.

Views

191

Likes

3

Replies

3
Re: Is Creative Cloud vulnerable to the Apache Log4j utility (CVE-2021-44228) zero-day exploit - Adobe Experience Manager 15-12-2021
If you want to know more about this log4j vulnerability here it is..!What is log4j Vulnerability.?The vulnerability is dubbed as Log4Shell and it is officially know as CVE-2021-44228 (CVE number is the unique number given to each vulnerability discovered across the world).what Log4j is used for.?Software developers use the Log4j framework to record user activity and the behavior of applications for subsequent review. Distributed free by the nonprofit Apache Software Foundation, Log4j has been do...

Views

1.2K

Like

1

Replies

0
Re: Is Creative Cloud vulnerable to the Apache Log4j utility (CVE-2021-44228) zero-day exploit - Adobe Experience Manager 15-12-2021
Hi @Bryski as per the information provided by our company, Adobe is working on it to fix the issue and even released a new (Replic APM) version to overcome the issue.I guess your organization is trying change the version of it and do a production build so that is the reason they are telling you to stop using it for sometime.while they fix the issue by updating the existing Log4j. and do a build for Stage, and Prod.kindly ignore if my answer doesn't sound valid.

Views

1.3K

Like

1

Replies

2