>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3560904. --> Reported by: [joelpittet](https://www.drupal.org/user/160302) Related to !58 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>When providing a custom selection handler for the <code>og</code> selection group, it never appears in the field settings UI. The code that builds the handler options replaces all discovered <code>og</code> handlers with the hard-coded <code>og:default</code> plugin, preventing other handlers from being listed. </p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <ol> <li>Create a custom selection handler within the <code>og</code> selection group.</li> <li>Add an OG reference field using <code>OgStandardReferenceItem</code>.</li> <li>Open the field settings form.</li> <li>Only <code>og:default</code> appears, and the custom handler is missing.</li> </ol> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Adjust the handler-collection logic in <code>OgStandardReferenceItem::fieldSettingsForm()</code> so it gathers and lists all plugins under the <code>og</code> selection group instead of forcing <code>og:default</code>. Ensure the form populates available handlers without overwriting them. </p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>Identify expected structure of OG selection group plugins.</li> <li>Update code to correctly merge all handlers.</li> <li>Add tests to confirm custom handlers appear.</li> </ul> <h3 id="summary-ui-changes">User interface changes</h3> <p>Additional handler options may appear in the field settings form when OG selection plugins are present. </p>