xProfile: prevent duplicate profile field templating when using pre-2.0 custom field types.

Prior to the xProfile field type overhaul in 2.0, plugins that added custom field types had to do so with a variety of actions.
One such plugin is "Buddypress Xprofile Custom Fields Type" and the changes in 2.0 caused an issue where the plugin's custom
templating was being rendered, alongside BuddyPress' profile field fallback type, the textbox.

BuddyPress uses a fallback field type to handle situations when extra profile types/data are provided by another plugin, and
then that plugin is removed. The original idea was that everything would fallback to rendering a textbox if a field type was
unregistered to give at least some kind of access to that profile field's data, but in practice this has caused a couple of
issues with templating, as this commit addresses.

This change essentially reverts the fallback behaviour to the pre-2.0 implementation: if a custom field type is unknown to
BuddyPress, that field simply won't be rendered.

Fixes #5589

git-svn-id: https://buddypress.svn.wordpress.org/trunk@8336 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
xProfile: fix profile field validation messages not showing on registration template.

Fixes #5595, props r-a-y

git-svn-id: https://buddypress.svn.wordpress.org/trunk@8338 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
Only load the activity just posted when on a user activity page

HeartBeat activity check feature introduced a "since" argument to load the activity that are newest. In a user activity page, this feature is not used but a timestamp is created using a "0" value causing all user activities to be reloaded. Checking if the value is empty before creating the timestamp will make sure the activity just posted will be the only one loaded into user stream.

props boonebgorges, imath

See #5603

git-svn-id: https://buddypress.svn.wordpress.org/trunk@8341 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
Blogs: Add check for activity component when recording a post comment.

Previously, if the activity component was disabled and the blogs component
was enabled, if a user posted a blog comment, a WSOD would occur.

This commit fixes this by adding a check for the activity component in
the bp_blogs_record_comment() function.

See #5606 (trunk)

git-svn-id: https://buddypress.svn.wordpress.org/trunk@8343 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
Blogs: Formatting improvements for activity comments connected to blog comments.

This commit:
- Readjusts the permalink for singular activity comments connected to blog comments to use the comment permalink instead of the activity thread permalink
- Readjusts the activity action for singular activity comments connected to blog comments to use the familiar blog comment action instead of the generic "posted an activity comment" action

See #5560 (trunk)

git-svn-id: https://buddypress.svn.wordpress.org/trunk@8345 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
Ensure that the BP_XProfile_Field_Type_Placeholder class has a validation regex

This ensures that any value will pass the is_valid() test for this field type.

Fixes #5589

git-svn-id: https://buddypress.svn.wordpress.org/trunk@8347 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
Allow some HTML in the copy of the latest activity update displayed in member header

We pass the saved value through the activity-specific kses filter, which
contains a whitelist of allowed tags. This makes for a more consistent
experience.

Fixes #3374

git-svn-id: https://buddypress.svn.wordpress.org/trunk@8351 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
Grunt: move everything into `/src/`.

This commit is part of a series that will re-organise BuddyPress trunk to use a Grunt build process. See #5160


git-svn-id: https://buddypress.svn.wordpress.org/trunk@8352 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
Grunt: remove bbPress 1.x external

This commit is part of a series that will re-organise BuddyPress trunk to use a Grunt build process. See #5160


git-svn-id: https://buddypress.svn.wordpress.org/trunk@8353 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
Grunt: rename unit tests folder to `phpunit`.

It'll be moved back into a `tests` folder in the next commit.

This commit is part of a series that will re-organise BuddyPress trunk to use a Grunt build process. See #5160


git-svn-id: https://buddypress.svn.wordpress.org/trunk@8354 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
Grunt: move phpUnit tests into new, top-level `tests` folder.

This commit is part of a series that will re-organise BuddyPress trunk to use a Grunt build process. See #5160


git-svn-id: https://buddypress.svn.wordpress.org/trunk@8355 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
Grunt: add first pass at Grunt build script.

This commit is part of a series that will re-organise BuddyPress trunk to use a Grunt build process. See #5160


git-svn-id: https://buddypress.svn.wordpress.org/trunk@8356 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
Grunt: move phpUnit config file into root folder.

This commit is part of a series that will re-organise BuddyPress trunk to use a Grunt build process. See #5160


git-svn-id: https://buddypress.svn.wordpress.org/trunk@8357 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
Grunt: add jshintrc and gitignore config files.

Taken from bbPress trunk.
This commit is part of a series that will re-organise BuddyPress trunk to use a Grunt build process. See #5160


git-svn-id: https://buddypress.svn.wordpress.org/trunk@8358 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
Grunt: sync svn:ignore property with `.gitignore`.

This commit is part of a series that will re-organise BuddyPress trunk to use a Grunt build process. See #5160


git-svn-id: https://buddypress.svn.wordpress.org/trunk@8359 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
Grunt: sync `.gitignore` against SVN's svn:ignore property.

Now, both are finally in sync. :)

This commit is part of a series that will re-organise BuddyPress trunk to use a Grunt build process. See #5160


git-svn-id: https://buddypress.svn.wordpress.org/trunk@8360 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
Grunt: remove svn:ignore property from `tests/phpunit/` for `phpunit.xml`.

This was an artifact of pre-2.1 versions of BuddyPress where the unit tests folder lived at the root
level of the project, and so we needed to support ignoring custom phpUnit build files.

The root `trunk` folder now has an ignore for `phpunit.xml`, and that's where custom phpUnit build
files should be placed going forwards.

This commit is part of a series that will re-organise BuddyPress trunk to use a Grunt build process. See #5160


git-svn-id: https://buddypress.svn.wordpress.org/trunk@8361 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
Grunt: remove `backpress` svn:ignore external from the `bp-forums` component.

Trunk no longer has an external of the old 1.x version of bbPress. See r8353.

This commit is part of a series that will re-organise BuddyPress trunk to use a Grunt build process. See #5160


git-svn-id: https://buddypress.svn.wordpress.org/trunk@8362 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
Grunt: add first pass at loader file for sites running `trunk`.

This commit is part of a series that will re-organise BuddyPress trunk to use a Grunt build process. See #5160


git-svn-id: https://buddypress.svn.wordpress.org/trunk@8363 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
Core: remove unused, SVN-only, `$Id` tag from the main file's headers.


git-svn-id: https://buddypress.svn.wordpress.org/trunk@8364 cdf35c40-ae34-48e0-9cc9-0c9da1808c22