jimgroom

Well, thanks to the great Ron Rennick this issue has already been solved on Twitter. Long and short of it, I did not update the SharDB plugin to the latest version, 2.8.1. Once that was updated the issue was fixed, I am happy to report.

Thank you, Ron, you are as clutch as I am lame.

@RichardHelms,
I just wanted to say thanks for taking the time to share your fix. it worked. You rule!

Excellent,

Thanks for the cookie for comments suggestion. I’ll be trying that out shortly.

Andrea,

There was a space at the bottom of both the typepad antispam and pluggable PHP files, but when I removed that spaces the error is still there. Curtiss had an idea that would change the code on line 225-227 of the TypPad Antispam code, and that removed the error but comments went directly to spam without moderation or anything.

Andrea_r,

I am checking now, and you are amazing—how did I know you would respond here? What would the WP community do without you?

*Bump*

Having the same issue, and I am wondering if it has something to do with OAuth support for PHP. WP Support center breaks down Twitter Tools pretty nicely here:
https://wphelpcenter.com/plugins/twitter-tools/

And While I’m not certain, I am gonna run that fix by my server admin and see if that might be a possible solution.

More soon.

@andrea_r,

Once again you rule, and so you know, we submitted the request to our server admin like this:

Could you please modify apache configuration on umwblogs.org
<https://umwblogs.org&gt; so that the domain share.teachumw.org
<https://share.teachumw.org&gt; has a virtual host declaration that points
to this folder /home/umwblogs/public_html/share

Sometimes sharing the terminology of how to ask can be just as helpful as understanding something, which i don’t claim to ??

Figure anything out here? I am running a multi-db setup using the SharDB plugin, and I got the same exact error after I copied the WP 3.0 core files, and tried upgrading the database. Was under the impression the dp.php file was working for this plugin, but I maybe missing something. Reverted back to WPMu 2.9.2 for the moment, but any help would be great.

jim

So, there shouldn’t be an issue with SharDB in this regard? Good to know, I guess I am gonna experiment with this upgrade and see what comes of it. I do everything in production, so I’m sure I’ll be back here soon ??

Thank you both.

Andrea,
Maybe the takeaway should be “Don;t try this at home, kids,” especially when you are ignorant like me ??

This is resolved, seems like the wp_x_options table in one of her blogs was filled with transient Magpie feeds, probably caused by the post syndicator we used to use (BDP RSS). The options table alone was 95 MBs, and once I cleaned that out her blogs showed back up—who knew? ??

Andrea,
Hahaha, yeah picture is woth a thousand unclear words—plus I always love an image in my posts ?? It does cut off the rest of the users on that page, luckily I deleted a test user and made her’s the 15th on page 1, so it prevents more collateral damage (it was screwing up 14 other users when it was the first entry on page 2).

Sorry to bother everyone here, looks like it was a theme issue. Seems to have been totally resolved once I deactivated the theme.

I imagine you saw this coming, but I would love to see some sophisticated syndication options built into WP/WPMu which would allow people to easily integrate a wide range of feeds of their various online work from numerous sources that are RSS ready into their blog. In many ways completing the circle of the blog as aggregation point. FeedWordPress does this quite well now, but having it as part of the core and regularly developed would make a lot of sense given where WordPress is headed.