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

Magicr
Magicr
Offline

Badges

Badges
19

Accepted Solutions

Accepted Solutions
4

Likes

Likes
28

Posts

Posts
67

Discussions

Discussions
6

Questions

Questions
61

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by Magicr
Customize the badges you want to showcase on your profile
Re: Granite component looks differently since AEM 6.3 - Adobe Experience Manager 17-05-2022
I could find the problem and a solution for it. A simple display:inline solves the problem. My question: what is the name of catogory of clientlibs so the gui for page properties accept this? By the way: the "cosmetical problem" occurs also in we-retail project, so it is a general bug.

Views

4

Likes

0

Replies

1
Re: Granite component looks differently since AEM 6.3 - Adobe Experience Manager 12-05-2022
How can I achive that, that my own css will be applied to page properties dialog?

Views

51

Likes

0

Replies

3
Betreff: Getting error for some user After adding my user component - Adobe Experience Manager 12-05-2022
Delete and recreate them. Also check the respository for hidden general failuers. Some errors on filesystem could run into respository errors.

Views

56

Likes

0

Replies

0
Re: Granite component looks differently since AEM 6.3 - Adobe Experience Manager 12-05-2022
As I wrote "since AEM 6.3" this issue exists in AEM 6.4 und 6.5 either. And it is a little bit annoying.

Views

74

Likes

0

Replies

0
Granite component looks differently since AEM 6.3 - Adobe Experience Manager 12-05-2022
In my projects I used often the component granite/ui/components/coral/foundation/form/selectSince AEM 6.3 there is an issue that this granite component looks differently when you include it into a dialog for page properties and in dialog for a component. Here the look in page properties: (This is not the expected look) And here the look in component dialog. (This is the expected look)How can I fix it in general? If is it a general bug will it fixed by Adobe? Thanks in advanced.

Views

116

Likes

0

Replies

6
Betreff: Getting error for some user After adding my user component - Adobe Experience Manager 12-05-2022
When the error message for only a couple of users occurs, then you have to check the existing user objects with some users which are working. May be there same properties are missing or the user object is corrupt in repository. You can export the user by creating a package. Use a program that can compare textfiles (I.e. Beoynd compare).

Views

106

Likes

2

Replies

2
Re: Custom validation for dialog fields. - Adobe Experience Manager 11-05-2022
I get a "Page not found" message. The ".html" is missing in posted link.

Views

82

Like

1

Replies

2
Betreff: Getting error for some user After adding my user component - Adobe Experience Manager 11-05-2022
The most likley reason is this is that an included model class returns a Null value. So go to html file from your component and look for: =""/>Then start the debugger in your IDE and find out why the including class returns Null.

Views

214

Like

1

Replies

4
Betreff: JCR SQL2 Query or Query builder predicate - Adobe Experience Manager 09-05-2022
I don't understand what your requirements exactly are. As far as I understand your prictures -whose shows your structure- the marked tags are a part of full path from others. So there is no other way. May be the keyword 'contains' allows you to avoid der percent signs. My above query would looks like:SELECT * FROM [dam:AssetContent] AS page WHERE ISDESCENDANTNODE(page ,"/search/in/path") AND NOT (Contains(page.[cq:tags], 'dsc:keywords') or Contains(page.[cq:tags], 'dsc:device')) The query builde...

Views

44

Like

1

Replies

0
Betreff: JCR SQL2 Query or Query builder predicate - Adobe Experience Manager 06-05-2022
SELECT * FROM [cq:PageContent] AS page WHERE ISDESCENDANTNODE(page ,"/search/in/path") AND NOT (page.[cq:tags] like "dsc:keywords%" or page.[cq:tags] like "dsc:device%") Due to the fact that the information is saved in jcr:content node, you have to work with this resource.

Views

92

Like

1

Replies

2