Problem/Motivation
The Rabbit Hole settings details element is shown on the vocabulary overview page. Maybe it's just an opinion, but I feel like it doesn't belong there. I'm also pretty sure it didn't appear there before updating my site to Drupal 11.3.2.
Steps to reproduce
Visit a taxonomy vocabulary list page.
Proposed resolution
Exclude 'overview' entity operations.
| Comment | File | Size | Author |
|---|
Issue fork rabbit_hole-3567965
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
dieterholvoet commentedComment #4
kazuko.murata commentedIt works fine on Drupal Core 11.3.2 and Rabit Hole 8.x-1.0.
Comment #5
johnatas commentedHello,
I can reproduce the issue with Drupal 11.3.2 and Rabbit Hole 2.0.0-beta1.
This issue appears to come from this change: Drupal\taxonomy\Form\OverviewTerms now extends Drupal\Core\Entity\EntityForm introduced in Drupal 11.3.0.
The fix proposed in MR !95 correctly fixes the problem.
Thanks,
Comment #6
anybodyConfirming this issue and setting priority to major, because it breaks the Taxonomy overview page saving functionality entirely, as reported in #3564792: Changes to the order of taxonomy elements are not saved.
Maybe you could ping a mainainer @dieterholvoet?
Comment #7
ronchica commentedThis fix also needs to be applied to the 8.x branch. It is a major issue as we cannot save the taxonomy term pages without using the patch from #3564792.
Comment #12
japerryConfirmed against 1.x and 2.x. since this is critical, and no new tests failed with 8.x-1.x, both are merged!
Comment #14
anybodyThanks @japerry, would you mind tagging a release with this critical fix? Seems all Drupal ^11.2 projects are affected
Comment #15
isampo commentedWhile waiting for the new release, here is the change from MR95 as a static patch for 2.0.0-beta1.
Comment #16
japerryNew releases made!
Comment #17
acbramley commented+1 to a new release with a critical fix (plus the 8.4 deprecation fixes!)
Comment #18
anybodyThank you very much @japerry!! :)
That was helpful.