Developer Overview
BuddyPress Status stores all data in WordPress options and user meta — there is no custom database table. The plugin registers a small set of filters and one action that let you change behavior without modifying plugin files.
Data Storage
Section titled “Data Storage”| Data | Location | Key |
|---|---|---|
| General plugin settings | wp_options |
bpsts_gnrl_settings |
| Admin-defined feeling activities | wp_options |
bpsts_feeling_activities |
| Admin-defined global status list | wp_options |
bpsts_global_statuses |
| User’s active status text | wp_usermeta |
bpsts_user_status |
| All saved statuses for a user | wp_usermeta |
bpsts_user_all_status |
| User’s selected mood type | wp_usermeta |
bpsts_user_mood_type |
| User’s selected mood value | wp_usermeta |
bpsts_user_mood_value |
Core Files
Section titled “Core Files”| File | Purpose |
|---|---|
buddypress-status.php |
Plugin bootstrap, constants, version |
includes/class-buddypress-status.php |
Main orchestrator class; loads hooks and theme-support filter |
includes/buddypress-status-general-functions.php |
All public helper functions and every filter/action |
includes/buddypress-status-emoji-data.php |
Unicode emoji data array and its filter |
public/class-buddypress-status-public.php |
Frontend rendering and AJAX handlers |
admin/class-buddypress-status-admin.php |
Settings page and option registration |
Extension Points
Section titled “Extension Points”The plugin exposes 8 filters and 1 action. See Hooks and Filters for full signatures and examples.
A localized JavaScript object (bpsts_ajax_object) is available on every page that loads the plugin’s public script. See JavaScript API for its properties.
Frontend markup uses a predictable set of CSS classes that you can target for styling. See CSS Classes for a grouped reference.