Probably this is sort of off-topic, but while I can add "Bulk operation: Queue" field to an Advanced Queue view, I consider it as VBO responsibility. If I wrong, correct me or move this issue to Advanced Queue (AQ) issues queue.
So the problem is that it's impossible to delete an item from AQ:
1) Add VBO filed to AQ view, enable "Delete item" op
2) Now in the view select an AQ item and execute Delete item op.
3) Result: item is not deleted, and instead more records is added to the AQ table (if viewing in the database) - those are about successfully executing operation on deletion which is of course fake as the op was to delete item and not about informing me about deleting something :)
Example view where I needed to delete items - is Commerce License Billing's synchronization view. If you simulate purchase of an example license of type "Example remote license" and then try to process an order with it, then you'll get new item in the Synchronization view (after executing AQ job, the item gets status of Failed btw)
I mark this as Task.
P.S. about AQ: at first I was confused about the lack of any admin UI for administrating AQ, but as soon as View integration is full and wonderful VBO is working as expected, no admin UI is needed as it can be cooked in few gestures.
Comments
Comment #1
OnkelTem CreditAttribution: OnkelTem commentedComment #2
OnkelTem CreditAttribution: OnkelTem commentedComment #3
OnkelTem CreditAttribution: OnkelTem commentedAfter short talk with Bojan, moving the issue to AQ queue.
So the question is how entity_delete() is implemented so that it can't really be deleted?
Comment #4
efpapado CreditAttribution: efpapado at Ramsalt Lab commentedHello, does anyone know the answer to OnkelTem's last question?
What is the logic behind NOT deleting old queue items?
I currently have an installation working with this module (because of commerce licence) for 3 months, and the advancedqueue table is already 2GBs (it contains more than 10.000.000 rows)
Comment #5
jweirather CreditAttribution: jweirather commented@efpapado: I'm not sure if you've seen it yet, but there is a patch available to help clean up the AQ table:
https://www.drupal.org/node/2054555
For me, I had to use patch #14 instead of #15.
Comment #6
jweirather CreditAttribution: jweirather commentedAnd +1 for the issue in general. I would really appreciate VBO actions for AQ items.
Also coming from Commerce License Billing, I'm experiencing quite a bit of errata, and VBO actions would make much easier the management of those issues.
Comment #7
Kazanir CreditAttribution: Kazanir at Platform.sh commentedWe're working on some improvements in this area -- not just VBO actions but overall better visibility, cleanup options, and more fine-grained control overall are on deck. Stay tuned.
Comment #8
Kazanir CreditAttribution: Kazanir at Platform.sh commentedOk, the default VBO actions from the Entity API module now work if it is enabled. We encourage people with specific needs to install this module and take advantage of the improved entity UX/DX it affords, and also to investigate the newly-committed table cleanup functions available on cron or at the end of queue runner processing. See the linked issues for more details.