Issue with Footer Template, When saving Footer with visibility conditions

[QuentinSAUT]

Hi everyone, 
We are asking for help, as we struggling with ACS editor.

On ACS STG, we are working on a new footer in "HTML TYPE = TEMPLATE."

After building the footer with content and style (specifically, we added visibility conditions for mobile-only and desktop-only at the structure level, as well as the "Do Not Stack" function for a four-column structure), we encountered an issue.

When we save the FOOTER TEMPLATE as a FOOTER FRAGMENT, we lose the visibility conditions and the "Do Not Stack" function.

Could you please help us resolve this issue?
CC enclosed exemples

Thank you in advance for your support.

Best regards,

[Craig_Thonis]

Hi Quentin,

This is a limitation with content fragments in which personalized or dynamic content cannot be saved as a fragment. Please see the documentation below where the following statement was pulled:

"Fragments cannot include personalization fields, dynamic content or another fragment.

Avoid saving as a fragment content with empty structure components. Once the >fragment is inserted, they will not be editable.

The mobile view is not available in fragments."

https://experienceleague.adobe.com/en/docs/campaign-standard/using/designing-content/building-email-...

Regards,
Craig

[QuentinSAUT]

thank you Craig Thonis for your answer, 

Do you think there is a way to get around this limitation? 
Can we directly compel the "visibility condition"n and the "do not stack" into the HTML? 

We truly need to have a footer saved as a fragment with different displays for mobile and desktop.

Thank you

[Sukrity_Wadhwa]

Hi @QuentinSAUT,
As shared by Craig, this appears to be a feature limitation. For the workaround that you’re exploring, I am looping in a few of our Community Advisors to check if there’s an alternate path that they can suggest. 

@ccg1706 & @SatheeskannaK - Is this something that you could help with? Would love your input here if you’ve come across a similar use case. Let me know what do you think.

[ccg1706]

Hi @QuentinSAUT regarding my experience with some projects, the best way that comes to mind it's trying to reach what you want by developing a content block. This will allow you to take full control over the layout, responsiveness, you can reuse it and avoid the limitations of fragments.

If you can share in detail your requirements, I'd be happy to help you further on with the implementation.

Best regards,

Celia