BP Legacy stopped filtering activity heartbeat requests

[imath]

Work achieved in #9099 introduced a regression about Legacy template pack. See:
​https://buddypress.org/support/topic/buddypress-group-load-newest-activity-bug/

Reason: the BP Legacy main JS file is not sending a bp_heartbeat post data, as a result the request is not parsed and BuddyPress URI globals neither.

Make sure bp_heartbeat post data is sent and use to transport cookies BP Legacy uses to remember logged in user's navigation preferences.

Trac ticket: ​https://buddypress.trac.wordpress.org/ticket/9248

[imath]

In 14062:

BP Legacy: load newest activities according to displayed context

Make sure the bp_heartbeat property is included into the sent Heartbeat data object & use it to transport the cookies BP Legacy uses to remember logged in user's navigation preferences.

The bp_heartbeat property is needed to be sure the current Heartbeat request is about BuddyPress and needs to be parsed using the BP Rewrite API since [13752]. This parsing job analyses the current URL to define the value of BP URI globals such as the current displayed single item.

Props dreampixel

Fixes #9248
Closes ​https://github.com/buddypress/buddypress/pull/393

[dcavins]

In 14083:

BP Legacy: load newest activities according to displayed context

Make sure the bp_heartbeat property is included into the sent Heartbeat data object & use it to transport the cookies BP Legacy uses to remember logged in user's navigation preferences.

The bp_heartbeat property is needed to be sure the current Heartbeat request is about BuddyPress and needs to be parsed using the BP Rewrite API since [13752]. This parsing job analyses the current URL to define the value of BP URI globals such as the current displayed single item.

Props dreampixel

Fixes #9248. (14.0 branch)