- @hswong3i opened merge request.
- @hswong3i opened merge request.
- @hswong3i opened merge request.
- @hswong3i opened merge request.
- @hswong3i opened merge request.
- @hswong3i opened merge request.
- First commit to issue fork.
- 🇳🇿New Zealand quietone New Zealand
After looking at other configuration pages I think the simplest solution is to add a status column. That will help make the state of the format easier to see and uses an existing pattern for configuration.
- 🇳🇿New Zealand quietone New Zealand
Regarding #157 and the idea to have a second page to list disabled formats I think this was answered in point 2 of the href=" https://www.drupal.org/project/drupal/issues/2502637#comment-15058495 🐛 Disabled text formats can't be seen in the GUI Needs work ">Usability report in comment #116. Specifically they state "The group agreed moving the discussion how the enabled/disabled state is communicated to a follow-up issue with resolution TBD."
- 🇳🇿New Zealand quietone New Zealand
@vijayavelr, Welcome to Drupal! Thanks for the interest in this issue. Since your solution is a custom module and will never get committed to core I suggest you create a contributed module → for that work. That is, if you wish to.
I also checked the priority and agree with alexpott that this is not Critical. There is not data loss and there is a work around. I have added the work around to the issue summary, so it is can be found.
- 🇳🇿New Zealand quietone New Zealand
@vijayavelr, Welcome to Drupal! Thanks for the interest in this issue. Since your solution is a custom module and will never get committed to core I suggest you create a contributed module → for that work. That is, if you wish to.
I was looking at other other configuration forms for examples of having a separate page for disable 'things'. There is none that I saw. The closest was search pages which simply add a column for 'Status'. That is easy to implement but does not fulfill the suggestion of a second page. For me, I think before coding and changes this should get direction from usability. I also am inclined to think that this should go in as an incremental step towards a better solution. I will ping in #usability.
I also checked the priority and agree with alexpott that this is not Critical. There is not data loss and there is a work around. I have added the work around to the issue summary, so it is can be found.
I have created a custom module patch disabled_text_formats_18062024.patch → by listing the disabled formats with enable links
Step 1 :
Step 2 :
Step 3:
Step 4: