 |
VOOZH | about |
|
VOOZH | about |
This document provides a comprehensive chronological record of all changes made to the BuddyPress VIP Go plugin since its initial release. The version history tracks bug fixes, feature additions, compatibility improvements, and infrastructure enhancements across all releases. This information is sourced from CHANGELOG.md1-124
The plugin follows Keep a Changelog format and Semantic Versioning principles. For information about the current plugin architecture and how these changes fit into the overall system, see System Architecture. For details about development practices that enforce quality across versions, see Development Guide.
Sources: CHANGELOG.md1-6
The plugin uses Semantic Versioning (MAJOR.MINOR.PATCH) with the current major version being 1.x. Given the plugin's role as a compatibility bridge between BuddyPress/BuddyBoss and WordPress VIP Go infrastructure, version increments follow this pattern:
| Version Component | Increment Trigger | Example |
|---|---|---|
| MAJOR (1.x.x) | Breaking changes to public API or fundamental architecture changes | Initial release: 1.0.0 |
| MINOR (1.x.0) | New features or significant functionality additions | (Not yet used; all changes are patches) |
| PATCH (1.0.x) | Bug fixes, compatibility fixes, infrastructure improvements | 1.0.1 through 1.0.12 |
All releases from 1.0.1 through 1.0.12 have been patch releases, indicating the plugin's mature, stable architecture focused on incremental compatibility and bug fixes rather than feature expansion.
Sources: CHANGELOG.md5-6
The following timeline visualizes the cadence and focus areas of plugin releases:
Key Observations:
Sources: CHANGELOG.md8-110
The following table categorizes all bug fixes by their underlying technical theme:
| Theme | Versions | Fix Count | Key Issues Resolved |
|---|---|---|---|
| Filesystem Timing | 1.0.7, 1.0.11 | 2 | opendir() warnings due to filter registration timing relative to bp_init priority 8 |
| BuddyBoss Default Avatars | 1.0.8, 1.0.10 | 2 | item_id=0 group avatar storage, opendir errors from avatar defaults |
| VIP Filesystem Compatibility | 1.0.6, 1.0.9 | 2 | Avatar upload handling, chunked video flock() incompatibility |
| BuddyPress Version Updates | 1.0.6 | 2 | BP 6.0+ filter rename, BP 10.0+ avatar history feature |
| Hook Arguments | 1.0.2, 1.0.3 | 2 | Incorrect parameter counts in action/filter calls |
| Component Activation | 1.0.1 | 1 | Fatal error when Groups component inactive |
| Cache Management | 1.0.4 | 2 | Video move cache invalidation, bp_core_reset_incrementor usage |
| Environment Detection | 1.0.5, 1.0.6 | 2 | DOING_AJAX check, simplified loading conditions |
| Email Notifications | 1.0.12 | 1 | Protocol-relative Gravatar URLs breaking in emails |
Sources: CHANGELOG.md8-110
Fixed:
//) to absolute HTTPS (https://) to prevent broken avatars in email notifications where protocol context is missingTechnical Context: Email clients don't have a protocol context to resolve //gravatar.com URLs, resulting in broken images.
Sources: CHANGELOG.md8-12
Fixed:
opendir filters to register before bp_init priority 8 to prevent timing race conditionTechnical Context: BuddyPress's bp_init action at priority 8 triggers filesystem operations in files.php that would fail if filters weren't yet registered. This fix ensures filters are in place before any directory operations occur.
Code References:
Sources: CHANGELOG.md14-18
Fixed:
opendir() on VIP filesystemTechnical Context: BuddyBoss attempts to read default group avatar directories using opendir(), which is incompatible with VIP Go's distributed filesystem.
Sources: CHANGELOG.md20-24
Fixed:
bfu_temp_dir filter to avoid "Failed to create lock file" errorTechnical Context: BuddyBoss's chunked video upload mechanism requires flock() for file locking, which VIP FHS doesn't support. The workaround uses local /tmp for assembly, then lets BuddyBoss move the complete file to VIP FHS. See Video Upload Architecture for details.
Code References:
vipbp_filter_chunked_upload_temp_dir in files.phpvipbp_delete_local_temp_file in files.phpSources: CHANGELOG.md26-30
Fixed:
item_id=0: When item_id=0 (default group avatar), store metadata in BP option vipbp-default-group-avatar instead of group metaTechnical Context: BuddyBoss uses item_id=0 to represent the default group avatar. WordPress doesn't support group meta for non-existent items, requiring storage in the options table instead. See Metadata Storage Architecture for schema details.
Code References:
vipbp_store_group_avatar_meta in files.phpvipbp_get_group_avatar_meta in files.phpSources: CHANGELOG.md32-37
Fixed:
bp_core_avatar_folder_dir filter outside bp_init callback to prevent opendir() warningsTechnical Context: The filter must be active before BuddyPress attempts directory operations during initialization. Moving it outside the bp_init callback ensures earlier registration.
Sources: CHANGELOG.md39-43
This version represents a significant compatibility overhaul with multiple fixes and infrastructure improvements.
Fixed:
DOING_AJAX checkChanged:
wp-env configuration for local developmentTechnical Context:
DOING_AJAX check was redundant because VIP environment detection already ensures proper loading contextCode References:
bp_core_avatar_history_is_disabled in files.phpInfrastructure Files:
Sources: CHANGELOG.md45-59
Fixed:
DOING_AJAX check before A8C_Files class initializationTechnical Context: Ensures the plugin doesn't attempt VIP filesystem operations during AJAX requests before the VIP environment is fully initialized. This check was later removed in 1.0.6 as redundant.
Sources: CHANGELOG.md61-65
Fixed:
bp_core_reset_incrementor calls after video moves to invalidate bp_media cache groupChanged:
Technical Context: BuddyPress caches media queries using incrementor-based cache keys. Moving videos requires cache invalidation to prevent stale data.
Code References:
vipbp_flush_video_cache hooked to bp_video_after_save in files.phpvipbp_filter_chunked_upload_temp_dir on bfu_temp_dir in files.phpSources: CHANGELOG.md67-77
Fixed:
xprofile_cover_image_uploaded hook to match expected parametersTechnical Context: The hook signature requires additional context data beyond the basic file information.
Sources: CHANGELOG.md79-83
Fixed:
Technical Context: WordPress hook system requires matching the declared argument count with the actual parameters passed.
Sources: CHANGELOG.md85-89
Fixed:
bp_is_active('groups') checks before accessing group-specific functionalityChanged:
Technical Context: BuddyPress has optional components. The plugin must check component availability before accessing component-specific functions or classes.
Maintenance:
.phpcs.xml.dist, .editorconfigSources: CHANGELOG.md91-104
Added:
Technical Context: This initial release established the core architecture that has remained stable for 9 years, requiring only compatibility patches for new BuddyPress/BuddyBoss versions and edge case fixes.
Sources: CHANGELOG.md106-110
The following diagram maps releases to the evolution of major features and architectural improvements:
Key Evolutionary Themes:
opendir() fixes requiring precise filter registrationflock() workaround, storage schema adjustmentsSources: CHANGELOG.md8-110
Analysis of the changelog reveals recurring patterns in how technical debt and edge cases were addressed:
Problem Pattern: VIP Go's distributed filesystem doesn't support standard PHP filesystem functions like opendir() and flock(). BuddyPress/BuddyBoss code assumes standard filesystem access.
Resolution Pattern:
Versions Addressing This: 1.0.7, 1.0.10, 1.0.11
Code References:
bp_core_avatar_folder_dir filter returning empty string: files.phpbp_core_avatar_folder_url filter returning empty string: files.phpbp_init callback: files.phpProblem Pattern: BuddyBoss uses item_id=0 for default group avatars, but WordPress doesn't support meta for non-existent items.
Resolution Pattern:
| Storage Type | item_id > 0 | item_id = 0 | Rationale |
|---|---|---|---|
| User Avatars | user_meta with key vipbp-avatars | N/A | Standard user meta |
| Group Avatars | group_meta with key vipbp-group-avatars | bp_option with key vipbp-default-group-avatar | item_id=0 requires options fallback |
| User Covers | user_meta with key vipbp-user-cover | N/A | Standard user meta |
| Group Covers | group_meta with key vipbp-group-cover | N/A | Standard group meta |
Versions Addressing This: 1.0.8
Code References:
vipbp_store_group_avatar_metavipbp_get_group_avatar_metaProblem Pattern: WordPress filters/actions require exact parameter counts matching their declarations.
Resolution Pattern:
Versions Addressing This: 1.0.2, 1.0.3
Code References:
add_action and add_filter callsdo_action calls: files.phpSources: CHANGELOG.md8-110
The project adopted structured Markdown standards in version 1.0.4, as evidenced by .markdownlint.json:
| Standard | Configuration | Purpose |
|---|---|---|
| Code Fence Style | fenced with consistent backticks | Standardized code block formatting |
| Heading Style | ATX (# syntax) | Consistent heading hierarchy |
| Line Length | 240 characters max | Readable diffs and editor wrapping |
| Link Style | Shortcut syntax for references | Clean reference-style links |
| Allowed Languages | bash, html, javascript, json, markdown, php, text | Syntax highlighting consistency |
These standards ensure consistent documentation across README, CHANGELOG, and code comments.
Sources: .markdownlint.json1-57 CHANGELOG.md75-77
| Year | Versions Released | Average Days Between Releases | Primary Focus |
|---|---|---|---|
| 2016 | 1 (1.0.0) | N/A | Initial release |
| 2017-2024 | 0 | N/A | Stable period |
| 2025 | 10 (1.0.1-1.0.10) | ~30 days | Compatibility fixes, infrastructure |
| 2026 | 2 (1.0.11-1.0.12) | 1 day | Critical timing fixes |
Insights:
Sources: CHANGELOG.md8-110
Based on the changelog pattern, future versions will likely address:
The plugin's mature architecture (stable since 2016) suggests future changes will continue as incremental compatibility patches rather than major architectural overhauls.
Sources: CHANGELOG.md1-124
Refresh this wiki