As a Fragment Developer I can enable an automatic propagation mode

• Type: Story
• Status: Closed
• Priority: Critical
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.2.X, Master
• Component/s: Fragment Administration
• Labels:
  • 7.2-sp1-should
  • fc_19_08
  • liferay-dxp-72-sp1
  • liferay-fixpack-dxp-2-7210
  • test_manual_done
  • test_map
• Branch Version/s:
  7.2.x
• Backported to Branch:
  Committed
• Epic Link: Automatic Fragment Propagation Mode
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/74360

Currently, when a fragment developer makes a change to an existing fragment, the change is not automatically propagated to the pages that were using this. This is by design, so that marketers and page authors in general have a higher degree of control over their pages, since they won't be automatically updated. Fragment developers still have the option to manually request propagation of changes when really needed.

For production, this works fine, but in development environment, having to manually propagate can become tedious. To solve this, the proposed solution is to allow enabling an automatic propagation mode. This mode is not active by default. When enabled, all fragments will be monitored for changes. Whenever a change happens, all pages using the fragment will be updated as well.

It must be possible to enable the fragment mode for the whole installation (system level configuration) or for an specific virtual instance.