By default, changes made to a custom fragment’s code are not propagated to deployed instances of the fragment. Using Fragment Propagation, you can propagate changes to fragment instances in one of two ways:
To avoid overwriting data, changes made to editable fields cannot be propagated to the fragment directly. However, you can force propagation by changing the fragment’s field ID. When propagated, the field’s content is no longer displayed, though you can retrieve its content from the database using the old field ID. To learn more, see Fragment Specific Tags and Attributes Reference in the developer documentation.
Follow these steps to manually propagate changes to individual instances of a fragment:
Open the Site Menu () and go to Design → Fragments.
Navigate to the Fragment Set for the desired fragment.
Click the Actions button () for the desired fragment and select View Usages.tip
If the View Usages option is unavailable, the fragment is not in use.
In the Usages and Propagation page, check the fragment instances you want to update to the latest version.
In the table, you can review whether a page or template is using a Previous Version or the Latest Version.
Click the Propagate button () to update the selected instances of the fragment.
Changes made to non-editable fields are automatically propagated to the selected fragment instances.
Follow these steps to automatically propagate changes to all instances of a fragment:
Automatic propagation can lead to unintended consequences in the production environment, such as typos or inaccurate content being published. Use Automatic propagation only for testing or development purposes.
Open the Global Menu (), click the Control Panel tab, and go to Configuration → System Settings.
Under the Content and Data section, click Page Fragments.
Check the Propagate Fragment Changes Automatically box.
When enabled, changes made to a fragment’s non-editable fields are automatically propagated to all instances of the fragment.