 |
VOOZH | about |
|
VOOZH | about |
This document describes the overall architectural design of the BuddyPress VIP Go plugin, including major components, data flows, and key architectural decisions. For detailed information about specific subsystems, see:
The BuddyPress VIP Go plugin implements a metadata-driven, transformation-on-demand architecture that enables BuddyPress media functionality on WordPress VIP's distributed file hosting infrastructure. The plugin consists of two primary components that work together to intercept BuddyPress media operations and redirect them through VIP-compatible pathways.
The architecture addresses fundamental incompatibilities between BuddyPress's filesystem expectations (local directory scanning, file locking, pre-generated image sizes) and VIP Go's distributed file hosting service (no directory listing, no flock support, CDN-backed delivery).
Sources:
The plugin implements distinct data flows for different media operations. Each flow follows the pattern of intercepting BuddyPress operations before filesystem access occurs.
Sources:
Sources:
The plugin's integration strategy relies on carefully timed filter hooks that intercept BuddyPress operations. Hook priorities and registration timing are critical to prevent filesystem operations.
Sources:
| Filter Category | Purpose | Return Pattern | Example |
|---|---|---|---|
| Early Prevention | Prevent filesystem operations before bp_init | Return empty/false before BP tries to scan | bp_core_avatar_folder_dir → __return_empty_string |
| URL Replacement | Replace filesystem-based URLs with VIP FHS URLs | Return complete URL with transformation params | bp_core_default_avatar_user → vipbp_filter_user_avatar_urls() |
| Operation Interception | Handle media operations (upload, crop, delete) | Return false to short-circuit BP function | bp_core_pre_avatar_handle_upload → vipbp_handle_avatar_upload() → false |
| Path Redirection | Redirect paths from VIP FHS to local filesystem | Return alternative path | bfu_temp_dir → vipbp_filter_chunked_upload_temp_dir() |
Sources:
The plugin stores all media information in WordPress database tables, avoiding any dependency on filesystem scanning. Different media types use different metadata structures optimized for their transformation requirements.
Avatar metadata includes crop coordinates because users can select custom crop regions. The ui_width field prevents upscaling images that were uploaded from narrow displays (e.g., mobile devices with 320px width).
Cover metadata includes only the URL because cover images use a fixed crop pattern (middle 25% vertically, full width horizontally) applied via URL parameters at render time.
Sources:
Instead of creating multiple physical image files (thumb, full), the plugin generates dynamic URLs with query parameters that instruct VIP FHS to perform transformations on-the-fly.
| Parameter | Purpose | Source | Applied By |
|---|---|---|---|
w | Clamp maximum width (anti-upscale) | ui_width from metadata | files.php223 |
crop | Crop coordinates (format: x,y,w,h) | crop_x, crop_y, crop_w, crop_h from metadata | files.php226-232 |
resize | Target dimensions (format: w,h) | $params['width'], $params['height'] from BP | files.php235 |
strip | Remove EXIF/IPTC data | Always info | files.php238 |
Original uploaded file:
https://example.com/wp-content/uploads/2024/01/avatar-12345.jpg
Transformed URL for 150x150 avatar display:
https://example.com/wp-content/uploads/2024/01/avatar-12345.jpg?w=450&crop=50px,30px,400px,400px&resize=150,150&strip=info
The VIP File Hosting Service processes these parameters server-side, caching the result in the CDN for subsequent requests.
Sources:
In WordPress multisite installations, the plugin centralizes all metadata storage on the root blog to simplify data access and avoid cross-blog metadata queries.
All metadata storage and retrieval functions check bp_is_root_blog() and call switch_to_blog() / restore_current_blog() as needed. This pattern appears in:
Sources:
BuddyBoss Platform extends BuddyPress with additional features that introduce new filesystem dependencies. The plugin includes specialized compatibility functions to handle these.
BuddyBoss's bb_get_default_custom_avatar() function uses opendir() to scan for avatar files, which fails on VIP FHS. The plugin uses a two-filter strategy to prevent this:
option_bp-default-custom-group-avatar filter (files.php941-947): Returns empty string when VIP avatar exists, preventing the condition that triggers opendir()bb_get_default_custom_upload_group_avatar filter (files.php958-966): Provides the actual avatar URL from stored optionBuddyBoss's chunked video upload requires flock() for file locking, which VIP FHS doesn't support. The plugin redirects chunk assembly to local temp directory:
bfu_temp_dir filter (files.php923-925): Returns get_temp_dir() . 'bb-large-upload'bp_core_pre_remove_temp_directory filter (files.php886-897): Uses wp_delete_file() instead of directory removalbp_video_after_save action (files.php905-907): Flushes cache after video moves to final locationSources:
The plugin relies on BuddyPress's upstream permission checks rather than implementing its own authorization layer. All media operation functions document their permission check dependency:
xprofile_screen_change_avatar() (files.php329)bp_attachments_cover_image_ajax_upload() (files.php554)xprofile_screen_change_avatar() (files.php657)Files are stored in VIP FHS with standard WordPress upload permissions. VIP's security model controls access through its file hosting infrastructure.
Sources:
Refresh this wiki