Description of the need
From @klonos in https://github.com/backdrop/backdrop-issues/issues/4890
With the label of the action being "Enable" as it currently is, it does indeed not make 100% sense in this case (although there is some logic that supported it being used, and it somewhat kinda matches other similar UI patterns).
Currently, with the PR as it is (and as @olafgrabienski pointed out), there is a small UX WTF when you click "Customize" and the display is moved to the "customized" section (without it actually being customized).
Proposed solution
Here's what @klonos is thinking would be a better UX:
- We leave the button label as "Customize" as per the current PR
- Change the action of that button so that it leads to the "Manage display" page for that display.
- Add a "Cancel" link/button to the "Manage display" form.
Additional information
This is a follow-up to https://github.com/backdrop/backdrop-issues/issues/4890
GitHub Issue #:
5129
Recent comments
To confirm that it is ok to be deleted, I would look in the config folder for any config files with the string taxonomyextra in. If you don't find any, then yet it is probably safe to drop...
taxonomyextra table after migration from Drupal 6
Today there was finally time to delve into this issue. First I downloaded the field_data_taxonomyextra table into a spreadsheet. There is a column called Bundle, which in my case included,...
taxonomyextra table after migration from Drupal 6
Hi Enthusiast - there is work in progress on an improvement to core that I think will help this. https://github.com/backdrop/backdrop-issues/issues/4127 I don't fully understand it...
The problem of caching the pages