Allow enabling all metadata fields by one click

Hi @Balu Ertl,

Changed the checkboxes to be a tableselect. Tested locally and it seems to work as intended. Please could you review #4

Hi Tyler, welcome to the Drupal Community! Thanks for picking up this issue. You started the right way but some further changes are still needed. Now tested the current MR and this is how it looked like to me:

The human labels of metadata fields in the rows display only their first character. This is because the core's Tableselect form element expects row data at an extra level deeper in the #options array key. Also the #header array key has to be under exactly the same name:

Now we have only one single column so I used “column” for the sake of simplicity. But the tech spec shows a clearer example of having multiple columns. Please apply the same changes so you should receive something like this:

Also, keep in mind that for the easiest way of testing, you need to authenticate your site to an Acquia DAM instance and check how the received data is being displayed. (If you have no access to an Acquia DAM system, then try mock the $display_key_options by filling up made up terms and check the rendered results.)

Hi! Thank you for the welcome!

I've made a change to MR #51. I've now got a result like you do.

Thank you for the extra information and time you put into your response also!

Hopefully this is now looking and working as expected!

As a feature improvement this should target branch 1.1.x. The MR needs to be updated.

baluertl → changed the visibility of the branch 1.1.x to hidden.

baluertl → changed the visibility of the branch 3444915-allow-enabling-all to hidden.

baluertl → closed merge request !51

1. Port changes from MR !51 to branch 1.1.x as MR !95
2. Remove the unnecessary Form title override, use the Page title from the routing itself instead
3. Delete the unnecessary fieldset form element
4. Replace instructions with a much more informative description about the purpose of this page
5. Invoke the parent form logic to allow alteration by anyone else
6. Use the action button inherited from the parent form controller
7. Do not render the form if there is no metadata from the Widen API

Current implementation:

Looks good! Committed

Automatically closed - issue fixed for 2 weeks with no activity.