Plugin Initialization and Environment Detection

This document explains how the BuddyPress VIP Go plugin detects the WordPress VIP Go hosting environment and conditionally loads its integration layer. For details on what the integration layer does after initialization, see Core Integration Layer (files.php). For installation requirements and activation order, see Installation and Configuration.

Overview

The plugin uses a defensive initialization strategy to ensure it only activates on WordPress VIP Go environments where the necessary infrastructure is available. The entry point `buddypress-vip-go.php` performs environment detection before loading the core integration logic in `files.php` This conditional loading pattern prevents the plugin from interfering with non-VIP BuddyPress installations.

Sources: buddypress-vip-go.php1-35

Entry Point and Plugin Structure

The plugin consists of two primary files:

File	Role	Lines	Importance Score
buddypress-vip-go.php	Entry point, environment detection, conditional loader	35	32.25
files.php	Core integration logic, hook registration, VIP file service handlers	966	105.65

The extreme importance disparity (105.65 vs 32.25) reflects that the entry point is essentially a gatekeeper while files.php contains the entire integration implementation.

Sources: buddypress-vip-go.php1-35 files.php1-966

Environment Detection Mechanism

The plugin detects the VIP Go environment by checking for three specific conditions at buddypress-vip-go.php28:

Detection Criteria

Check	Purpose	Provided By
class_exists( 'A8C_Files' )	Verifies VIP File Hosting Service client is available	VIP Go MU plugins
defined( 'FILES_CLIENT_SITE_ID' )	Confirms site is configured for VIP file service	VIP platform configuration
defined( 'FILES_ACCESS_TOKEN' )	Validates authentication credentials exist	VIP platform configuration

All three checks must pass for the integration to load. If any check fails, the plugin remains dormant and BuddyPress operates with its native file handling.

Sources: buddypress-vip-go.php28-32

Initialization Sequence

Sources: buddypress-vip-go.php25-34 files.php11-52

Hook Registration Timing

The integration layer uses a two-phase hook registration strategy to ensure proper integration with BuddyPress's initialization sequence:

Phase 1: Immediate Registration (File Load)

When `files.php` is loaded, it immediately registers critical filters at files.php11-16:

These filters must be registered before the bp_init action (priority 8) where bp_setup_title() runs. They prevent BuddyPress from attempting filesystem operations that are incompatible with VIP Go's remote file hosting.

Phase 2: bp_init Registration

At files.php18-52 the bulk of integration hooks are registered on the bp_init action:

Hook Type	Count	Purpose
Avatar fetch filters	3	Override URL generation for avatars
Avatar upload filters	2	Redirect uploads to VIP file service
Cover image filters	2	Handle cover image uploads and retrieval
Crop operation filters	1	Store crop coordinates in metadata
Deletion filters	2	Clean up files and metadata
Video upload filters	2	Handle chunked uploads and temp directories
Video cache actions	1	Flush cache after video operations
BuddyBoss compatibility	2	Prevent filesystem scanning errors

This timing ensures BuddyPress has completed its core initialization before the integration layer modifies its behavior.

Sources: files.php11-52

Conditional Loading Pattern

Sources: buddypress-vip-go.php25-34 files.php11-52

Why This Approach

The conditional loading pattern provides several benefits:

Environment Safety: The plugin can be installed on any WordPress installation without causing errors. On non-VIP environments, it simply does nothing.

No Core Modifications: BuddyPress core code remains untouched. All integration happens through WordPress's hook system.

Activation Order Independence: Because the plugin checks for VIP infrastructure at runtime (during bp_loaded), it doesn't matter whether BuddyPress or this plugin activates first.

Development Flexibility: Developers can test BuddyPress functionality locally without the plugin interfering, then deploy to VIP Go where the integration automatically activates.

Single Codebase: The same plugin package works across all environments without configuration changes or environment-specific builds.

Sources: buddypress-vip-go.php25-34

Detection Flow in Code

Sources: buddypress-vip-go.php25-34

Key Functions and Classes Referenced

Entity	Type	Source	Purpose
bp_loaded	Action Hook	BuddyPress	Fires after BuddyPress initializes
A8C_Files	Class	VIP Go MU plugins	Client for VIP File Hosting Service
FILES_CLIENT_SITE_ID	Constant	VIP platform	Site identifier for file service
FILES_ACCESS_TOKEN	Constant	VIP platform	Authentication token for file service
bp_init	Action Hook	BuddyPress	Fires during BuddyPress initialization (priority 8)
bp_disable_avatar_history	Filter Hook	BuddyPress 10.0+	Controls avatar history feature
bp_core_avatar_folder_dir	Filter Hook	BuddyPress	Provides filesystem path for avatars

Sources: buddypress-vip-go.php26-32 files.php12-16 files.php18-52

Multisite Considerations

While environment detection itself is not multisite-specific, the detection happens once per site in a multisite network. Each subsite's BuddyPress installation will trigger the bp_loaded action independently. However, BuddyPress typically operates from the root blog in multisite environments, which is why the integration layer includes blog-switching logic throughout. For details on multisite handling, see Multisite Architecture.

Sources: buddypress-vip-go.php25-34