Needs review
Project:
SuperCron
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Jul 2010 at 02:48 UTC
Updated:
10 Aug 2011 at 21:29 UTC
Jump to comment: Most recent file
Comments
Comment #1
Manonline commentedThis file add the drush support. It need work, but marking as need review.
Usage:
- drush supercron [modules]
- drush supercron all
Comment #2
thekenshow commentedTesting on D6.16 and drush 3.3, 'drush supercron --help' returns the help text but trying to run any or all modules (e.g., 'drush supercron system') return "Drush command could not be completed" (The Last Called entry on the Settings page confirms that hook_cron has not been run for the module).
Comment #3
rcross commentedComment #4
eojthebraveCleaned up the code, removed all references to node_export module, added some additional comments, and fixed things so it will work with 2.x-dev version of the module.
I also modified the callback function a bit so that if you do NOT specify either the name(s) of a module whose hook_cron() implementation you want to run, or the keyword 'all', drush will present you with a list of enabled modules to choose from. Much like typing `drush clear-cache` with no arguments.
Comment #5
pillarsdotnet commentedComment #6
cor3huis commentedCould not life test due to other issue, but reading through, it looks fine.
IMHO It is best to have a feature freeze for SuperCron v2.x now otherwise a v2.x will never see the light of day.
Then also we can start a port to Drupal 7...
Comment #7
pillarsdotnet commentedIt's not RTBC until it's tested. That's the "T" in "RTBC".
Comment #8
cor3huis commentedTrue, thanks, I was to enthusiastic. However other critical issues make it impossible to test at the moment.
Comment #9
pillarsdotnet commentedHere's a combined patch for all critical issues. Now you can test.
Comment #10
bcmiller0 commented+1
Comment #11
pillarsdotnet commentedModule appears abandoned.
Comment #12
jdwfly commentedLets not close issues just because the module appears abandoned. You never know when the maintainer will pick up development again, and from what I have read it seems as though they are starting back up. It may be worth a shot emailing the developer to see if they would review your patch. I've done that many times and sometimes they even gave me commit access.
Comment #13
pillarsdotnet commentedSorry; I'm no longer using D6 on any of my sites, and I've moved to Elysia Cron for my D7 sites, so I'm okay with the module and patch being abandoned.