Add support for "current_theme_supports"

[GIGALinux]

This patch adds support for the function current_theme_supports which is introdruced with WordPress 2.9. The user gets a warning if the current theme used is maybe incompatible with BuddyPress. The user gets the possibility to dismiss the message.

[jason_jm]

Going to try and test this tonight

[jason_jm]

This is working for me.

BTW, this code is beautifully written.

A compliment like this doesn't come often if ever from me.

[jason_jm]

This is working for me = tested

[GIGALinux]

Thanks for testing and the compliment, but thats only the WordPress coding standards ;-)
​http://codex.wordpress.org/WordPress_Coding_Standards

[jason_jm]

Yup! And code is poetry :-D

[DJPaul]

I thought something like this was in 1.2 but I can't find it quickly. Bumping to 1.2.1 for further review.

[DJPaul]

We ought to use this instead of the technique used in bp_core_activation_notice(). We can set it in bp-default and hopefully child themes will inherit it.

[DJPaul]

Feedback appreciated if we want to do this?

[DJPaul]

The idea of switching the theme nag to current_theme_supports() is an interesting one; what else could BP do if it checked for support?

However, the approach in this patch is unsuitable as it would add (yet another) option to the blog options table, which is why BP check if a constant is set in the current implementation.. We need to be consolidating these, not adding more.

[DJPaul]

Marking this as resolved as it was implemented with recent commits r5747 and r5749