Closed (outdated)
Project:
Queue UI
Version:
7.x-2.x-dev
Component:
Documentation
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
10 Dec 2010 at 16:52 UTC
Updated:
9 Jan 2025 at 23:07 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
coltraneGreat idea
Comment #2
geerlingguy commentedSubscribe.
Comment #3
msonnabaum commentedHere's an initial stab at it. Seems to work using the beanstalkd queue backend.
Comment #4
coltrane#3 looks good though I haven't tested it yet
However, until there's a plan for meta queue information I don't want to swap to hook_cron_queue_info()
I'll start a discussion issue about that
Comment #5
chx commentedYou can always query cron queues and add the ones from MySQL.
Comment #6
msonnabaum commentedHere's a version that merges the hook_cron_queue_info implementations in with the custom hook.
Comment #7
gregglesComment #8
gregglesThis patch helped my beanstalkd backed site to see some queues that had a size of zero.
But, it doesn't help with the thing I care about which is deleting the queue. It applies with an offset of 1.
Comment #9
attiks commentedre-rolled for new version
Comment #10
jelle_sNew patch based on #9. With this patch Queue UI integrates nicely with hook_cron_queue_info(). There's no need for hook_cron() (queue_ui_cron()) anymore because queue ui implements hook_cron_queue_info(). This way, all queues defined in hook_queue_info that have a cron key in their info array and are enabled for cron (
variable_get('queue_ui_cron_' . $queue_name, FALSE) == TRUE) are exposed to cron via queue_ui_cron_queue_info (hook_cron_queue_info).Comment #11
jelle_s*sigh*... Forgot the patch
Comment #12
jelle_sReroll
Comment #13
volegerComment #14
volegerDrupal 7 reached EOL