Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

Core Teaser Component | AEM Cloud | Displaying dynamic media url

Avatar

Community Advisor

Hi Team,

We have not enabled Dynamic Media and using the Teaser Core component (core/wcm/components/teaser/v2), but getting the dynamic media url for that component. attaching the snapshot for the <img src=..> tag.

Shailesh_Bassi__0-1680718849372.png

The teaser refers to core/wcm/components/image/v3/image/cq:dialog/content/items/tabs/items/asset which further has the design dialog property (enableDmFeatures)

Shailesh_Bassi__1-1680718958840.png

I checked the property value and it is also not set to true, but still it is rendering the dynamic media url.

 

Any pointers will be helpful.

 

Thanks

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @Shailesh_Bassi_ I once faced this issue and found the root cause. When the project was created by default using arctype i found that by default their is a dynamic media configration file got generated in ui.config and after every deployment it got enabled. 

 

Please check for any dynamic media configuration in your default code. 

 

Or else check if their is any cloud service configured on the root pages

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

Hi @Shailesh_Bassi_ I once faced this issue and found the root cause. When the project was created by default using arctype i found that by default their is a dynamic media configration file got generated in ui.config and after every deployment it got enabled. 

 

Please check for any dynamic media configuration in your default code. 

 

Or else check if their is any cloud service configured on the root pages

Avatar

Community Advisor

Hi @Jagadeesh_Prakash I have explicitly set the property "enableDynamicMedia" as "n", while executing the maven archtype.

The same archetype is actually executing the correct response in the form of the img tag in the higher environment, it is just one of the lower environment on which this issue is reproducible.

I have checked all the config files as well and the associated properties, but there is none. 

Please let me know if there is anything which could be a possible reason for this?

 

Thanks.