Issue with Footer Template, When saving Footer with visibility conditions | Community
Skip to main content
Q
QuentinSAUT
February 10, 2025
Question

Issue with Footer Template, When saving Footer with visibility conditions

  • February 10, 2025
  • 1 reply
  • 967 views

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,

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

Craig_Thonis
Adobe Employee
Craig_ThonisAdobe Employee
Adobe Employee
February 14, 2025

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.
    Q
    QuentinSAUTAuthor
    February 19, 2025

    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
    Community Manager
    Sukrity_WadhwaCommunity Manager
    Community Manager
    May 14, 2025

    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.

    Sukrity Wadhwa
      Terms & ConditionsAccessibility statement

      Loading footer...