Social Features

Core platform features for user-to-user interaction: reactions (likes, favorites, bookmarks), blocking, reporting, and messaging. These are generic systems used by any interactive site -- the dating plugin and others add domain-specific behavior on top.

Reaction System

A polymorphic reaction system that works with any entity type. Supports likes, favorites, bookmarks, passes, and any other reaction type. Uses the same entity_type + entity_id pattern as EntityPhoto and ChangeTracking.

Spec: Reaction System Spec

Data Model

Table: rct_reactions

Usage

Check if a user has reacted:

require_once(PathHelper::getIncludePath('data/reactions_class.php'));

$is_liked = Reaction::has_reacted($user_id, 'event', $event_id);

Toggle a reaction (react if not reacted, unreact if already reacted):

$result = Reaction::toggle($user_id, 'event', $event_id);
// $result = ['action' => 'reacted'|'unreacted', 'reaction' => $reaction_obj]

// With a specific reaction type:
$result = Reaction::toggle($user_id, 'post', $post_id, 'bookmark');

Get reaction count for an entity:

$count = Reaction::get_count('event', $event_id);

Get all entities a user has reacted to:

// All likes
$reactions = Reaction::get_user_reactions($user_id);

// Only event favorites
$favorites = Reaction::get_user_reactions($user_id, 'event', 'favorite');

Query with MultiReaction:

$reactions = new MultiReaction(
    ['entity_type' => 'event', 'entity_id' => $event_id, 'deleted' => false],
    ['rct_create_time' => 'DESC']
);
$reactions->load();

Reaction Button (UI Component)

Drop a reaction button into any view:

// Basic like button with count
Reaction::render_button('event', $event_id);

// Customized bookmark button
Reaction::render_button('post', $post_id, [
    'reaction_type' => 'bookmark',
    'show_count' => false,
    'icon_active' => 'fas fa-bookmark',
    'icon_inactive' => 'far fa-bookmark',
    'css_class' => 'btn-sm'
]);

The button handles AJAX toggling and state updates automatically. User must be logged in.

AJAX Endpoint

File: ajax/reaction_ajax.php

Entity Types

Any entity with a primary key can be reacted to. Common types:

Messaging / Conversations

Threaded user-to-user messaging with conversation grouping, read status, and unread counts. The messaging system is a core API that any plugin can use -- for example, the dating plugin creates conversations automatically when users match.

Spec: Messaging Enhancements Spec

Data Model

Table: cnv_conversations

Table: msg_messages (existing, modified)

Added column:

Required index: (msg_cnv_conversation_id, msg_sent_time DESC) on msg_messages for efficient inbox and conversation queries.

Usage

Get or create a 1:1 conversation and send a message:

require_once(PathHelper::getIncludePath('data/conversations_class.php'));

$conversation = Conversation::get_or_create_conversation($sender_user_id, $recipient_user_id);
$message = $conversation->add_message($sender_user_id, 'Hey, are you coming to the event?');

get_or_create_conversation() returns the existing conversation if one already exists between the two users. add_message() creates the message, clears cnp_delete_time for all participants (resurfaces deleted conversations), and creates notifications for other participants (unless muted).

Create a conversation with explicit participant list:

$conversation = Conversation::create_conversation([$user_id_1, $user_id_2], 'Optional subject');

Check unread conversation count for a user:

$unread = Conversation::get_unread_count($user_id);

This is session-cached in $_SESSION['message_unread_count'] — the header icon reads from cache and only queries the database on cache miss.

Get the other participant in a 1:1 conversation:

$other_user = $conversation->get_other_participant($current_user_id);
// Returns User object

Check if a user is in a conversation:

if ($conversation->has_participant($user_id)) {
    // user can view/send messages
}

Load messages in a conversation:

require_once(PathHelper::getIncludePath('data/messages_class.php'));

$messages = new MultiMessage(
    ['conversation_id' => $conversation->key, 'deleted' => false],
    ['msg_sent_time' => 'ASC'],
    50  // limit
);
$messages->load();

Mark a conversation as read:

// Load the participant row for this user
$participants = new MultiConversationParticipant(
    ['conversation_id' => $conversation->key, 'user_id' => $current_user_id]
);
$participants->load();
$participant = $participants->get(0);
$participant->set('cnp_last_read_time', gmdate('Y-m-d H:i:s'));
$participant->save();

// Invalidate session cache
$_SESSION['message_unread_count'] = null;

Block System Integration

Conversation::get_or_create_conversation() and add_message() check for blocks before proceeding. If either user has blocked the other, a ConversationException is thrown. Plugins don't need to check blocks separately -- the messaging API handles it.

Plugin Usage

Plugins use the Conversation API directly from their own logic. For example, the dating plugin:

// In plugins/dating/logic/match_logic.php — on mutual like
require_once(PathHelper::getIncludePath('data/conversations_class.php'));

$conversation = Conversation::get_or_create_conversation($user_id_1, $user_id_2);
// Conversation is now ready for the matched users to message in

Plugins that want to restrict who can message whom (e.g., dating match-only messaging) handle that in their own routes and logic before calling the messaging API. The messaging system itself has no gating -- it's just an API for creating conversations and sending messages.

AJAX Endpoint

File: ajax/conversations_ajax.php

Header Icon

An envelope icon with unread count badge appears in the header between the cart and notification bell icons. The count is session-cached ($_SESSION['message_unread_count']) and recomputed on cache miss via Conversation::get_unread_count(). Cache is invalidated when sending, reading, or deleting conversations.

Public Routes

Admin

Settings