When a Profile entity is modified within its own postSave() method, the isSyncing state is not correctly propagated.
This leads to unexpected behavior when profile updates indirectly trigger configuration changes or other entity updates that rely on isSyncing to avoid recursive or unintended operations.
In other words, during profile save operations initiated as part of a config import or other syncing process, follow-up changes triggered in postSave() may still execute logic that should be suspended when isSyncing is TRUE.
This can result in:
- Configuration updates running during sync operations
- Unwanted hooks or side effects triggering
- Potential infinite loops or partial updates during imports
- Implement hook_ENTITY_TYPE_presave() or hook_ENTITY_TYPE_update() on profile that triggers a config or entity update.
- Save a profile entity as part of a config import or other syncing process where $entity->isSyncing() should be TRUE.
- In postSave(), trigger a change that causes another entity/config to update.
- Observe that isSyncing is not correctly propagated to the triggered operations.
Ensure that the isSyncing flag is correctly maintained during the postSave() phase for Profile entities.
- Add test coverage to confirm isSyncing is respected during postSave() operations.
- Update Profile::postSave() to propagate the flag correctly.
None.
- Internal behavior of Profile::postSave() adjusted to ensure isSyncing is respected.
- No changes to the public API.
None.
Active
1.0
Code
zaporylie → changed the visibility of the branch 3538535-propagate-synchronize-flag to hidden.