Thursday, September 3, 2026

Central Whitelist Sync & V4 Config Rework

Fixed the central whitelist API integration so centrally whitelisted IPs are honored locally, and enlarged the updated config variants' cards with price/CTA changes for 4 Bed units.

Backend Security Frontend

Config Files Fixed

Tasks Completed

API Sync Restored

Task Summary

Root cause 1: the fetch URL pointed at an HTML dashboard instead of the JSON API endpoint
Root cause 2: the API key was another site's key, not the project's own registered key
Fixed endpoint + key across root, all config variants and thin-clients; deleted stale cache files
Updated config variant: enlarged cards (plan image 200→260px, padding 1rem→1.5rem)
Updated config variant: hidden price line on 4 Bed cards and changed CTA to "Price Breakup"

Technical Details

Central Whitelist API Integration

The centralized dashboard stores per-site API keys. After signing in with the dev password, the correct key for the project was extracted and applied so the pull returns JSON with the user's IPv6 addresses already whitelisted. Local fallback whitelist file retained.

JSON API pull with the project's own API key | returns user IPv6 whitelist

Updated Config Variant Behavior

A $isFourBed flag hides the "Starting From â‚¹..." price and renders "Price Breakup" for 4 Bed (and 4 Bed Large) cards, while 3 Bed keeps its price and "Check Price" CTA. Floor plans sourced from a JSON data file.

AI-Assisted Tools

Claude Pro