Expand my Community achievements bar.

SOLVED

Nested Fragment model is not getting published on publishing Content Fragment

Avatar

Community Advisor

As par Adobe documentation, "If you publish a content fragment for which the model has not yet been published, a selection list will indicate this and the model will be published with the fragment" but the nested content fragment (created using Fragment Reference data type) model is not getting published when we publish content fragment. Is it a product bug or OOTB behavior.

https://experienceleague.adobe.com/docs/experience-manager-65/assets/content-fragments/content-fragm...

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Hi @Bhuwan_B ,

This feature does work. I did try this on my AEM 6.5.11 server and I see on activation of a content fragment, it is pulling up its dependent model which is not published. Check the Screen capture here - 

https://github.com/sinhaanish/myDemoFiles/issues/1

 

View solution in original post

2 Replies

Avatar

Correct answer by
Employee Advisor

Hi @Bhuwan_B ,

This feature does work. I did try this on my AEM 6.5.11 server and I see on activation of a content fragment, it is pulling up its dependent model which is not published. Check the Screen capture here - 

https://github.com/sinhaanish/myDemoFiles/issues/1

 

Avatar

Community Advisor

@Anish-Sinha Thanks for your reply, I validated and it works fine on AEM 6.5.11.0 but it shows highlighted issue with AEM 6.5.10.0. Have logged an Adobe Ticket and checking for changes in implementation logic between AEM 6.5.10.0 and AEM 6.5.11.0.

The following has evaluated to null or missing: ==> liql("SELECT id, subject, body, depth, post_time, author.login, author.id, author.rank, metrics.views FROM messages WHERE topic.id = '${topicId}' AND is_solution = true").data.items[0] [in template "analytics-container" at line 82, column 31] ---- Tip: It's the final [] step that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign acceptedAnswer = liql("SELECT... [in template "analytics-container" at line 82, column 5] ----