Daniel J. Lewis

Thank you for sharing this fix! It worked for me on two different sites.

THANK YOU! I just ran across your post while trying to solve the problem that was showing up with a conflict over Gravity Forms.

Adding this line also seems to further fix the comment issue with Facebook like:

.fb_edge_comment_widget { width: 400px;}

It would be nice is the sizing affected the sidebar widget, too.

No. I had expected that the developer reads these forums.

Any update to this? I’m interested in the same thing, but add to this that I have WordPress Multisite/Network and want bbPress on one subsite.

Right now, I can’t even get SFC to appear on the default site’s sign-up page.

Well, I can tell. I posted two podcast episodes yesterday, each to a separate site on my WordPress 3.3.1 Network. On one site, I had to refresh the cache to remove the widget. That site’s episode was available in the RSS feed.

But on the other site, where I actually posted first around 10:30 last night, the feed still wasn’t updated nearly twelve hours later!

This is unacceptable, and it’s a waste of the cache to have to refresh it every time I post something new. So I’m going to switch to WP Super Cache.

I can’t quite tell. I forgot to check when I published a new post, but it did show up in the RSS feed overnight. But I also think I remember refreshing my cache anyway after moving a widget (which doesn’t always refresh that cache on its own).

It could be that W3TC is being very slow at updating the RSS cache.

The instructions are poorly written. I’m new to this, but it’s impossible to go to the “WP phpBB Bridge” menu without activating the plugin.

Thanks for that. It fixed the problem with ShareBar, but it’s still grabbing text that shouldn’t be there. This time, it’s grabbing the PowerPress podcasting plugin text.

<meta property='og:description' content='Podcast: Play in new window | Download ACTUAL EXCERPT HERE.' />

Perhaps SFC is pulling from the_excerpt too late in the filter chain?

Thanks for popping in here, Otto. If SFC is really pulling from the excerpt, then how is it capturing stuff like ShareBar from the post? Sharebar doesn’t appear in the excerpt or even on the front page where the excerpts would be listed. Sharebar is only within the post.

Extesy, I did look carefully and that’s why I wrote my post carefully. W3TC only writes domain-specific information if you have those options checked. One of them is “Cache requests only for [domain] hostname” in Page Cache > General Settings. If I disable that on all of my WordPress Network sites and ensure all the settings are exactly the same, I don’t get any .htaccess conflicts.

nicoleb, can you mark this unresolved? zvhipp’s suggestion is nice, but it doesn’t fix the real problem.

I’d rather not start a duplicate post on this issue.

That’s not a fix, that’s a workaround. Having the word “Tweet” in the tweet button is very important for accessibility.

This problem is actually amplified if you have any other social buttons, like +1, Stumbleupon, and even Facebook buttons.

The real problem is that SFC is pulling the og:description tag from the _content_ of the page, not the written excerpt, as its documentation makes it seem.

I came to these forums to finally report this problem, too. Are we all running WordPress 3.3? This RSS caching issue showed up after I upgraded.

I’m running WordPress Network. Anyone else?

I’ve had to force refresh my cache whenever I publish a new post. It’s terrible. And I’ve had the same settings that I had in WP 3.2.

W3TC just may not be compatible with WP 3.3 yet.