public function HeartbeatAccess::skipActiveUser in Heartbeat 6.4
Skip active user. Return whether you want to skip the active user (being the logged-in user and NOT the displayed user) from display. Typical private will not skip this one ofcourse where most other will skip active user since you don't want to watch your own activity.
5 methods override HeartbeatAccess::skipActiveUser()
- GroupsActivity::skipActiveUser in modules/
og_activity/ groupsactivity.inc - Skip active user. We never want to skip the active user.
- MembersActivity::skipActiveUser in modules/
og_activity/ membersactivity.inc - Skip active user. We never want to skip the active user.
- OgHeartbeat::skipActiveUser in modules/
og_activity/ ogheartbeat.inc - Skip active user. We never want to skip the active user.
- PrivateHeartbeat::skipActiveUser in includes/
privateheartbeat.inc - Skip active user. We never want to skip the active user. not for logged-in user and not for displayed user (profile). This is ofcourse because private stream is intended to show own activity.
- SingleHeartbeat::skipActiveUser in includes/
singleheartbeat.inc - Skip active user. We never want to skip the active user. not for logged-in user and not for displayed user (profile). This is ofcourse because private stream is intended to show own activity.
File
- includes/
heartbeataccess.inc, line 76 - HeartbeatAccess object is the object that takes stream configuration to create a stream of activity objects. It is the controlling organ at the pre-query, query and post-query phases.
Class
- HeartbeatAccess
- Abstract class heartbeataccess This base class has final template methods which are used by the derived concretes. The HeartbeatAccess is a state object that is given to the HeartbeatMessageBuilder to set the access to the current request.
Code
public function skipActiveUser() {
$skip = $this->_whoisuser_type == self::TYPE_USER_PROFILE ? FALSE : (empty($this->stream->skip_active_user) ? FALSE : $this->stream->skip_active_user);
return $skip;
}