Implements direct-to-cart functionality for landing page CTAs.
Features:
- Parse URL parameters: ?add-to-cart=123
- Support simple products: ?add-to-cart=123
- Support variable products: ?add-to-cart=123&variation_id=456
- Support quantity: ?add-to-cart=123&quantity=2
- Auto-navigate to cart after adding
- Clean URL after adding (remove parameters)
- Toast notification on success/error
Usage examples:
1. Simple product:
https://site.com/store?add-to-cart=332
2. Variable product:
https://site.com/store?add-to-cart=332&variation_id=456
3. With quantity:
https://site.com/store?add-to-cart=332&quantity=3
Flow:
- User clicks CTA on landing page
- Redirects to SPA with add-to-cart parameter
- SPA loads, hook detects parameter
- Adds product to cart via API
- Navigates to cart page
- Shows success toast
Works with both SPA modes:
- Full SPA: loads shop, adds to cart, navigates to cart
- Checkout Only: loads cart, adds to cart, stays on cart
User feedback: 'SPA means Single Page, why 4 pages?'
Correct architecture:
- 1 SPA entry page (e.g., /store)
- SPA Mode determines initial route:
* Full SPA → starts at shop page
* Checkout Only → starts at cart page
* Disabled → never loads
- React Router handles rest via /#/ routing
Changes:
- Admin UI: Changed from 4 page selectors to 1 SPA entry page
- Backend: spa_pages array → spa_page integer
- Template: Initial route based on spa_mode setting
- Simplified is_spa_page() checks (single ID comparison)
Benefits:
- User can set /store as homepage (Settings → Reading)
- Landing page → CTA → direct to cart/checkout
- Clean single entry point
- Mode controls behavior, not multiple pages
Example flow:
- Visit https://site.com/store
- Full SPA: loads shop, navigate via /#/product/123
- Checkout Only: loads cart, navigate via /#/checkout
- Homepage: set /store as homepage, SPA loads on site root
Next: Add direct-to-cart CTA with product parameter
🐛 Three Critical Email Issues Fixed:
1. Newlines Not Working
❌ "Order Number: #359 Order Total: Rp129.000" on same line
✅ Fixed by adding <br> for line continuations in paragraphs
Key change in MarkdownParser.php:
- Accumulate paragraph content with <br> between lines
- Match TypeScript behavior exactly
- Protect variables from markdown parsing
Before:
$paragraph_content = $trimmed;
After:
if ($paragraph_content) {
$paragraph_content .= '<br>' . $trimmed;
} else {
$paragraph_content = $trimmed;
}
2. Hero Card Text Color
❌ Heading black instead of white in Gmail
✅ Add inline color styles to all headings/paragraphs
Problem: Gmail doesn't inherit color from parent
Solution: Add style="color: white;" to each element
$content = preg_replace(
'/<(h[1-6]|p)([^>]*)>/',
'<$1$2 style="color: ' . $hero_text_color . ';">',
$content
);
3. Blue Border on Cards
❌ Unwanted blue border in Gmail (screenshot 2)
✅ Removed borders from .card-info, .card-warning, .card-success
Problem: CSS template had borders
Solution: Removed border declarations
Before:
.card-info { border: 1px solid #0071e3; }
After:
.card-info { background-color: #f0f7ff; }
�� Additional Improvements:
- Variable protection during markdown parsing
- Don't match bold/italic across newlines
- Proper list handling
- Block-level tag detection
- Paragraph accumulation with line breaks
🎯 Result:
- ✅ Proper line breaks in paragraphs
- ✅ White text in hero cards (Gmail compatible)
- ✅ No unwanted borders
- ✅ Variables preserved during parsing
- ✅ Professional email appearance
Test: Create order, check email - should now show:
- Order Number: #359
- Order Total: Rp129.000
- Estimated Delivery: 3-5 business days
(Each on separate line with proper spacing)
