Releases for Facebook-style Statuses (Microblog)

This release is recommended for everyone. It resolves a number of bugs in the 3.0-RC3 release and makes the experience more intuitive. With this release the focus is now moving to the D7 branch, which has moved to the Statuses namespace.

If you are also using the Facebook-style Micropublisher module, you should upgrade to an FBSMP release from November 25, 2011 or later.

Upgrade Notes from 6.x-3.0-RC3

• Make sure to run update.php after upgrading.
• The default Views have changed. In order to see these changes, you may need to refresh the Views cache at admin/build/views/tools. If you have edited the default views, your changes will not be overridden.
• There are some significant theming changes. If you've done any custom theming, you may need to rework some of it. The most important changes are:
• The markup for statuses in the default FBSS views has changed to match the markup that FBSS outputs on individual status pages.
• The CSS styles for the status update form and the status comment forms have changed. Classes have been added to make this easier.

Upgrade Notes from 6.x-2.x and earlier

If you are upgrading from a release earlier than 6.x-3.0-RC2, please read the 6.x-3.0-RC2 release notes for steps you must take to upgrade.

The 2.x branch of FBSMP requires this release or a later one.

This is mostly a bugfix release and hopefully the branch point for 7.x development.

Upgrade notes from 6.x-3.0-RC2

• There are some changes to the form structure and HTML/CSS markup that could affect custom theming.
• The default Views have changed. If you've customized your views and you're happy with them, there's no need to do anything.
• If you have User Relationships installed and you've never changed the settings at admin/settings/facebook_status/contexts, FBSS will now show your relationships' status updates as well as your own when you view your own stream. If you have UR installed and you have changed those settings but you still want that behavior, you now have the option to set different Views for your own status stream and other users' status streams at admin/settings/facebook_status/contexts/user.

This should be the final release of the 6.x-2.4 branch. I consider it extremely stable; after over 2 years of development and testing by thousands of sites, there are no bugs that I am aware of at the time of release. Changes from 6.x-2.3 mostly include bug fixes.

Changes from 6.x-2.3

Input filters should not run the access check when statuses are viewed
#860688 posts on wall of users with a hyphen (-) in their name don't show
#854906 flag.js : context.find is not a function by cookie235
#863724 Undefined offset errors in facebook_status.module by cpliakas
#866506 Use keydown or keypress instead of keyup event for character counter
#874108 Escaped characters in Views RSS style plugin for statuses (thanks d4rkngel)
#875924 Flags on statuses not being deleted (thanks d4rkngel)
#895136 Receiving Error: unserialize() expects parameter 1 to be string
#932336 Any ideas? notice: Undefined index: sid in facebook_status.module on line 456 (thanks mbergenlid)
#952486 patch for twitter 3.x to work (thanks jlporter and d4rkngel)
#874108 Escaped characters in Views RSS style plugin for statuses by d4rkngel
#806004 [owner] = [poster] ? by 5t4rdu5t
#1063392 Plaintext filter runs over username link in "does not have a status" message
Issue #1120766 by IceCreamYou: make the $exclude_blank parameter of facebook_status_get_status() work when false

Whoops! This release got messed up. Please see 6.x-3.x-beta2 instead.

This release is the branch point; after this I will be working on the 3.x branch, which requires rewriting extensive portions of the module. I consider this release extremely stable. It adds some minor features, but it is mostly a stability/bug-fix release that is recommended for everyone.

Notes

• If you skipped the 2.2 release, make sure you read the release notes.
• FBSS now supports the jQuery Autogrow plugin so your status update boxes can grow as the user types, like on Facebook. (This is really only useful if you allow more than 140 characters in a status.)
• It is now possible to set the text of the "Re-post" link in the View field. This change makes "Share" the default text (previously "Re-post" was the default text). The "Re-post" field is not in any default Views, so this only affects people who have manually added it.

Changes from 6.x-2.2

#811646 Some problems after update to 2.2
#814168 Missing views-view-row-rss.tpl.php
#815996 Fatal error while trying to edit a status (accidental Pathauto dependency)
#795616 Clone the share-status page and its cool behavior?
Better handling for facebook_status_mentions view
#823050 Improper token array in facebook_status_token_list() by Dave Reid

This release is the first stable release to work with the Facebook-style Statuses Comments module, which allows commenting on statuses.

