Troubleshooting: Cloudflare zone dropdown is blank or frozen in Super Page Cache
After clicking Connect to Cloudflare with a new or updated API token in Super Page Cache, the zone/domain dropdown may stay blank, fail to load, or cause the settings screen to freeze. The most common cause is an API token that is missing the Zone > Zone > Read permission, which the plugin needs to load your domain list. Less often, it is a temporary loading state that a page refresh resolves.
Why this happens
When you connect or reconnect a Cloudflare API token, the plugin fetches your zone (domain) list from the Cloudflare API. If your token does not include Zone > Zone > Read, the plugin cannot retrieve that list, the domain selector stays empty, and the settings screen can go blank with a browser-console error such as Cannot convert undefined or null to object. Less often, the same symptom appears briefly if the page renders before the zone list finishes loading, in which case refreshing the page resolves it.
Recovery steps
- Confirm your API token includes the Zone > Zone > Read permission, which is required to list your domains. In your Cloudflare dashboard, open My Profile > API Tokens, edit the token (or create a new one), add Zone > Zone > Read, and save. See the Cloudflare Permissions guide for the full set of permissions the plugin needs.
- Back in the plugin, re-enter your API token and click Connect to Cloudflare again, then select your zone.
- If the dropdown was only slow to load, refresh the browser page or navigate back to Settings → Super Page Cache → Cloudflare Integration. You can also clear your browser cache or perform a hard-refresh (Ctrl+Shift+R on Windows/Linux, Cmd+Shift+R on Mac), then reload the page.
- If the selector still fails to load, contact support and include a screenshot of the Cloudflare Integration tab. If you see a browser-console error such as
Cannot convert undefined or null to object, include that in your message as well.
📝 Note: A blank or frozen zone dropdown after connecting is most often caused by an API token that is missing Zone > Zone > Read. Add that permission before assuming the issue is only temporary.