Downloads

Download tar.gz 91.4 KB
MD5: c89a12e55adab810afff4ef044e480c0
SHA-1: 45d390e812d372b6422ea44496437282726b4244
SHA-256: 248366f4efda60f7193729997d6c09eedd3ab97b125a5e07e06a970e61799960
Download zip 145.73 KB
MD5: 6cb92c178f5e49598ac1951dd54ca309
SHA-1: 47e74626cb4baa3aadbd0a04607f423169a37a92
SHA-256: dbc990c5a2eb7e6034183344c3322686f50f728704cb140881aedc5511bb4142

Release notes

This is the first stable release of the 6.x-3.x branch. This branch is now recommended over the 6.x-2.x branch for new sites.

From 6.x-1.x and earlier

Upgrading is only supported between adjacent branches. For example, if you are on 6.x-1.x, you must first upgrade to the latest 6.x-2.x release before upgrading to 6.x-3.x.

From 6.x-2.x

Major improvements from the 2.x branch

  • Groups and other nodes can now have their own status streams.
  • Status comments are now part of the core package instead of living in a separate project.
  • Many new integrations have been added, and many of the old ones have been improved.
  • Cleanup and standardization of the API and HTML/CSS.
  • Better performance due to moving integrations into submodules and only loading resources as necessary.
  • Many less significant changes designed to provide a smoother experience for the user and increased flexibility for the administrator.

Upgrade Steps

  1. Make a backup of your database.
  2. If you have FBSMP or FBSSTS installed, disable them.
  3. If you have custom Views for status updates or if you have overridden the default Views provided by the module, back them up and then delete them.
  4. If you have custom Rules/Rule sets, Triggers, or Activity templates that use FBSS-related actions or events, back them up and then delete them.
  5. Delete the entire facebook_status directory from your site's "modules" folder.
  6. Upload the new facebook_status directory for the 3.x branch to your site's "modules" folder.
  7. Run update.php. If you are upgrading to 3.0-RC2, updates 6302 and 6303 will fail, creating errors about duplicate columns. You can safely ignore this. The problem is fixed in the development build.
  8. Most integrations with other modules have been moved to submodules. FBSS will detect if you were using those integrations with the 2.x branch and automatically enable the relevant submodules. However, you should go to admin/build/modules and review which submodules are enabled to ensure that the ones you want to use are enabled. (There are also some new integrations you may want to enable.)
  9. Check the FBSS permissions and make sure they are set up the way you want.
  10. If you want, review the settings at admin/settings/facebook_status.
  11. If you need to, re-create your custom Views/Rules/Triggers/Activity templates.
  12. Check your site's links and make sure they still point to the right places. Some URL paths have been changed (probably most significantly, share-status is now /statuses/share).
  13. Review any custom (FBSS-specific) CSS, JS, or theme overrides your site has added to make sure it still works with the new markup.
  14. Configure any settings with integrations you are using. For example, you may want to configure Pathauto settings for status update pages, or the amount of Userpoints users receive for posting status updates.

From 6.x-3.0-beta2

There are over 60 bug fixes and feature improvements from Beta 2. The highlights include adding and improving a lot of integrations, making stream contexts more flexible, adding the "view own comments" permission, and fixing plenty of bugs. Perhaps the most exciting new integration is with the Services module, which provides a public-facing API so that (phone/desktop/web) apps can integrate with your website.

You must run update.php after upgrading from 6.x-3.0-beta2 to 6.x-3.0-RC2.

Created by: icecreamyou
Created on: 27 May 2011 at 16:32 UTC
Last updated: 30 Aug 2011 at 02:50 UTC
New features
Bug fixes
Unsupported

Other releases