Users upgrading from 5.x should first upgrade to FBSS 6.1 before moving to 6.2.

Upgrade Notes

• Everyone should run update.php after upgrading to this release.
• New settings related to new features have been added. You should review your settings after upgrading, and also check out the documentation.

Changes since 6.x-2.0

Bolded changes add or remove settings or major features. These changes could affect the way your site uses Facebook-style Statuses. Emphasized changes indicate less important changes that may offer new opportunities for your site should you actively choose to take advantage of them. Developers should pay attention to underlined changes.

#634784 Added a killswitch to use a non-UTF8 version of FBSST tag matching for people without UTF8 support in PCRE
Temporarily removed support for hyphens in tags in FBSST because Views doesn't support them
Share-status page now can show a view of latest statuses as well
Fixed Poster name always shows up as link to profile in Views

Facebook-style Statuses is officially stable. Please review the extensive documentation to learn more about what this module offers.

Why use 2.x?

The 2.x branch of Facebook-style Statuses is a complete rewrite which offers a very wide array of new features. Read the documentation to get the complete picture, but here are a few of the most important features new to 2.x:

• AHAH-based status submission
• Extensive integration with other modules
• Users can post on each others' profiles like on Facebook
• Users can make @userreferences and use #hashtags like on Twitter
• Users can "like" statuses like on Facebook or "follow" other users like on Twitter
• Complete, easy API (including theme functions)
• Cleaner, more useful, easier-to-use User Interface
• Highly customizable through the settings
• Optional Open API, allowing other sites to see your users' status updates
• ...and much, much more.

Upgrade Notes

• Everyone should run update.php after upgrading to this release.

This should be the last beta release; the next stable release will probably be a Release Candidate. Activity integration is probably broken in this release.

Upgrade Notes

• Run update.php immediately after upgrading.
• Most default views probably require the PHP Filter module to be enabled.
• If you have problems with your views, go to admin/build/views and click "Revert" next to each view where that option is offered.
• If you were using the facebook_status_convo view from Beta 3, you should delete it; it was replaced by facebook_status_mentions.
• You should review the module's settings at admin/settings/facebook_status and admin/settings/facebook_status/advanced as well as the module's permissions at admin/user/permissions#module-facebook_status
• New views were added and one Views-generated block was removed.
• The "edit own status" and "edit all statuses" permissions now also give permission to delete the relevant statuses.

Changes from 6.x-2.0-BETA3

This release adds a number of major features. Important changes are emphasized; very important changes are bolded.

Shortened the time after posting a status in which the next status will overwrite the previous one from 12 to 10 seconds

You must run update.php if you are upgrading from any previous version.

There is an API change from Beta 1: the $status parameter of theme('facebook_status_item') must be an object or NULL.

See the Beta 1 release notes for more information.

Please see the extensive documentation to learn about what this module delivers.

Changes from Beta 1:

Fixes AHAH submission so this branch is now fully usable and probably stable!

This is probably the last alpha release, unless a critical issue is found before beta. Do not use on production sites without testing, but everyone else should use this.

These things will be done before beta:

From Alpha 1, fixes an unintended dependency on the core Trigger module.

===========================

NOT RECOMMENDED FOR PRODUCTION SITES. Definitely recommended for developer/non-production sites. Developers upgrading from dev releases before Alpha 1 (and certainly those upgrading from 1.x) need to run update.php after upgrading to this version.

Known bugs:

The 2.x development branch. Upgrade to this if there is a newer dev release than official release before filing bug reports. It's usually stable.

This release should be very stable.

Fixed/new from the last RC:
JS won't allow empty status to save
Status on profile
Unclosed <a> for non-editable statuses

#369052 Reset form on click (with inspiration from dave_trigeia)
#381702 Token conflict
#380648 Cleared statuses show in Activity
#314950 Activity 6.1/5.4 integration
#371074 Author pane integration problem?
#341360 Better cleared status text

Upgrade Notes
- Some strings have been changed. This will affect translations.
- The tokens used for Activity messages have changed.

Fixes a number of issues from Beta 1:
#365849
#374057
#334063
#363814
#362699
...among others.

All non-postponed issues in the queue relevant to the 5.x branch have been fixed, so this release should be stable. However, the fixes have not been heavily tested, which is why this is only a beta release. In a few weeks if there are no major issues with this release I will create an official 1.0 release.

Fixed from the November 23rd dev release: