>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3460895. --> Reported by: [geek-merlin](https://www.drupal.org/user/229048) Related to !49 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>- \Drupal\default_content\Importer::importContent does not <code>$entity-&gt;setSyncing()</code> before save.<br> - Third party post-save hooks thus have no way to know they should not fire.<br> - \Drupal\Core\Entity\SynchronizableInterface, which is extended by \Drupal\Core\Entity\ContentEntityInterface, is clear in its requirement:</p> <div class="codeblock"> <pre><span style="color: #000000"><span style="color: #0000BB">&lt;?php<br>&nbsp; </span><span style="color: #FF8000">/**<br>&nbsp;&nbsp; * Sets the status of the synchronization flag.<br>&nbsp;&nbsp; *<br>&nbsp;&nbsp; * @param bool $status<br>&nbsp;&nbsp; *&nbsp;&nbsp; The status of the synchronization flag.<br>&nbsp;&nbsp; *<br>&nbsp;&nbsp; * @return $this<br>&nbsp;&nbsp; */<br>&nbsp; </span><span style="color: #007700">public function </span><span style="color: #0000BB">setSyncing</span><span style="color: #007700">(</span><span style="color: #0000BB">$status</span><span style="color: #007700">);<br><br>&nbsp; </span><span style="color: #FF8000">/**<br>&nbsp;&nbsp; * Returns whether this entity is being changed as part of a synchronization.<br>&nbsp;&nbsp; *<br>&nbsp;&nbsp; * If you are writing code that responds to a change in this entity (insert,<br>&nbsp;&nbsp; * update, delete, presave, etc.), and your code would result in a change to<br>&nbsp;&nbsp; * this entity itself, a configuration change (whether related to this entity,<br>&nbsp;&nbsp; * another entity, or non-entity configuration), you need to check and see if<br>&nbsp;&nbsp; * this entity change is part of a synchronization process, and skip executing<br>&nbsp;&nbsp; * your code if that is the case.<br>&nbsp;&nbsp; *<br>&nbsp;&nbsp; * For example, \Drupal\node\Entity\NodeType::postSave() adds the default body<br>&nbsp;&nbsp; * field to newly created node type configuration entities, which is a<br>&nbsp;&nbsp; * configuration change. You would not want this code to run during an import,<br>&nbsp;&nbsp; * because imported entities were already given the body field when they were<br>&nbsp;&nbsp; * originally created, and the imported configuration includes all of their<br>&nbsp;&nbsp; * currently-configured fields. On the other hand,<br>&nbsp;&nbsp; * \Drupal\field\Entity\FieldStorageConfig::preSave() and the methods it calls<br>&nbsp;&nbsp; * make sure that the storage tables are created or updated for the field<br>&nbsp;&nbsp; * storage configuration entity, which is not a configuration change, and it<br>&nbsp;&nbsp; * must be done whether due to an import or not. So, the first method should<br>&nbsp;&nbsp; * check $entity-&gt;isSyncing() and skip executing if it returns TRUE, and the<br>&nbsp;&nbsp; * second should not perform this check.<br>&nbsp;&nbsp; *<br>&nbsp;&nbsp; * @return bool<br>&nbsp;&nbsp; *&nbsp;&nbsp; TRUE if the configuration entity is being created, updated, or deleted<br>&nbsp;&nbsp; *&nbsp;&nbsp; through a synchronization process.<br>&nbsp;&nbsp; */<br>&nbsp; </span><span style="color: #007700">public function </span><span style="color: #0000BB">isSyncing</span><span style="color: #007700">();<br></span><span style="color: #0000BB">?&gt;</span></span></pre></div> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <p>- Have a post-save hook that must not fire on isSyncing (e.g. creates group for created node)<br> - Import content.<br> - See that hook fires processint though it has correct isSyncing condition.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Add setSyncing.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <h3 id="summary-ui-changes">User interface changes</h3> <h3 id="summary-api-changes">API changes</h3> <h3 id="summary-data-model-changes">Data model changes</h3>