Cloudflare admin for cms-election-fox.blogspot.com. This theme does not contain the public Election Fox app.
This Worker tracks its own D1 usage automatically — no setup needed for the numbers below. With a Cloudflare API token configured (optional, see below), this switches to Cloudflare's own precise account-wide numbers instead, including storage size.
A Worker cannot check its own account's usage — this needs a Cloudflare API token with read access to your account's analytics.
1. Go to My Profile → API Tokens and create a token with Account → Account Analytics → Read permission.
2. Add it to the Worker as a secret named CF_API_TOKEN.
3. Add your Account ID (shown in the dashboard sidebar on any domain overview page) as a secret named CF_ACCOUNT_ID.
4. Redeploy the Worker, then click Refresh above.
Same workflow as Village map: Cloudflare pulls the whole sheet into an editable R2 draft (session). Preview is a sample; Import stores every row. Imports never touch D1.
Editable R2 draft of the election sheet. The map-style editor holds the full row; other fields round-trip on save. Publish rebuilds live elections data.
Same as Elections: Cloudflare pulls the full sheet. Publishing Karnataka writes state-map-ka and does not delete Punjab state-map-pb. Optional verified labels: State Regional Name, District Regional Name, Tehsil Regional Name, Village Regional Name, Gram Panchayat Regional Name, Assembly Constituency Regional Name, and Parliamentary Constituency Regional Name.
Cloudflare village draft. The 11 core fields plus 7 verified regional-name fields are editable on screen; other fields round-trip on save. Publish rebuilds live state-map data.
Writes Worker dataset home. Public frontend already knows how to load /data/datasets/home/current.json.
Partner-tier ad management. Scheduling isn't built yet, so sponsors save as draft here and won't go live until that lands. After activating or changing a sponsor, click Publish sponsors below — the live site reads a published snapshot, not the CMS directly, so nothing appears at election.afoxtv.com until you publish.
Locked: the list below is read-only except Pause/Set live, Upload file and Delete. Click Unlock to edit name, tier, click URL, dates and repeat schedule directly in the list — click Lock again to save everything you changed.
Pulls every sponsor you have — any status — into the editable table below in this exact column shape. Fix whatever needs fixing (a Repeat Times typo, a date, anything) directly in the table, then click Import to save just that change; everything else about the sponsor is preserved since it's still there in the row. Uploaded-file sponsors show a blank Media URL on export on purpose — leave it blank and the file stays untouched.
Columns: Sponsor Name, Partner Tier, Click URL, Media URL, Target Level, State, District, Tehsil, Village, Constituency, Constituency Type, Start Date, End Date, Repeat Times, Repeat Every Minutes, Repeat Every Seconds. Repeat Times is a semicolon-separated list of 24-hour clock times (e.g. 09:00;13:00;18:00) the ad should play at. Repeat Every Minutes/Seconds plays it on a steady interval instead — Seconds wins if both are filled in, so use Seconds when you need precision below a minute (the CMS's own Hour : Min : Sec editor always saves to Seconds). Leave all of these blank to run anytime within the date range. One row per sponsor+target — repeat the Sponsor Name on extra rows to target more than one place. Target Level is one of: india, state, district, tehsil, village, pc, ac. Media URL can be a YouTube/Vimeo link or a direct image/video link — title, duration and thumbnail are fetched automatically on import. Sponsors always import as draft; use Set live in the list below once you're ready.
A Worker has no API to check its own quota usage in real time — the numbers below are the fixed platform limits, not a live reading of what you've actually used today. For your real usage, check the Cloudflare dashboard directly.
D1 resets at midnight UTC (5:30 AM IST). Sponsors, Elections, Village map and Home copy run on R2 content docs (zero D1) — the D1 numbers above are driven by live votes, which are deliberately kept on D1.
Tab content (state map copy, elections, sponsors, future tabs…) lives as JSON documents in R2. Editing here never touches D1 quota; visitors read published docs via /data/content/… on the CDN cache. Every publish keeps an archive copy under _history.