Ahhhh I misunderstood, you're working on the code itself, I was thinking more "end user".
PHP kicks that notice out when you're trying to read a variable that hasn't been set with any data.
Personally, this should be sent to the coders of these two modules, but I'm a sucker for bug-fixing, and here's a guess.
Line 36 of bot_joomblog.php -- change it to read as follows: if (isset($row->state))
{ if (!$row->state) {return;} }
Line 229 of mod_rd_section_blog.php -- change it to read as follows: if (isset($r->params))
{$content_params =& new mosParameters( $r->params );}
This is a best guess.. it could very well break your code. Make sure you can revert to a copy just in case..basically all I'm doing is checking to see if there's actually data there before executing that bit of code.
I'd give this a whirl, if it does the trick, great, but if not, you're really should be chatting to the guys who coded this.