When exporting Fragment based pages hide Primary key reference tight to a site that can't be validated on other sites

• Type: Story
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: None
• Fix Version/s: None
• Component/s: Fragment Administration
• Labels:
  • d_20_12
  • d_21_01
• Epic Link: Export group of pages to import from a Site Initializer to simplify development

Intro/context:

When we export a fragment based pages we also export some internal keys to reference content. However this key is unique to the site that has been used to export the fragment based page and will bring issues to the importer.

The goal of this Story is to solve the issue for fragments while we don't solve it for widgets (config can't be saved) due to the amount of work that it represents (around 70 widgets). We might bring support for specific widgets (if requested)

- 

When exporting a fragment based page (display page template, content page, master page, template page)

Then there is no internal references to contents which value is tight to a site configuration

-