Experience Fragment reference provider behavior

[michaltobiasz]

I have some doubts if the reference mechanism used for experience fragments to provide references when publishing the page works as should.

I want to publish a page ex. /content/test/gb/en/page1 in edit mode. The page is based on the dynamic template which contains in the structure experience fragments (header and footer) pointing to language-master
/content/experience-fragments/test/language-master/en/header
/content/experience-fragments/test/language-master/en/footer

There are also XFs live copies created for en/gb
/content/experience-fragments/test/gb/en/header
/content/experience-fragments/test/gb/en/footer

Experience fragments store in the properties, paths to pages from the given market.
Ex.
/content/experience-fragments/test/language-master/en/header has component with property path pointing to /content/test/language-master/en/page2
/content/experience-fragments/test/gb/en/header has component with property path pointing to /content/test/gb/en/page2

In case when I publish /content/test/gb/en/page1 the reference mechanism is analyzing references from /content/experience-fragments/test/language-master/en/header and it children only. I'm wondering if this mechanism shouldn't check /content/experience-fragments/test/gb/en/header which is indead used by the page and don't check the language-master part.

Any idea if it is correct behavior or XF reference provider mechanism is missing something?

[ky940819]

Just to clarify for me,
Do you have XFs being referenced withing XFs?
Or is the issue that it's not picking up the correct localized XF variant, and is always just checking the master, which is what is actually referenced in the page (even if it's not what is rendered)?
Or none of the above?

[michaltobiasz]

Do you have XFs being referenced withing XFs? - No

Yes. The reference provider is not finding the correct localized XF ex. /content/experience-fragments/test/gb/en/header and it always just looking for references defined in the master /content/experience-fragments/test/language-master/en/header and it child nodes. The path to master is found in the template structure from which the page was created.

[vladbailescu]

@michaltobiasz, you are right: the reference provider should resolve to the localised experience fragments, not the masters, when publishing a localised page. Since the provider is not part of Core Components, but it's in the product, I filed an improvement ticket (CQ-4317044). Please reach out to customer support if you want to file a request and have it prioritised higher based on the impact on your work!

[michaltobiasz]

@vladbailescu thank you for your response!

[nowugetme]

XFs being referenced withing XFs the reference provider should resolve to the localised experience fragments
https://setkorp.com/