>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3513811. --> Reported by: [joelpittet](https://www.drupal.org/user/160302) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>In a fresh install of the Organic Groups (OG) module, creating a group and a group content type with the <code>og_audience</code> field (which uses the <code>og_standard_reference</code> field type) results in a field instance being generated with the <code>og:default</code> selection handler.</p> <p>However, when navigating to the field in the Field UI and saving the field settings, the handler is replaced with <code>default:node</code>. This also forces the user to select a bundle because:</p> <ul> <li>The available group types are not filtered.</li> <li>The <code>og:default</code> handler is not presented in the UI.</li> </ul> <p>This behavior is unexpected and suggests an inconsistency in how the selection handler is initialized and persisted.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <ol> <li>Install the Organic Groups module in a fresh Drupal instance.</li> <li>Create a group content type and add an <code>og_audience</code> field.</li> <li>Observe that the field instance uses the <code>og:default</code> selection handler.</li> <li>Navigate to <strong>Admin &rarr; Structure &rarr; Content types &rarr; (Your group content type) &rarr; Manage fields</strong>.</li> <li>Edit the <code>og_audience</code> field settings and save.</li> <li>The selection handler changes from <code>og:default</code> to <code>default:node</code>, forcing the selection of a bundle.</li> </ol> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <ul> <li>Determine whether <code>og:default</code> should be used as the initial selection handler or if <code>default:node</code> should be applied from the start.</li> <li>Consider extending the default selection handlers at runtime instead of relying on <code>og:default</code>.</li> <li>Add explicit OG selection handlers similar to those in Drupal 7: <ul> <li><code>og_non_member_post</code>: Allows selecting group nodes that a user is <strong>not</strong> a member of.</li> <li><code>og</code>: Restricts selection to group nodes where the user <strong>is</strong> a member.</li> </ul> </li> <li>Ensure that the selection handler does not unexpectedly change when saving field settings.</li> </ul> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>Investigate why <code>og:default</code> is being replaced by <code>default:node</code>.</li> <li>Decide whether OG should override the selection handler at runtime rather than during field creation.</li> <li>Implement missing selection handlers from OG in Drupal 7.</li> <li>Add test coverage to verify the correct handler behavior before and after saving field settings.</li> </ul> <h3 id="summary-ui-changes">User interface changes</h3> <ul> <li>Modify the Field UI to properly present and persist the <code>og:default</code> handler.</li> <li>Add missing OG selection handlers to the selection UI.</li> </ul> <h3 id="summary-api-changes">API changes</h3> <ul> <li>Ensure OG extends the correct selection handler instead of modifying it unexpectedly.</li> <li>Introduce additional OG-specific selection handlers.</li> </ul> <h3 id="summary-data-model-changes">Data model changes</h3> <ul> <li>No direct database schema changes, but field configuration behavior needs review and may need config update.</li> </ul>