>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3048232. --> Reported by: [idebr](https://www.drupal.org/user/1879760) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>The 'Hide revision field' module provides a configurable field formatter for the revision log field for revisionable entities. This allows you to create revisions but reduces noise for your content editors/site owners.</p> <p>This module overwrite the 'revision' form array key for content entity forms. The Scheduled Transitions module uses this array key to list the available revisions. This results in a very confusing user experience where the list is empty.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Since it hard to detect the hardcoded revision form element (see <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/drupal/issues/2696555" title="Status: Active">#2696555: On the entity form of revisionable entities, make "create new revision" and "revision log" configurable</a></span>), let's simply use a different array key to circumvent this array key collision.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ol> <li>Write a patch</li> <li>Review</li> <li>Commit</li> </ol> <h3 id="summary-ui-changes">User interface changes</h3> <p>Sites with the 'Hide revision field' module enabled can use the 'Scheduled transitions' module.</p> <h3 id="summary-api-changes">API changes</h3> <p>None.</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>None.</p>