Sorry for the several updates over the last day. Somebody pointed out that I hadn’t pushed a new version of SFC in several months, and that the fixes in trunk had gotten a ways ahead of those in the released version. Unfortunately, I didn’t actually go and test properly, so versions 0.22 and 0.23 had minor but critical bugs in them. Version 0.24 should push shortly with the fixes for those bugs as well as the enhancements over the last several months.
A short list of the changes/fixes:
- Thanks to Burak Tuyan, the whole plugin is now more i18n capable, for people who want to translate it.
- Added an sfc_img_exclude filter, to let others add their own image classes to exclude from the automatic image finder for share and publish and such.
- The sfc_like_button() functions now supports a url parameter to add a like button to a specific URL.
- A couple of patches by Jamie Zawinski: Publish now sends up to 1000 chars from the post to Facebook.
- Also thanks to jwz, publish now gets images correctly in more cases.
- If you enable login avatars (by uncommenting that code), it will show them for comments now too.
- Eliminated deprecated calls to Facebook functions (xid and register users calls)
- Custom Post Type support for automatic publishing (any CPT with public=>true will get auto-published).
- Custom Post Type support for manual publishing (any CPT with public=>true will show the meta box in its edit screen).
- Contextual help added to SFC Settings page.
- Improved error messages
- Numerous other minor optimizations and bugfixes
Version 1.0, which will ditch the old Connect code entirely, isn’t quite ready yet. The new registration stuff will be in there though, eventually. It will probably be after I get back from the core developers meeting though. Sorry for the excessive delay on that. I know lots of people want it, I never seem to have the time. I’ll try to find the time and finish it up soon. Really.
Note to users: If you got the “Breaking change: API deprecations” email from Facebook today, then you are probably using the SFC-Login plugin, or have at some point. Version 0.24 removes the code they are deprecating from the SFC-Login plugin. So upgrade and you’ll be fine. However, note that SFC is no longer compatible with WordPress versions prior to 3.0. Upgrade WordPress to 3.0 or later before upgrading SFC.
Note to international users: And with all that, there’s still a bug. If you’re seeing weird characters in your FB Published posts, edit the sfc-publish.php file. On line 179 you’ll find
return utf8_encode($text);. Change it to
return $text; to fix the problem with the double encoded characters. The next version will have this fix as well, but I didn’t think it was major enough to push a whole new version right away.