I run corn and then I noticed the error message as follow at Reports/recent log messages
Notice: Undefined property: stdClass::$module in _linkchecker_add_block_custom_links() (line 916 of C:\wamp\www\sites\all\modules\linkchecker\linkchecker.module).
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | screenshot.png | 28.94 KB | DrupalDan |
Comments
Comment #1
hass commentedAre you really running latest DEV?
Comment #2
hass commentedThis cannot happen at cron time. Please describe how to repro.
Comment #3
DrupalDan commentedYes, I'm pretty sure I'm running the latest dev version as I downloaded it eariler today. I did nothing partcular, just followed the routine: install, enable, and configure. As far as configuration, I just checked the content types for scanning and set Check interval for links 1 day and left everything as default. To be sure everything is ok I went to reports to see if there was any error reported there, and then I found it.
I think that's pretty much the whole process. Attach a screenshot for your information.
Thanks
Comment #4
hass commentedFirst of all. Set the check interval back to 4 weeks, please. I should remove this bullshit setting.
Please also add the lines documented in http://drupal.org/node/1603782#comment-6049218 and run the clear all button on the bottom of the settings page. Your screenshot shows it happened in a batch, not cron.
Thanks for reporting back. Block module suxxx more and more...
Comment #5
DrupalDan commentedHi hass, thanks for your response. After adding the lines, does it look like this?
Comment #6
hass commentedThis was a far larger fix than I expected, but I found the reason, refactored the logic and fixed the bug. There is no need to backport to D6. Would be great to hear; if this fixed the issue for you.
Commit: http://drupalcode.org/project/linkchecker.git/commit/a920eb0
Comment #7
DrupalDan commentedHi hass, I just downloaded the latest dev version and after I run cron, the system didn't throw that error message anymore, so I think that means the issue has been fixed. Thank you very much for the effort.
Comment #8
hass commentedThanks a lot for your feedback!