Crypoverse - Cryptocurrency Payment Gateway [BTC, LTC, ETH] v3.1.2

# Crypoverse - Crypto Payment Gateway - Changelog

## Version 3.1.2 (2025-12-15) - PRODUCTION RELEASE: Complete Structural Fix

### **FINAL FIX: "Rebuild" vs "Upgrade" Issue - ROOT CAUSE RESOLVED!**

**Issue #10: XenForo Shows Wrong Version After Installation** - **FIXED **
- **Root Cause**: Conflicting version sources and incorrect addon structure
- **Analysis**: Researched XenForo 2.x addon best practices and modern standards
- **Discovery**: XenForo works correctly with ONLY addon.json for version control
**Issue #6: Payment Provider Not Created on Fresh Installs (NEW INSTALLATIONS)**
- **Fixed** - Payment provider now properly registers during fresh installations
- **Fixed** - Improved installStep2() with comprehensive error handling and fallback mechanisms
- **Fixed** - Added upgrade3000800Step1() to recreate missing payment provider for existing installations
- **Cause** - installStep2() was not properly handling edge cases and missing error logging
- **Impact** - Fresh installations of v3.0.5+ were not creating the "Crypoverse" option in payment provider dropdown
- **Critical** - Without this fix, the addon appeared to install successfully but was completely non-functional

### What Was Wrong:
1. Had build.json (unnecessary file causing conflicts)
2. Had _data/addon_info.xml (not required for XenForo 2.x)
3. Had two hashes.json files (circular reference issue)
4. Used MD5 hashes (outdated)
5. Hash paths were relative to addon folder (incorrect)
6. Circular reference causing infinite hash changes

### The Fix (v3.1.2):
1. **DELETED**: build.json (conflicting version source)
2. **DELETED**: _data/addon_info.xml (not needed for XenForo 2)
3. **DELETED**: _data/hashes.json (circular reference issue)
4. **UPDATED**: hashes.json to use SHA-256 instead of MD5
5. **UPDATED**: Hash paths to be ZIP-relative: `src/addons/Crypoverseaddon/CryptoPayment/...`
6. **VERIFIED**: addon.json is now the SOLE source of version information
7. **CLEANED**: Removed all debug code from Setup.php
8. **FIXED**: Option phrases now display correctly (used dots instead of underscores)

### Why This Fixes Everything:
- XenForo reads version ONLY from addon.json (as designed)
- No conflicting version sources to cause confusion
- SHA-256 provides better file integrity validation
- ZIP-relative paths match XenForo's internal structure
- No circular references = no infinite hash changes
- Follows XenForo 2.x modern addon structure standards

## Version 3.0.7 (2025-11-28) - CRITICAL ZIP STRUCTURE FIX + ALL PREVIOUS FIXES

NOTE: For upgrading addon replace files using FTP or just overwrite addon from ACP!


### CRITICAL FIXES

**Issue #5: Invalid XenForo Archive Structure (NEW)**
- **Fixed** - Corrected ZIP archive structure to start with `CryptoPayment/` folder at root
- **Cause** - Previous ZIPs had incorrect structure: `upload/src/addons/Crypoverseaddon/CryptoPayment/`
- **Impact** - ZIP now uploads successfully, no more "File does not appear to be a valid add-on archive" error
- **Critical** - Without this fix, XenForo rejects the ZIP file completely

**Issue #4: Addon Not Upgrading (Shows "Rebuild" Instead of "Upgrade")**
- **Fixed** - Updated version in `_data/addon_info.xml` and corrected XML attribute order
- **Cause** - XenForo uses addon_info.xml (not just addon.json) to detect version during upgrade
- **Impact** - Addon now properly upgrades from 2.5.1/3.0.4 to 3.0.7 without requiring "Overwrite files" option
- **Critical** - Without this fix, users were stuck on old versions even after "upgrading"
- **Details** - Ensured version_id attribute comes before version_string in XML

**Issue #1: Missing hashes.json File Health Check Error**
- **Fixed** - Copied hashes.json from `_data/` folder to addon root folder
- **Cause** - XenForo expects hashes.json in addon root, not in _data subfolder
- **Impact** - File health check now works correctly in XenForo Admin CP

**Issue #2: MySQL Error with Emoji Characters in phrases.xml**
- **Fixed** - Removed all emoji characters from phrases.xml that caused MySQL utf8mb4 errors
- **Error** - `Incorrect string value: '\xF0\x9F\x93\x9A <...' for column 'phrase_text'`
- **Impact** - Addon installation/upgrade now completes without MySQL errors
- **Changed Phrases**:
- `option_group_cryptoPayment_explain` - Removed , , emojis
- `enter_api_key_from_crypto_platform` - Removed , , emojis

**Issue #3: Undefined Constant CallbackState:AYMENT_CANCELLED**
- **Fixed** - Removed usage of non-existent XenForo constants
- **Error** - `Undefined constant XF\Payment\CallbackState:AYMENT_CANCELLED`
- **Root Cause** - XenForo 2 only has 3 constants: PAYMENT_RECEIVED, PAYMENT_REINSTATED, PAYMENT_REVERSED
- **Impact** - Webhook callbacks now process correctly without fatal errors
- **Files Modified**:
- `Payment/CryptoProvider.php` (lines 634, 641, 837, 868, 875, 887)
- `Controller/CryptoPayment.php` (lines 135-138)
- `Controller/PaymentReturn.php` (lines 70-100)

Updates: v3.0.1 → v3.0.4

We've released several important updates addressing critical bugs and improving the payment logging system.

---

What's Fixed

v3.0.4 (October 9, 2025)

• Fixed RMMP product names showing "Order - XXXXX" instead of actual resource titles
• Fixed "Unknown user/profile" entries in payment logs
• Added payment initiation logging for better transaction tracking
• Removed unnecessary technical log entries

v3.0.3 (October 9, 2025)

• Fixed payment provider logs not appearing in Admin CP
• Improved XFRM resource name detection

v3.0.2 (October 8, 2025)

• Fixed server error: "Undefined constant PAYMENT_CANCELED"
• Restored detailed payment logging
• Fixed underpaid transaction handling