The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Add some extra watchdog() logging to help debug problems during the cron run.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | twitter-n2558457-9-6.x-5.x.patch | 4.7 KB | damienmckenna |
| #8 | twitter-n2558457-8-7.x-6.x.patch | 4.41 KB | damienmckenna |
| #6 | twitter-n2558457-6-7.x-5.x.patch | 4.49 KB | damienmckenna |
Comments
Comment #2
damienmckennaFor 6x-5.x.
Comment #3
damienmckennaComment #4
damienmckennaAnd a little more.
Comment #5
damienmckennaPorted to 7.x-6.x.
Comment #6
damienmckennaPorted to 7.x-5.x.
Comment #7
damienmckennaA small update for 6.x-5x.
Comment #8
damienmckennaUpdated patch for 7.x-6.x.
Comment #9
damienmckennaThe last 6.x-5.x was actually the 7.x-5.x patch uploaded a second time. Doh.
Comment #10
damienmckennaCommitted.
Comment #15
bibo commentedThis is kinda old, but may I ask why there is not option to avoid this debugging? I've setup my Twitter-module and accounts correctly, but I don't want to import tweets right now. So my logs are getting filled with:
It's annoying because I've managed to remove all other unimportant clutter from the logs. Even this message is avoidable by for example not letting the modules cron hook run, but I would imagine it to be best if there was a variable to be avoid writing these messages (with UI or settings.php only).
Sorry for commenting on this old issue though, I don't plan on creating an issue about this. Maybe I'm the only one annoyed by the log spam.
Comment #16
danchadwick commented@bibo +1. Log spam in the d7 version is annoying.