The Operations Menu for a Taxonomy contains "Edit Vocabulary" but does not contain "Delete Vocabulary".
The Operations Menu for Menus and Content Types contains both "Edit" and "Delete".
I believe the Operations Menu for these two should be consistent within the context of /admin/structure. I've been working with Menus and Taxonomies all day. My preference would be to add "Delete Vocabulary" to the Taxonomy Operations Menu.
| Comment | File | Size | Author |
|---|---|---|---|
| #49 | interdiff-40-49.txt | 754 bytes | gaurav.kapoor |
| #49 | Adding-delete-vocabulary-2621626-49.patch | 1.79 KB | gaurav.kapoor |
| #44 | Adding-delete-vocabulary-2621626-0-6.patch | 994 bytes | alokbhatt |
| #40 | Adding-delete-vocabulary-2621626-0-5.patch | 945 bytes | alokbhatt |
| #35 | Adding-delete-vocabulary-2621626-0-4.patch | 1.13 KB | alokbhatt |
Comments
Comment #2
cilefen commentedI think this issue makes sense.
This is on the fine line between a bug, a feature, or a task. I am going with feature, which postpones it to 8.1.x.
Comment #3
Greg Sims commented@cilefen I understand why you might call this a Feature Request. Why would you defer it to 8.1.x? My understanding is this is 6+ months away. Perhaps it should be called a Human Factors Bug in the GUI.
Comment #4
cilefen commenteda) I could be wrong. ;-)
b) If it is a feature request, by definition it moves to 8.1.x. Actually the same is the case for "string, markup, user interface, or render array changes", which this issue is as well.
Comment #6
alokbhatt commentedAdded "Delete vocabulary" link as suggested.
Comment #8
alokbhatt commentedMay I know the cause of patch failure? The functionality is working fine at my end.
Does it failed after applying the patch?
Comment #11
alokbhatt commentedPlease review new patch
Comment #12
alokbhatt commentedThanks for review. Please move to rtbc.
Comment #13
dinesh18 commentedI tried applying the patch, but the patch does not apply. PFA screenshot Patch_failed.png.
We need to work on the patch.
Comment #14
alokbhatt commented@Dinesh18 : Kindly test it with Drupal 8 current Development version.
Comment #15
dinesh18 commentedHello,
#11 patch is working properly. PFA screenshots for different scenarios.
Also, PFA git bash warning errors which needs to be resolved.
Comment #16
dinesh18 commentedNeed to work on patch to remove warnings.
Comment #17
swentel commentedThere's no reason to move this to critical suddenly
Comment #18
alokbhatt commented@Dinesh18 : New patch won't give the warning. Thank you for review it. Please check again new patch.
Comment #19
alokbhatt commentedComment #20
cilefen commentedIf there is broad agreement, this may as well be a task.
Comment #21
dinesh18 commented@alokbhatt : I have tested the new patch #18 and it doesn't give any warnings in git bash and it is working as expected. PFA screenshot
Changing the status to RTBC
Comment #22
lauriiiIt would be great to have UI review from a product manager on this.
Comment #23
yoroy commentedThe other listings where there is a delete link (content types, views, custom block types, view modes, likely others as well) the label is only "Delete", not "Delete ", so I think we should do that here as well. The position of the link is correct: it should be the last one.
Thanks for working on this!
Comment #24
gaurav.kapoor commentedComment #25
gg24 commentedPatch works as intended for me.
Comment #26
alexpottThis is not necessary the default title is
'Delete'... plust()would be wrong here - and yes it is wrong above.Also I think we should file a followup issue to review the order of the vocabulary operations and consider changing "Edit vocabulary" to "Edit" to match content types etc... In my opinion the order should be the same as what you see on admin/structure/types for content types (which is the same as you see on admin/structure/block/block-content/types and admin/structure/comment) but with "Add terms" and "List terms" first because these are the most common operations for people - happy to defer that to a UX expert though. What I'm pretty sure about is that the order on admin/structure/taxonomy is pretty odd.
Comment #27
alokbhatt commentedCan we have clear requirement? Because initially there was no such comment on link title and if I am not wrong issue was about "Delete" link was not there and depends on that I made a patch file.
Comment #28
yoroy commentedCurrent situation:
Desired situation:
Additional steps
Does that help?
Comment #29
alokbhatt commentedYes, that is clear.
@alexpott: Please clear the order, it should like below:
List terms
Add terms
Manage fields
Manage form display
Manage display
Edit
Delete
Please correct the order if not suitable, also publishing new path with the same. Please review new patch.
As you said t() is not required that doesn't make sense to me, because it is labels which should be translatable, correct me if I am wrong.
Comment #30
alokbhatt commentedComment #32
alokbhatt commentedAdding patch because previous one was failed.
Comment #33
alokbhatt commentedComment #34
alokbhatt commentedComment #35
alokbhatt commentedNo sure why the patch is not going into the queue for testing, so I am uploading it again.
Comment #36
alokbhatt commentedComment #39
berdirwhat Alex is saying is that these lines are not necessary because those are the default labels from the parent method. Just remove them and it will look the same.
Comment #40
alokbhatt commented@Berdir: Thanks for review. Please review new patch.
Comment #41
alokbhatt commentedComment #42
berdirA test is looking for an edit vocabulary link, you need to update that to use just Edit
Comment #43
alokbhatt commented@Berdir: You suggest to remove "Edit" line in #32, anyways I tested in my local machine, it shows "Edit" only.
Comment #44
alokbhatt commentedPlease check updated patch.
Comment #45
alokbhatt commentedComment #48
berdirNo, you misunderstood.
The previous patch was fine. But as you can see, it has a failing test that we need to fix. In VocabularyUiTest.php, it is still looking for "Edit vocabulary", that's what you need to update. That and going back to the patch from #40.
Comment #49
gaurav.kapoor commentedComment #50
swaps commented@yoroy -I would propose to keep Lable as 'Delete Vocabulary'.
For other cases like content types or menus - Delete , Edit lables are making clear sense.
But Vocaulary will have terms associated with it . Also 'List terms' , 'Add terms' links are also there in the dropdown .
Keeping link label as 'Edit Vocabulary' and 'Delete Vocabulary' would give better experience.
Current situation:
There is no link to delete a vocabulary in the dropbutton on the vocabulary listing page
Desired situation:
Add a delete link to the dropbutton.
The label should be "Delete Vocabulary".
The link should be the very last one in the dropbutton.
*Maybe we can also update 'Add terms' lable to 'Add term'
Cheers,
SwapS
Comment #51
yoroy commentedWell, deleting a vocabulary *also* deletes its terms. Which is tricky in itself, but I don't think "Delete vocabulary" instead of "Delete" helps with that. If anything, it might even suggest that the terms inside might not get deleted.
Comment #52
berdirAgreed with #51.
What we are missing is to extend the tests to make sure that there is a Delete operation now as well and clicking it to make sure we end up on the delete form.
Comment #54
websiteworkspace commentedHow does basic and essential functionality like "delete vocabulary" not exist when 8.x core is already at 8.4?
Why two years, and still this patch hasn't been made part of a release?
Comment #55
websiteworkspace commentedComment #56
swentel commentedComment #57
flocondetoileRe #54 : The delete link is available when editing a vocabulary. You can delete a vocabulary. This is *just* the link in the dropdown buttons in the vocabulary page list which miss.
Comment #59
amateescu commentedDuplicate of #2469545: Vocabulary listing missing delete operation for vocabularies.