Well, maybe if I post some of the actual errors I’m getting, it’ll help…
Warning: array_map(): The first argument, ‘map_attrs’, should be either NULL or a valid callback in c:\websites\wordpress2.02\wp-includes\rss-functions.php on line 164
Warning: join(): Bad arguments. in c:\websites\wordpress2.02\wp-includes\rss-functions.php on line 164
It’s those two lines, repeated over and over again.
Lines 160 through 169 is this:
// if tags are inlined, then flatten
$attrs_str = join(' ',
array_map('map_attrs',
array_keys($attrs),
array_values($attrs) ) ); <-- line 164
$this->append_content( "<$element $attrs_str>" );
array_unshift( $this->stack, $el ); }
Again, these errors appear only until I refresh the page. Then they go away.
Anyone have any ideas?
Well, I *think* I’ve figured it out. I’m going to post the solution I found here – but I make no guarantees. The reason I say this is because the problem disappears when you reload the page and doesn’t come back. However, when I shut down my computer last night, then brought everything back online this morning, the problem presented itself again. So my possible solution *could* be just a case of the fact that I reloaded to see if it actually worked, and that’s why it’s working. (I hope that made sense to you!)
Anyway, I closed my browser, reopened it, cleared the cache and it worked. Then I closed everything and shut down the computer, rebooted and tried again – it still works – no more error. So if someone else comes along and has this error and can give this a try (just to see if it actually *does* work) I’d appreciate a follow-up.
In the meantime, here’s the solution I came up with.
Turns out “join()” is just an alias for the PHP function “implode”. So, I changed this:
$attrs_str = join(' ',
to this:
$attrs_str = implode(' ',
And so far, it’s working.
Again, if anyone ever finds differently, please let me know. (And if this *is* an actual solution, should I “bug report” this? When I googled, I found all *kinds* of sites with this exact same problem – but no solutions.)
I don’t know if I should mark this “resolved” yet or not – so I’m going to leave it “unresolved” until further testing proves I actually found a fix. Hopefully, that’s okay!
Well, good thing I didn’t mark it resolved. Although the change works on my localhost server, when I uploaded and made it live, it still gives me these errors.
Still, the really odd thing is, it’s only happening to sites that are based on Blogger.com.
So if anyone has any ideas, I’d appreciate them!
I just started playing around with the build-in mini magpie and I get exactly the same error sometimes at http://www.cogmios.nl/planet. I wonder if you, after 10 months, have found at why it happens and if you are willing to share this?
