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
BedrockMission!

Learn More

View all

Sign in to view all badges

Ivo_Eersels
Community profile Ivo_Eersels Level 1
Job title here
Location here
3 BADGES
Level 1

Level 1

Learn more
Joined the community 15-04-2014 1:28:01 AM
Offline
Top badges earned by Ivo_Eersels
Customize the badges you want to showcase on your profile
I know years have passed, but for other people seeing thi...
Avatar
Give Back 5
Level 1
Ivo_Eersels
Level 1

Likes

0 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
View profile
Ivo_Eersels
- Adobe Experience Manager
I know years have passed, but for other people seeing this I will say this. In my experience the system properties have highest precedence for determining runmode. Somewhere above on this page I added a 'full test report' with all my test cases and their results to prove it. So according to my extensive testing the runmode precedence is actually like: system properties (-D) > sling.properties > -r option > JAR filename.So to me your observation is easily explained assuming you were talking about...

Views

5.2K

Likes

0

Replies

0
Re: order of precedence of Sling run modes
Avatar
Give Back 5
Level 1
Ivo_Eersels
Level 1

Likes

0 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
View profile
Ivo_Eersels
- Adobe Experience Manager
I am sorry, but it seems that this needs to be verified again by one of your sysadmins as I get the impression that incorrect information is being copied over and over, even in the documentation. It is still like this in https://docs.adobe.com/content/help/en/experience-manager-65/deploying/configuring/configure-runmodes.html#using-the-r-option I tested it on my local system and it clearly shows precedence is like this: system properties (-D) > sling.properties file > -r option > filename detect...

Views

5.2K

Likes

0

Replies

0
Re: [AEM Skill Builder | October] AEM Component Generator – Best Practice AEM Components in a Fraction of the Time
Avatar
Give Back 5
Level 1
Ivo_Eersels
Level 1

Likes

0 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
View profile
Ivo_Eersels
- Adobe Experience Manager
Unfortunately I can't attend at that date/time. Will a recording be made available for watching it later? And do you need to register anyway to be able to access it?

Views

5.3K

Likes

0

Replies

0
Re: Client Library Versioning in AEM 6.1
Avatar
Give Back 5
Level 1
Ivo_Eersels
Level 1

Likes

0 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
View profile
Ivo_Eersels
- Adobe Experience Manager
I stated in my post "in our project" so ofcourse there is no path in this configuration. The screenshots above are not related to my project and the url I posted points to your own running AEM instance?Furthermore I believe that the screenshots with the black rectangles is flawed in a sense that it also mentions content types text/javascript and text/css? In my understanding you want to rewrite links inside a text/html response which point to a clientlib. So I don't understand why you would need...

Views

5.3K

Likes

0

Replies

0
Re: Client Library Versioning in AEM 6.1
Avatar
Give Back 5
Level 1
Ivo_Eersels
Level 1

Likes

0 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
View profile
Ivo_Eersels
- Adobe Experience Manager
Sorry, no not at all. As you normally want this feature active in all runmodes (author and publish) this shouldn't be in a runmode specific folder in my opinion. Even if it was, I stated that it works and doesn't work with 2 urls patterns on AUTHOR.I think I fixed it though. In our project we had another rewriter configuration active next to the 'versioned-clientlibs' node. It had a 'Paths' property value of '/content/...' in it. So I figured, what if that one is overwriting the result of my ver...

Views

5.3K

Likes

0

Replies

2
Re: Client Library Versioning in AEM 6.1
Avatar
Give Back 5
Level 1
Ivo_Eersels
Level 1

Likes

0 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
View profile
Ivo_Eersels
- Adobe Experience Manager
HiI am on AEM 6.4 too. For me it is even stranger... I seems to work with a node of type nt:unstructured, but only on AUTHOR instance with a url which contains the /editor.html/ for triggering the authoring widgets in it. If I leave out the /editor.html, the md5 hashes disappear from all the clientlib references in the HTML markup.On PUBLISH the feature doesn't seem to be active either (due to not using editor.html in the url?)I have no idea why this is happening. Any hints?

Views

5.3K

Likes

0

Replies

4
Why does AEM ECommerce Hybris integration use Hybris 'guid' as orderId for anonymous orders
Avatar
Give Back 5
Level 1
Ivo_Eersels
Level 1

Likes

0 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
View profile
Ivo_Eersels
- Adobe Experience Manager
Hi guys,I am using AEM ECommerce Hybris integration version 6.3.2 (cq-commerce-hybris-impl-6.3.2.jar ) and Hybris version is 6.3.0.2.When I place an order with a logged in account, the order is created in Hybris and I see an order confirmation page with a nice order number likeThank YouYour order is being processedOrder number 00000008We are processing your order and an email confirmation has been sent to your email address. ...When I place an order without logging in (so as an anonymous custome...

Views

411

Likes

0

Replies

0
Clicking the 'Target' context menu option renders content components useless
Avatar
Give Back 5
Level 1
Ivo_Eersels
Level 1

Likes

0 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
View profile
Ivo_Eersels
- Adobe Experience Manager
HiWe are running AEM 6.0 SP1 and have developed custom components for a project. Now we noticed that if a content author right clicks a content component in Edit mode and selects 'Target' from the context menu, the component becomes inaccessible. When right-clicking it you only get the context menu from the webbrowser and the content component also is no longer hightlighted with the green squares around it to mark editable areas.Why is this happening? I could disable this 'Target' context menu o...

Views

442

Likes

0

Replies

0
Re: Removing the Target command from the context menu
Avatar
Give Back 5
Level 1
Ivo_Eersels
Level 1

Likes

0 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
View profile
Ivo_Eersels
- Adobe Experience Manager
I went with the solution mentioned by adamyocum Jun 20, 2013 12:37 PM. And overlayed /libs/cq/ui/widgets/source/widgets/wcm/EditBase.js. But I would like to know why clicking 'Target' messes up our components? Either we are doing something wrong or AEM has a setup problem which allows content author to mess up components (clicking Target, leaves you unable to right-click the component again to edit/correct it) Regards,Ivo

Views

302

Likes

0

Replies

0