- Issue created by @Balu Ertl
- First commit to issue fork.
- Status changed to Needs review
about 1 month ago 5:13pm 7 May 2024 - π¬π§United Kingdom NexusNovaz
Hi @Balu Ertl,
Changed the checkboxes to be a tableselect. Tested locally and it seems to work as intended. Please could you review #4
- Issue was unassigned.
- Status changed to Needs work
about 1 month ago 1:39pm 8 May 2024 - ππΊHungary Balu Ertl Budapest πͺπΊ
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.) - π¬π§United Kingdom NexusNovaz
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!
- Status changed to Needs review
about 1 month ago 7:18pm 9 May 2024