Expand my Community achievements bar.

Learn about Edge Delivery Services in upcoming GEM session
SOLVED

Tech - Inherited Image on Tile when Page gets deactivated/not available

Avatar

Level 2

Hi Team,

 

We are following MSM structure for our global sites & while using OOTB tease inherit feature in image option we are facing this scenario. We only rollout the selective pages to other country sites based on BU requirement, so all the subpages will not be available in country sites, due to this the inherit image option will fail in country sites, since it cant find the respective page authored in link field on teaser component in the respective country site. The image will not load & we have to manually author the images in country site pages. So when it comes to multiple sites the manual effort is increasing.

We would like to understand, is there any idle way to manage this scenario, either via customising OOTB teaser component, or custom rollout configs or any other suggestions? 

 

Thank you.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @madhuyadawad 

I believe leveraging a custom rollout could be beneficial.

Utilizing a custom rollout allows for the automation of adding or updating images within the respective live copy, mirroring the manual authoring process.



Arun Patidar

View solution in original post

3 Replies

Avatar

Correct answer by
Community Advisor

Hi @madhuyadawad 

I believe leveraging a custom rollout could be beneficial.

Utilizing a custom rollout allows for the automation of adding or updating images within the respective live copy, mirroring the manual authoring process.



Arun Patidar

Avatar

Community Advisor

Hi @madhuyadawad 

One possible solution to manage this scenario is to customize the OOTB teaser component or create a custom component that handles the image inheritance in a more flexible way. 

1. Custom Teaser Component: Create a custom teaser component that allows authors to select the image directly instead of inheriting it from a linked page. This way, authors can manually choose the image for each teaser, eliminating the dependency on linked pages.

2. Custom Rollout Configurations: Modify the rollout configurations to exclude the image property from being rolled out to country sites. This way, the image property will not be inherited, and authors can manually author the images in the country site pages without affecting the global site.

3. Dynamic Image Path: Instead of directly linking the image in the teaser component, you can modify the component to dynamically generate the image path based on the country site. This can be achieved by using a custom script or logic to determine the image path based on the current site or country.

4. Content Fragments: Consider using Content Fragments to manage the image content separately from the pages. Content Fragments can be authored and managed independently and can be referenced in the teaser component. This way, the image content can be shared across multiple sites without the need for manual effort.



Avatar

Community Advisor

@madhuyadawad Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community



Esteban Bustamante