>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3274553. --> Reported by: [anybody](https://www.drupal.org/user/291091) Related to !31 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Allow to define typical, named presets (profiles) to select from when configuring field display settings instead of setting each value individually.</p> <p>On each field's display settings, "fences presets" can be used as follows:</p> <p>Use the settings from the global preset, but don't store the reference so that the field settings are standalone like entered manually. The settings shouldn't be disabled, when a preset is used, as they are completely detached from the global preset and can be further overwritten per field display setting (if necessary).</p> <p>This should be implemented as submodule: fences_presets</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>Create a "fences_presets" submodule. (use <code>drush gen</code> to generate the module and move it into a new "modules" folder)</li> <li>Create a "fences_preset" config entity (might be possible to generate one through <code>drush gen</code> otherwise checkout the <a href="https://git.drupalcode.org/project/examples/-/tree/4.0.x/modules/config_entity_example">config_entity_example</a> although its routing doesn't seem up-to-date.... otherwise look for config entities in core.)</li> <li>The config entity should have the following basic properties:</li> </ul> <ol> <li>ID</li> <li>label</li> <li>status (enabled / disabled)</li> <li>description</li> </ol> <ul> <li>And the following fences properties (see fences.module, these should be wrapped inside a fieldset on display):</li> </ul><ol> <li>field_tag</li> <li>field_classes</li> <li>field_items_wrapper_tag</li> <li>field_items_wrapper_classes</li> <li>field_item_tag</li> <li>field_item_classes</li> <li>label_tag</li> <li>label_classes</li> </ol> <ul> <li>The config entity should have an add / edit form, delete form and config entity collection (should be auto generated through <code>drush gen</code>, otherwise see examples module / core implementations)</li> <li>The select should include an option "No preset" which is selected by default and does not change any settings (also very good for the follow-up issue so that there is a way to change from a preset to the "No preset" option if there are a few unique or specific changes to one item).</li> <li>Create a new select render element inside "<a href="https://api.drupal.org/api/drupal/core%21modules%21field_ui%21field_ui.api.php/function/hook_field_formatter_third_party_settings_form/10.0.x">fences_field_formatter_third_party_settings_form()</a>", called "fences_presets", where the preset config entities can be selected from, note that this form element should be purely cosmetic and not save any real value in the config, it's just used to be picked up by the JavaScript. ALTERNATIVELY, we could also render the select via JavaScript, but that's not good for the follow-up issue, where we want to reference the preset entities.</li> <li>Once, the value from the "fences_presets" select changes, we need to load the values of the selected preset and pass it to JavaScript. Inside our JavaScript, we need to populate the fences options with the values from our selected preset entity (field_tag on fences_field_tag, field_classes on fences_field_classes, etc.). This should be done by passing an array representation of the fences presets into "drupalSettings", through attaching the JS library in <a href="https://api.drupal.org/api/drupal/core%21modules%21field_ui%21field_ui.api.php/function/hook_field_formatter_third_party_settings_form/10.0.x">fences_field_formatter_third_party_settings_form()</a> and passing the config entities to drupalSettings. This way, JavaScript can simply access "drupalSettings" and get the config entity (by config entity ID).</li> </ul> <p>And that's it! The config entity itself should not update, when a preset is overridden on a field formatter setting. This part will be tackled in the future through: <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-4"><a href="https://www.drupal.org/project/fences/issues/3419266" title="Status: Postponed">#3419266: Add option to ovewrite fences presets in the formatter settings (preset by reference)</a></span>.</p> <p><strong>Tests are needed as well.</strong></p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Allow to define presets for typical configurations.</p> <h3 id="summary-ui-changes">User interface changes</h3> <p>A simple select, with presets separated with optgroups:<br> <img src="https://www.drupal.org/files/issues/2023-07-20/fences_presets.png" alt=""></p> <h3 id="summary-api-changes">API changes</h3> <h3 id="summary-data-model-changes">Data model changes</h3>