Closed (fixed)
Project:
Entityqueue
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
27 Nov 2013 at 17:57 UTC
Updated:
29 Dec 2013 at 03:10 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
jojonaloha commentedThis patch actual requires that the patch in #33 of #1450590: Add permissions to queues is applied first. It adds a 'delete subqueue' link to the operations on the subqueues page. It also adds a canDeleteSubqueue(EntitySubqueue $subqueue) to EntityQueueHandlerInterface. For the MultipleEntityQueueHandler it doesn't allow deleting the original subqueue.
Comment #2
amateescu commentedThe patch looks good, feel free to commit it.
I did notice a slightly weird behavior while testing it though, something that I didn't anticipate in the original code that added the 'multiple queues' handler. Why do we default to create an initial subqueue for that case? It seems that if people want multiple subqueues, they should also be allowed to control the name of the first subqueue and also delete it. Maybe open a followup issue for that? It will also affect the
canDeleteSubqueue()code introduced here..Comment #3
jojonaloha commentedCommitted 76425b7
Also opened a follow-up issue: #2156879: Don't add initial subqueue for multiple queues