a) you can use the cron_queue hook to grab some of the queue names b) you can ask the user to enter them. This way it would not be DB dependent.

Comments

coltrane’s picture

Great idea

geerlingguy’s picture

Subscribe.

msonnabaum’s picture

Status: Active » Needs review
StatusFileSize
new2.01 KB

Here's an initial stab at it. Seems to work using the beanstalkd queue backend.

coltrane’s picture

Status: Needs review » Needs work

#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

chx’s picture

You can always query cron queues and add the ones from MySQL.

msonnabaum’s picture

Here's a version that merges the hook_cron_queue_info implementations in with the custom hook.

greggles’s picture

Status: Needs work » Needs review
greggles’s picture

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

attiks’s picture

Version: 7.x-1.x-dev » 7.x-2.x-dev
StatusFileSize
new1.85 KB

re-rolled for new version

jelle_s’s picture

New 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).

jelle_s’s picture

*sigh*... Forgot the patch

jelle_s’s picture

Reroll

voleger’s picture

Issue summary: View changes
Status: Needs review » Postponed (maintainer needs more info)
Issue tags: +Needs issue summary update, +Needs reroll
voleger’s picture

Status: Postponed (maintainer needs more info) » Closed (outdated)

Drupal 7 reached EOL