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

OnkelTem’s picture

Issue summary: View changes
OnkelTem’s picture

Issue summary: View changes
OnkelTem’s picture

Project: Views Bulk Operations (VBO) » Advanced Queue
Version: 7.x-3.x-dev » 7.x-1.x-dev
Component: Core » Code
Category: Task » Bug report

After 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?

efpapado’s picture

Hello, 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)

jweirather’s picture

@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.

jweirather’s picture

And +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.

Kazanir’s picture

Assigned: Unassigned » Kazanir
Category: Bug report » Feature request
Priority: Normal » Major

We'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.

Kazanir’s picture

Status: Active » Closed (duplicate)
Related issues: +#2054555: Cleanup of the advancedqueue table, +#1998326: Add VBO support to change status

Ok, 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.