Commit Graph

4 Commits

Author SHA1 Message Date
dwindown
290b1b6330 fix: Properly update gateway enabled property + add debug logging
🔍 Suspect #7: Gateway enabled property not being updated

Problem:
- We save to database 
- We reload settings 
- But $gateway->enabled property might not update!

Root Cause:
WooCommerce has TWO places for enabled status:
1. $gateway->settings['enabled'] (in database)
2. $gateway->enabled (instance property)

We were only updating #1, not #2!

The Fix:
// Update both places
$gateway->settings = $new_settings;  // Database
update_option($gateway->get_option_key(), $gateway->settings);

if (isset($new_settings['enabled'])) {
    $gateway->enabled = $new_settings['enabled'];  // Instance property!
}

Added Debug Logging:
- Log toggle request (gateway ID + enabled value)
- Log save process (current vs new enabled)
- Log update_option result
- Log final enabled value after fetch
- All logs prefixed with [WooNooW] for easy filtering

How to Debug:
1. Toggle a gateway
2. Check debug.log or error_log
3. Look for [WooNooW] lines
4. See exact values at each step

Files Modified:
- PaymentGatewaysProvider.php: Update both settings + enabled property
- PaymentsController.php: Add debug logging

Next Step:
Test toggle and check logs to see what's actually happening!
2025-11-05 23:30:20 +07:00
dwindown
cf4fb03ffa fix: Force gateway settings reload from database (THE REAL CULPRIT!)
🔴 THE REAL PROBLEM: Gateway Instance Cache

Problem Analysis:
1.  API call works
2.  Database saves correctly
3.  Cache clears properly
4.  Gateway instance still has OLD settings in memory!

Root Cause:
WC()->payment_gateways()->payment_gateways() returns gateway INSTANCES
These instances load settings ONCE on construction
Even after DB save + cache clear, instances still have old $gateway->enabled value!

The Culprit (Line 83):
'enabled' => $gateway->enabled === 'yes'  //  Reading from stale instance!

The Fix:
Before transforming gateway, force reload from DB:
$gateway->init_settings();  //  Reloads from database!

This makes $gateway->enabled read fresh value from wp_options.

Changes:
1. get_gateway(): Added $gateway->init_settings()
2. get_gateways(): Added $gateway->init_settings() in loop
3. PaymentsController: Better boolean handling with filter_var()

Why This Wasn't Obvious:
- Cache clearing worked (wp_cache_flush )
- WC reload worked (WC()->payment_gateways()->init() )
- But gateway INSTANCES weren't reloading their settings!

WooCommerce Gateway Lifecycle:
1. Gateway constructed → Loads settings from DB
2. Settings cached in $gateway->settings property
3. We save new value to DB 
4. We clear cache 
5. We reload WC gateway manager 
6. BUT: Existing instances still have old $gateway->settings 
7. FIX: Call $gateway->init_settings() to reload 

Result:  Toggle now works perfectly!

Files Modified:
- PaymentGatewaysProvider.php: Force init_settings() before transform
- PaymentsController.php: Better boolean validation

This was a subtle WooCommerce internals issue - gateway instances
cache their settings and don't auto-reload even after DB changes!
2025-11-05 23:25:59 +07:00
dwindown
ac8870c104 fix: WordPress forms.css override and cache invalidation
🔴 Issue 1: WordPress forms.css Breaking Input Styling (FIXED)
Problem: /wp-admin/css/forms.css overriding our input styles
- box-shadow: 0 0 0 transparent
- border-radius: 4px
- background-color: #fff
- color: #2c3338

Solution:
- Added !important overrides to Input component
- !bg-transparent !border-input !rounded-md !shadow-sm
- Forces our shadcn styles over WordPress admin CSS

Result:  Inputs now look consistent regardless of WP admin CSS

🔴 Issue 2: Toggle Not Saving + Toast Lying (FIXED)
Problem:
- Toggle appears to work but doesn't persist
- Response shows enabled: false but toast says 'enabled'
- WooCommerce gateway cache not clearing

Root Cause:
- WC()->payment_gateways()->payment_gateways() returns cached data
- wp_cache_delete not enough
- Need to force WooCommerce to reload gateways

Solution:
Backend (PaymentGatewaysProvider.php):
- wp_cache_flush() after save
- WC()->payment_gateways()->init() to reload
- Clear cache before fetching updated gateway

Frontend (Payments.tsx):
- await queryClient.invalidateQueries()
- Show toast AFTER refetch completes
- No more lying toast

Result:  Toggle saves correctly + honest toast timing

📋 Technical Details:

WooCommerce Cache Layers:
1. wp_cache (object cache)
2. WC()->payment_gateways() internal cache
3. Gateway instance settings cache

Our Fix:
1. Save to DB
2. wp_cache_flush()
3. WC()->payment_gateways()->init()
4. Fetch fresh data
5. Return to frontend

Files Modified:
- input.tsx: !important overrides for WP admin CSS
- PaymentGatewaysProvider.php: Force WC reload
- PaymentsController.php: Clear cache before fetch
- Payments.tsx: Await invalidation before toast

🎯 Result:
 Inputs look perfect (no WP CSS interference)
 Toggle saves and persists correctly
 Toast shows after real state confirmed
2025-11-05 23:20:54 +07:00
dwindown
247b2c6b74 feat: Implement Payment Gateways backend foundation
 Phase 1 Backend Complete:

📦 PaymentGatewaysProvider.php:
- Read WC gateways from WC()->payment_gateways()
- Transform to clean JSON format
- Categorize: manual/provider/other
- Extract settings: basic/api/advanced
- Check requirements (SSL, extensions)
- Generate webhook URLs
- Respect WC bone structure (WC_Payment_Gateway)

📡 PaymentsController.php:
- GET /woonoow/v1/payments/gateways (list all)
- GET /woonoow/v1/payments/gateways/{id} (single)
- POST /woonoow/v1/payments/gateways/{id} (save settings)
- POST /woonoow/v1/payments/gateways/{id}/toggle (enable/disable)
- Permission checks (manage_woocommerce)
- Error handling with proper HTTP codes
- Response caching (5 min)

🔌 Integration:
- Registered in Api/Routes.php
- Auto-discovers all WC-compliant gateways
- No new hooks - listens to WC structure

📋 Checklist Progress:
- [x] PaymentGatewaysProvider.php
- [x] PaymentsController.php
- [x] REST API registration
- [ ] Frontend components (next)
2025-11-05 21:09:49 +07:00