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

Rohitash_Singh_
Rohitash_Singh_
Offline

Badges

Badges
4

Accepted Solutions

Accepted Solutions
0

Likes

Likes
1

Posts

Posts
4

Discussions

Discussions
1

Questions

Questions
3

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by Rohitash_Singh_
Customize the badges you want to showcase on your profile
Re: After Inplace upgrade of AEM from 6.3 to 6.5, Components are in a satisfied state
Avatar
Ignite 1
Employee
sunjot16
Employee

Likes

107 likes

Total Posts

164 posts

Correct reply

50 solutions
Top badges earned
Ignite 1
Give Back 100
Give Back 50
Give Back 5
Give Back 3
View profile
sunjot16
- Adobe Experience Manager
In addition to JaideepBrar​ 's updates, if your components are using coralui 2, you should migrate your components to coralui 3.The following document maybe helpful:Legacy CoralUI 2 Components — Granite UI 1.0 documentation There were some deprecated & removed features, which you can find here:Deprecated and Removed Features - AEM 6.3Deprecated and Removed Features - AEM 6.4Deprecated and Removed Features - AEM 6.5

Views

3.5K

Likes

0

Replies

0
Re: On AEM 6.0+SP3 updated my pom with aem-api 6.0.0-SP3 and facing below issue, anyone faced this before?
Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,401 likes

Total Posts

3,347 posts

Correct reply

1,137 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile
Jörg_Hoh
- Adobe Experience Manager
Well, even though Geometrixx might work, it's not supported; probably there is a reason for that 🙂In your case you are building your custom code, maybe that's problematic?

Views

679

Likes

0

Replies

0
Likes from