New features

Note: If you are updating from a previous version of Features You MUST run update.php before Features will begin automatically rebuilding feature components when safe to do so. This is not necessary for new installations.

This release of Features contains a lot of new features and many changes to the internals for rebuildable components. There are no major API changes but as always please test thoroughly in a staging environment before rolling out beta4 to production sites.

Great job by all the patch contributors and users who provided bug reports and feature requests.

- #616222: Moving conflict detection API functions into module proper.
- #520220: Allow modules to be ignored when cleaning up dependencies.
- #597330 by fago, fixed display of rule names in feature building ui.
- #616222 by q0rban: API function for installing maximum dependencies of modules/features.
- #606992 by dmitrig01: Human readable names for feature components.
- #612824: Proper handling of rebuildables & component reverting. Reported by greggles, Roger Saner.
- #616030 by q0rban: Simplify access check against features administration pages.
- #597836: Remove form_alter() which hides features from admin/build/modules.
- 3 stage state signature handling.
- #597422 by Roger López: Consistify user permission, role sorting.

- RFI attacks from 'https' and 'ftp' sites are now included in the report
- Added bar chart for displaying top 10 RFI attack hosts
- Disabled sorting on 'Domain' and 'Script name' headers in RFI report (derived results sorting is not possible)
- Added the swf sourcecode to the module enabling complete distribution of module and charting components

The 2.x branch of Facebook-style Statuses is a complete rewrite which offers a very wide array of new features. It is very stable; everyone is encouraged to upgrade to this version. Please review the extensive documentation to learn more about what this module offers, especially if upgrading from a previous version.

Upgrade Notes

• Everyone should run update.php after upgrading to this release.
• If you get an error about not finding the {facebook_status_tags} table while upgrading, you can safely ignore it -- I accidentally put some upgrade code in the wrong file. (See this issue)
• Some views have changed. To adopt the changes, go to /admin/build/views and click "revert" next to the default Facebook-style Statuses views. There is also a new "Re-post" field that is not implemented in any default view, but which you may want to add yourself.
• New settings have been added. You should review your settings after upgrading, and also check out the documentation.
• New features have been added. You should review the documentation to get the full picture.

#623012 - Added wildcard (*) option for "Enforceable pages" field.
#545582 - Removed anonymous role from "User role" field options.
SA-CONTRIB-2009-106 - Agreement - Cross Site ScriptingUpdated output of module settings fields to use check_plain().

This release fixes minor bugs and adds new features and a completely new installation procedure. No more copying folders and editing Wysiwyg module files.

#625276: Make use of hook_wysiwyg_plugin
#585450: Wrap link around text rather than using title from views listing
#584436: Automatically load template files from module directory
#584504: Make JS external & fix inserted links for non-root installations

Known Issues:
#629682: Error message on new install. - Annoying bug that does not effect how boost works.
#631452: Table doesn't exist in multisite setup
#630174: warning: md5() expects parameter 1 to be string, array given in /site/sites/all/modules/boost/boost.module on line 1921

This should be an awesome release. Please report any bugs or WTF's you encounter.

Notes:
I was able to identify a bug with the FieldAPI so the beginning part of the buttons on the boost page have a number added to them as a way to get around the bug; or at least identify when Drupal is screwing up, and prevent the wrong operation from taking place.
The flush button will now say flush or expire based on your settings. If that page is already expired then it will always say flush.
You can now leave the url_alias option turned on in the crawler and it will be smart about what url's it crawls.
Multi site flushing works a lot better now.
301 redirects are now killed from the cache (404 & 403 where already taken care of).
Overwriting of the cache is no longer required for "Do not flush expired content on cron run, instead recrawl and overwrite it" to work. This BTW is a huge win for performance.

Bug Fixes:
#621668: Large Websites & boost_tree_directory() function don't play along
#621870: Set time limits when dealing with the file system
#623784: Gzip corruption when saving data-stream if using pressflow and built in cache and boost at the same time
#623578: boost_stats.php & drupal_json missing
#623516: Based on settings have flush button say flush or expire
#623536: Expiration validation (be smart in short)
#624026: Make the "Flush all sites caches in this database (singe db, multisite)" work better
#625014: boost_cache_kill() is very database intensive
#625962: _boost_index_exists should grab Column_name instead of Key_name
#626634: Call time pass by reference...

Feature Requests:
#623540: Allow setting of url import bulk size
#478644: Cache file path shouldn't be stored in the DB by default
#613926: Better url_alias behavior in crawler
#627844: Kill old paths from cache if a 301 was given
#629470: Set boost tag in header