ES Football Bypass for Cloudflare

By Carrero

★ 5.0/5 (4 ratings)100+ active installationsVersion 2.0.3

Automatically manages Cloudflare configuration during football matches to avoid mass IP blocks affecting legitimate websites in Spain.

Description

ES Football Bypass for Cloudflare is a WordPress plugin created by David Carrero Fernandez-Baillo to help Spanish website owners protect their legitimate sites from collateral damage caused by mass IP blocks ordered during football matches. The project is open source (GPLv2) and available on GitHub: https://github.com/dcarrero/cf-football-bypass

The plugin automatically monitors football events in Spain by querying hayahora.futbol and, based on the result, manages Cloudflare DNS records to toggle between Proxied and DNS Only modes. This prevents legitimate visitors from being affected by judicial blocks targeting pirate football streaming.

The Problem

In Spain, during football matches, mass IP blocks are enforced by judicial orders to combat pirate streaming. These blocks also affect legitimate websites that have nothing to do with football, causing traffic and revenue losses.

The Solution

When football is detected:
– Automatically disables the Cloudflare proxy for selected DNS records
– Your website switches to DNS Only mode, avoiding potentially blocked Cloudflare IPs
– After the configured cooldown period, automatically re-enables the Cloudflare proxy

Two interface modes: Simple and Advanced

Since version 1.9.6 the plugin ships with two interface modes that you can switch from Settings → Interface mode:

  • Simple (default on new installs, recommended for agency/client sites): shows only the essentials. Block status, manual proxy ON/OFF buttons, basic email notifications on state changes, Cloudflare credentials, bypass behavior and uninstall options. Logs, feed diagnostics panel, staleness threshold, log retention and external cron token are hidden to reduce noise for non-technical users. Logs are still written to disk — you can always switch to Advanced if you need to diagnose something.
  • Advanced (default on upgrades from earlier versions): shows everything, including the full feed diagnostics panel, the logs tab, the technical console and the advanced options. Ideal for developers, power users, or when you need to diagnose behavior or configure a server-side cron.

There is also a standalone subpage “Is there football now?” that simply answers YES or NO based on the public feed, with a short note about the data source. Perfect to share the link with a final client that just wants to know if there are active blocks right now.

Key Features

Full Automation
– Automatic monitoring every X minutes (configurable 5-60 min)
– Automatic bypass activation/deactivation
– Integrated WordPress cron system

Dual Cloudflare Authentication Support
– Global API Key (traditional)
– API Token with specific permissions (more secure)

Granular Control
– Specific DNS record selection (A, AAAA, and CNAME)
– Configurable bypass duration (60-600 minutes)
– Customizable cooldown interval after disabling Cloudflare
– Manual control for special cases

Informative Dashboard
– Real-time football status
– Last check performed
– Bypass status (active/inactive)

Additional Tools
– Cloudflare connection test button
– Manual football status check
– Manual activation/deactivation buttons
– Detailed logging for debugging and auditing
– Protected endpoint for external cron

External Services

This plugin connects to the following external services:

hayahora.futbol

The plugin periodically queries the endpoint https://hayahora.futbol/estado/data.json to check whether there are active IP blocks during football events in Spain. This query runs automatically based on the configured cron interval (default: every 15 minutes) and can also be triggered manually from the admin panel.
– Data sent: An HTTP GET request with the site’s home URL in the User-Agent header. No personal or visitor data is transmitted.
– URL: https://hayahora.futbol/
– About the service and privacy: https://hayahora.futbol/#sobre-los-bloqueos
– Terms of use: The service is free, open source, and does not collect personal data from plugin users or their visitors.
– Trust: the plugin acts on what this feed reports. If the feed reported blocks that do not exist, the selected records would switch to DNS Only and your origin IP would become visible in DNS while the bypass lasts. The plugin limits this with HTTPS, the minimum number of affected ISPs, the staleness threshold and the cooldown, and you can always force the proxy back on by hand.

Cloudflare API

The plugin uses the official Cloudflare API (https://api.cloudflare.com/client/v4/) to read DNS records and toggle the proxy status (Proxied/DNS Only) for selected records. It requires API credentials that you provide in the plugin settings. Credentials are stored in the WordPress database and sent via HTTPS headers to Cloudflare.
– Data sent: API credentials (in headers), DNS record modifications (record ID, type, name, content, proxied status).
– URL: https://api.cloudflare.com/
– Terms of Service: https://www.cloudflare.com/terms/
– Privacy Policy: https://www.cloudflare.com/privacypolicy/

Server IP Detection Services

The plugin detects your server’s outgoing IP address (displayed in the Settings page) by querying three public services. Only the server’s own IP is returned; no personal or visitor data is transmitted. Results are cached for 1 hour.
– https://api.ipify.org/ – Provided by ipify. Privacy Policy: https://www.ipify.org/
– https://checkip.amazonaws.com/ – Provided by Amazon Web Services. Privacy Policy: https://aws.amazon.com/privacy/
– https://icanhazip.com/ – Provided by Cloudflare. Privacy Policy: https://www.cloudflare.com/privacypolicy/

Affiliate Links

The plugin’s operation page includes affiliate links clearly marked with “(aff)” to VPN services and security tools. These links are optional and do not affect the plugin’s functionality.

Cron and Automation

How does the cron system work?

The plugin uses WordPress internal cron (wp_cron) which runs when there are visits to the website. This is usually sufficient for most sites.

What if my site has low traffic and cron doesn’t run regularly?

Go to ES Football Bypass > Configuración (the plugin’s Settings page) and copy the token from the “External cron” section. With that token you can set up a real server cron:

*/15 * * * * curl -s “https://yourdomain.com/wp-cron.php?cfbcolorvivo_cron=1&token=YOUR_TOKEN_HERE” > /dev/null 2>&1

You can regenerate the token by clearing the field and saving settings (a new one is generated). This endpoint only runs the plugin check, without depending on visits. It is always available and answers only requests that carry the token, so it cannot be switched off: if you do not use it, simply never share the URL.

The token travels in the URL, so it can end up in your web server, proxy or Cloudflare access logs. Anyone who has it can only trigger the same check the cron job runs, not change settings or choose which records are switched. If you think it has leaked, regenerate it and update your crontab.

What is the “Cooldown after disabling Cloudflare”?

This is the waiting time (default 60 minutes) that the plugin respects before checking if Cloudflare can be re-enabled after detecting a block. During this period, the proxy remains in “DNS Only” mode even if the JSON stops marking the domain, avoiding rapid activation/deactivation cycles.

How do I verify that cron is working correctly?

In the Operation tab, click “WP-Cron Diagnostics” to see the next execution and the result of the last check. You can also review the integrated logs.

Abilities API

Since 2.0.0 the plugin registers five abilities through the WordPress Abilities API (WordPress 6.9 and newer), under the es-football-bypass category. This lets the REST API, MCP servers and AI agents read the block status and operate the bypass without going through the admin screens.

Every ability requires the manage_options capability, declares JSON Schemas for its input and output, and carries readonly/destructive/idempotent annotations so clients know what is safe to call.

HTTP methods over REST

WordPress derives the HTTP method from each ability’s annotations, so REST clients must use the right verb (MCP clients call abilities by name and are unaffected):

  • get-status and list-dns-records are readonly, so they are served over GET, with input as query parameters (?input[type]=A).
  • set-managed-records and run-check are served over POST, with input in the JSON body ({"input": {...}}).
  • set-proxy is annotated destructive, so it is served over DELETE. Pass its input as query parameters (?input[mode]=off): a JSON body is not read on DELETE requests.

es-football-bypass/get-status

Read-only. Returns whether La Liga IP blocks are active right now, whether this site resolves to a blocked IP, whether the bypass is engaged, the resolved IPs, how many records are managed, and the last check and feed timestamps.

es-football-bypass/list-dns-records

Read-only. Returns the cached DNS records with their proxy state and whether the plugin manages each one. Optional input: type (A, AAAA or CNAME) and managed_only.

es-football-bypass/set-managed-records

Replaces the list of records the plugin is allowed to switch. Input: record_ids (array of Cloudflare record IDs). IDs that do not exist in the zone are returned in ignored_ids. Pass an empty array to stop the plugin from touching DNS at all.

es-football-bypass/run-check

Runs the same check as the cron job: fetches the hayahora.futbol feed and applies the bypass policy, which may switch the managed records.

es-football-bypass/set-proxy

Forces the managed records to Proxied (CDN) or DNS Only. Input: mode (on or off). Annotated as destructive, since it changes live DNS at Cloudflare. Returns an error when no records are managed or Cloudflare credentials are missing.

Forcing the proxy with set-proxy or the manual buttons is a one-off action: it does not change bypass_active, and the next check applies the automatic policy again. If blocks are active, a forced Proxy ON is switched back to DNS Only; if they are not, a forced Proxy OFF is switched back on.

Logs and Auditing

Where can I see the action history?

In the ES Football Bypass for Cloudflare > Logs menu. It shows the latest automatic executions (internal or external cron) and manual actions with date, detail, and user.

Can I disable logging?

Yes. In ES Football Bypass > Configuración (the plugin’s Settings page) you can disable logging or adjust retention days (minimum 1). Logs are stored in the uploads directory under es-football-bypass-for-cloudflare/logs/ protected with .htaccess.

How do I verify that cron is working correctly?

You can check if it’s scheduled in Tools > Site Health > Info > Scheduled Events, looking for the ‘cfbcolorvivo_check_football_status’ event. You can also review WordPress error logs where the plugin records all its actions.

Server Requirements

  • WordPress 6.9 or higher
  • PHP 7.4 or higher
  • PHP Extensions: curl, json
  • Permissions: Ability to make outbound HTTP requests
  • Cron: Functional WordPress cron system

Support

  • Author: David Carrero Fernandez-Baillo
  • Website: https://carrero.es
  • Contact: https://carrero.es/contacto/

If you need help, send a direct message on X or use the contact form. Issues and improvements are also welcome in the repository: https://github.com/dcarrero/cf-football-bypass

This plugin was born from the real need to protect legitimate websites from the mass blocks affecting the Spanish digital industry during sporting events.

Specific Use Cases

High Traffic Sites
– Allows selecting only critical records (www, root domain)
– Keeps other services (mail, ftp, etc.) always proxied
– Minimizes impact on CDN and cache

Sites with Multiple Subdomains
– Granular control per subdomain
– Different strategies for different services
– Total configuration flexibility

Emergencies and Manual Override
– Manual control buttons for special situations
– Does not depend solely on automatic detection
– Allows quick reaction to failures

License

GPLv2 or later. You are free to use, modify, and distribute this plugin under the terms of the GPL.

Installation

  1. Download and Install

    • Download the plugin zip file
    • Extract (or upload the resulting folder) to wp-content/plugins/es-football-bypass-for-cloudflare/
    • Go to your WordPress dashboard > Plugins > ES Football Bypass for Cloudflare > Activate
  2. Cloudflare Configuration

    • Go to ES Football Bypass > Configuración (the plugin’s Settings page)
    • Select your authentication type (Global API Key or API Token)
    • Enter your Cloudflare credentials
    • Add your domain’s Zone ID
  3. Plugin Configuration

    • Set the check interval (recommended: 15 minutes)
    • Adjust the cooldown interval after disabling Cloudflare (default: 60 minutes)
    • Click “Test connection and load DNS”
    • Select the DNS records you want to manage
    • Save the configuration

Getting Cloudflare Credentials

For Global API Key:
1. Go to Cloudflare > My Profile > API Tokens
2. In “API Keys”, copy your “Global API Key”
3. You will also need your account email

For API Token (recommended):
1. Go to Cloudflare > My Profile > API Tokens
2. Click “Create Token”
3. Use the “Custom” template
4. Required permissions:
– Zone:Read (to read zone information)
– DNS:Read (to list DNS records)
– DNS:Edit (to modify proxy status)

FAQ

Is it safe to use this plugin?

Yes. The plugin only modifies the proxy status of Cloudflare (Proxied/DNS Only) for the records you select. It does not delete or modify the content of DNS records.

What happens if football detection fails?

In case of an error querying hayahora.futbol, the plugin assumes there is NO football for safety, maintaining the current state without making changes.

Can I use this with any DNS provider?

No, this plugin is specifically designed to work with Cloudflare. Your DNS must be managed by Cloudflare.

Does it affect my website’s SEO?

It should not negatively affect SEO. The plugin only temporarily changes whether your site goes through the Cloudflare proxy or not. Content and URLs remain the same.

What happens if I deactivate the plugin during an active bypass?

When deactivating the plugin, a function automatically runs that re-enables the Cloudflare proxy for all selected records.

Can I manually control the bypass?

Yes, the plugin includes buttons to:
– Manually check football status
– Force bypass activation/deactivation
– Test Cloudflare connection

What DNS record types are supported?

Currently supports A, AAAA, and CNAME records, which are the most common and affected by IP blocks.

How does the cron system work?

See the “Cron and Automation” section for details on wp_cron, external endpoint, and configuration recommendations.

Screenshots

Changelog

2.0.3

  • FIX: The External cron setting said that leaving the token empty disables the endpoint, but an empty field generates a new token. The text now explains that the endpoint is always available and only answers requests carrying the token
  • HARDENING: The .htaccess that protects the logs folder now uses the Apache 2.4 syntax (Require all denied) and keeps the Apache 2.2 one as a fallback. The file left by earlier versions is rewritten automatically
  • DOCS: The readme explains that the cron token can appear in access logs and how the plugin limits the trust it places in the hayahora.futbol feed
  • DOCS: Menu paths updated to the plugin’s own top-level menu

2.0.2

  • FIX: Activating the plugin no longer causes a fatal error when another copy is already active in a different folder, such as an old install from GitHub. The second copy now stops and shows a notice asking you to deactivate the other one, then takes over
  • FIX: The scheduled check is restored if it is missing while the plugin is active

2.0.1

  • HARDENING: The status feed is now downloaded with wp_safe_remote_get(), so internal addresses are rejected, and its size is capped at 20 MB (filter cfbcolorvivo_feed_max_bytes). A larger response is discarded and the local copy stays in use
  • HARDENING: A new external cron token set by hand must have at least 16 characters. Tokens already saved keep working
  • I18N: Abilities translated into Spanish, Catalan, Basque, French and Galician
  • DOCS: Forcing the proxy by hand does not change bypass_active, and the next check applies the policy again
  • INTERNAL: GitHub Actions pinned to exact commits

2.0.0

  • NEW: Abilities API support (WordPress 6.9+). The plugin now registers five abilities under the “ES Football Bypass” category, so the REST API, MCP servers and AI agents can drive the bypass without going through the admin screens: get-status, list-dns-records, set-managed-records, run-check and set-proxy
  • NEW: es-football-bypass/get-status — whether La Liga IP blocks are active, whether this site resolves to a blocked IP, and whether the bypass is currently engaged
  • NEW: es-football-bypass/list-dns-records — the cached DNS records with their proxy state and whether the plugin manages each one, filterable by record type or to managed records only
  • NEW: es-football-bypass/set-managed-records — replaces the list of records the plugin may switch; IDs missing from the Cloudflare zone are reported back as ignored
  • NEW: es-football-bypass/run-check — runs the same check as the cron job and applies the bypass policy
  • NEW: es-football-bypass/set-proxy — forces the managed records to Proxied (CDN) or DNS Only. Annotated as destructive so clients ask for confirmation, and it returns a clear error when no records are managed or Cloudflare is not configured
  • All abilities require the manage_options capability, declare JSON Schemas for input and output, and carry readonly/destructive/idempotent annotations so agents know what is safe to call
  • NEW: Filters cfbcolorvivo_site_domain and cfbcolorvivo_is_local_domain, so a staging copy, a reverse-proxied install or a WordPress Playground preview can unlock the Operation page and be checked against the production domain
  • FIX: The “Unsaved changes” warning was visible on page load before touching anything — the stylesheet was overriding the hidden attribute
  • FIX: PHP memory exhaustion while processing the status feed. The feed (about 5 MB, 50 MB once decoded) was decoded up to three times in a row and every copy was kept in memory until the end; a fourth decode on the Operation page only read a timestamp. It is now decoded once, so peak memory falls to roughly a third. Thanks to joserikko for the report
  • FIX: After an automatic check the cached DNS records kept the proxy state from before the change, so the Operation page and list-dns-records could report the opposite of what was live at Cloudflare until the next refresh
  • FIX: Uninstalling now removes the logs folder completely; a hidden .htaccess file was being left behind
  • COMPAT: Minimum WordPress version raised to 6.9, which is where the Abilities API landed. Sites on older versions stay on 1.9.8, which contains the DNS record selection fix
  • INTERNAL: The “Force Proxy ON/OFF” logic is now shared between the admin AJAX actions and the abilities, so both follow exactly the same path against Cloudflare

1.9.8

  • FIX: Unchecking a DNS record had no effect — the selection was read from the checked HTML attribute instead of the live checkbox state, so every record stayed selected and manual actions were applied to the whole zone. Reported by users; anyone who had narrowed the selection should re-check it after updating
  • NEW: Explicit “Save selection” button, so choosing which records the plugin manages no longer requires triggering a Cloudflare action. An “Unsaved changes” warning appears when the selection differs from what is stored
  • NEW: Record type filters (A / AAAA / CNAME) and quick-select buttons (“Only A”, “A + AAAA”, “Select all visible”, “Deselect”) — this is the supported way to tell the plugin to manage only A records and ignore CNAMEs
  • NEW: Select-all checkbox in the table header, live “X of Y records selected” counter, per-record badges for your own domain and for records Cloudflare cannot proxy, and readable “Proxied (CDN)” / “DNS Only” state pills
  • UX: Operation page buttons regrouped into numbered steps — “1. DNS records” (Save selection, Reload from Cloudflare) and “2. Manual actions” (Check blocks, Force Proxy OFF/ON). WP-Cron diagnostics moved next to the other diagnostic tools in Advanced mode
  • FIX: In Simple mode the action feedback was written to a hidden element, so buttons appeared to do nothing. Progress and result messages are now visible in both modes
  • FIX: Forcing Proxy ON/OFF with nothing selected now explains what to do instead of failing silently, and the confirmation dialog states how many records will be changed
  • FIX: Record IDs that no longer exist in the Cloudflare zone are dropped from the stored selection instead of being kept forever
  • COMPAT: Tested up to WordPress 7.1 (no jQuery/jQuery UI usage, so the 7.1 jQuery UI 1.14.2 update does not affect this plugin)

1.9.7

  • SECURITY: Action log file name now includes a per-site random secret, so the log URL is not guessable on servers where the directory .htaccess is ignored (nginx, LiteSpeed). Existing logs are migrated automatically to the new name on first write. Logged IPs remain anonymized (GDPR)
  • PERFORMANCE: The Operation page no longer makes redundant blocking HTTP calls on every load — the hayahora.futbol feed download and the Cloudflare DNS sync are throttled (once per minute by default; overridable via the cfbcolorvivo_feed_fetch_throttle_seconds and cfbcolorvivo_oppage_dns_throttle_seconds filters). The “Test connection”, “Update IPs” and “Clear local cache” actions still force a fresh refresh on demand

1.9.6

  • NEW: “Is there football now?” subpage under Operation — a plain YES/NO status panel based on the hayahora.futbol feed, with a short note about the data source. Designed for non-technical users to check at a glance whether there are active La Liga IP blocks
  • NEW: Optional “Notifications recipient” email field — leave empty to use the site administrator (default), or set a different address to route notifications to a support mailbox or to the final client
  • UX: Settings page reorganized into clearer sections: Interface mode, Cloudflare Credentials, Bypass behavior (with “Force Proxy OFF during football” now at the top), Email notifications, Uninstall, and Advanced options (only visible in Advanced mode)
  • UX: Technical options (Staleness threshold, Action logging, Log retention, External cron token) are now grouped under “Advanced options” and hidden in Simple mode to reduce noise for client sites
  • UX: “Advanced” mode label now explicitly mentions cron settings so users know where to find them
  • I18N: Plugin now calls load_plugin_textdomain() so the bundled .mo files in /languages/ are picked up when installing from the release zip (previously only translations published on translate.wordpress.org were applied)
  • I18N: All five bundled languages (es_ES, ca, eu, fr_FR, gl_ES) are now at 100% translation coverage — machine-assisted translations for ca/eu/fr_FR/gl_ES will be refined by the GlotPress community over time

1.9.5

  • NEW: Feed diagnostics panel on the Operation page (local data.json age and size, last remote fetch status, active blocked IPs count)
  • NEW: “Clear local cache (data.json)” button to force a clean re-fetch on the next check
  • NEW: Staleness threshold setting (1-72h, default 6h) — “blocked” states whose last stateChange is older than this are treated as unblocked, preventing orphan entries from keeping the bypass active indefinitely. Overridable via cfbcolorvivo_stale_threshold_seconds filter
  • NEW: Minimum-ISPs-with-blocks setting (1-20, default 2) — general bypass only triggers when at least N distinct ISPs report blocks simultaneously, reducing false positives from isolated single-ISP outages. Falls back to classic behavior if the feed has no per-ISP information. Overridable via cfbcolorvivo_min_isps_blocked filter
  • NEW: Feed diagnostics panel now lists the ISPs with active blocks and whether they meet the minimum-ISPs gate
  • NEW: Optional email notifications to the site admin when the bypass turns on/off automatically, with a 2-minute throttle to prevent bursts. Off by default. Overridable via cfbcolorvivo_email_throttle_seconds filter
  • NEW: Interface mode setting — “Simple” hides the diagnostics panel, the logs tab and the technical console for non-technical users, leaving only the block status and the manual proxy ON/OFF buttons. “Advanced” shows everything as before. New installs default to Simple; upgrades from 1.9.x and earlier keep the Advanced experience automatically
  • NEW: External cron settings now show the full request URL and a ready-to-paste crontab example using your current check interval
  • NEW: “Delete data on uninstall” setting — uncheck it to keep settings, credentials and logs across reinstalls. Cron hook and ephemeral transients are always cleaned up regardless of this setting
  • SECURITY: Update URI header added to lock updates to WordPress.org (prevents slug hijacking by external sources)
  • PERF: get_settings() memoized per request, avoiding repeated normalization on the same page load
  • FIX: Explicit logging when dns_get_record() fails for the site domain
  • FIX: DateTime parse errors when comparing lastUpdate are now logged instead of silenced
  • FIX: Warning logged when hayahora.futbol JSON has unexpected structure (no lastUpdate nor known IP keys)
  • CODE: stateChanges parsing deduplicated across three call sites into a single latest_state_from_changes() helper
  • UI: “Reset settings” option removed — uninstalling the plugin (with “Delete data on uninstall” checked, which is the default) gives the same clean slate and avoids duplicating the destructive action

1.9.2

  • I18N: Source language refactored to English (was Spanish), aligning with the WordPress.org translation convention
  • I18N: New es_ES.po with 100% Spanish translations bundled (no functionality change for Spanish users)
  • I18N: ca, eu, fr_FR and gl_ES translations completed to 100% (23 new strings added)
  • I18N: en_US.po removed (source IS English now, no longer needed)
  • I18N: .pot regenerated from current code with English msgids and accurate line references
  • DOCS: Plugin header Description rewritten in English to match the new source language

1.9.1

  • FIX: Text domain changed to match new WP.org slug (es-football-bypass-for-cloudflare)
  • FIX: All file paths now use wp_upload_dir() instead of hardcoded WP_CONTENT_DIR
  • FIX: File operations migrated to WP_Filesystem API (no more file_put_contents)
  • FIX: register_setting() uses proper array format with sanitize_callback
  • FIX: Stricter sanitization for selected_records, bypass_blocked_ips and state fields
  • FIX: Inline JavaScript no longer uses PHP interpolation, uses wp_localize_script data
  • FIX: Plugin data directory renamed to es-football-bypass-for-cloudflare in uploads
  • FIX: Contributors field corrected in readme.txt
  • DOCS: External services section updated with hayahora.futbol information links

1.9.0

  • RENAME: Plugin renamed from “CF Football Bypass” to “ES Football Bypass for Cloudflare” (WordPress.org trademark compliance)
  • DOCS: External services section expanded with server IP detection services documentation
  • DOCS: Enhanced privacy and data transmission details for all external services

1.8.6

  • CODE: Full WordPress Coding Standards compliance (PHPCS): tabs, spacing, Yoda conditions, snake_case variables, PHPDoc comments
  • UX: Plugin version now displayed on all plugin pages (Operation, Settings, Logs)
  • I18N: All remaining hardcoded Spanish strings wrapped in __() for consistent translations
  • CODE: Short ternary operators replaced with full ternary for WP standards
  • CODE: in_array() calls now use strict mode
  • CODE: Assignment-in-condition patterns refactored

1.8.5

  • NEW: Support for Cloudflare Account-owned API Tokens (in addition to User API Tokens and Global API Key)
  • NEW: Account ID field shown when Account Token is selected
  • UX: Auth type selector now offers three options: Global API Key, User Token, Account Token
  • UX: Email and Account ID fields show/hide dynamically based on selected auth type

1.8.2

  • NEW: Server outgoing IP detection shown in Settings to help restrict Cloudflare API Token by IP
  • UX: IP is cached for 1 hour and detected from multiple sources for reliability

1.8.1

  • SECURITY: External cron token comparison now uses hash_equals() to prevent timing attacks
  • PERFORMANCE: Log pruning throttled to once per day instead of on every log event
  • UX: Confirmation dialogs before destructive actions (Force OFF, Force ON, Reset)
  • UX: Action buttons are disabled during AJAX operations to prevent double-click
  • UX: Local environment detection with friendly warning on Operation page
  • CODE: Added uninstall.php for complete cleanup on plugin removal (WP_Filesystem)
  • CODE: Replaced deprecated current_time(‘timestamp’) with time() (WP 5.3+)

1.8.0

  • IMPROVEMENT: Changed all prefixes from cfb_ to cfbcolorvivo_ to avoid conflicts with other plugins
  • IMPROVEMENT: Changed all CSS/JS identifiers from cfb- to cfbcolorvivo- for uniqueness
  • CODE: Settings option renamed to cfbcolorvivo_settings
  • CODE: Cron hook renamed to cfbcolorvivo_check_football_status
  • CODE: Log directory renamed to cfbcolorvivo-logs
  • CODE: All AJAX actions, transients, and filters updated with new prefix

1.7.1

  • FIX: Fixed critical bug in configuration checkboxes that prevented unchecking options once activated
  • FIX: “Force Proxy OFF during football” option can now be properly disabled
  • FIX: “Action logging” option can now be properly disabled
  • FIX: Improved code compliance with WordPress.org plugin guidelines

1.7.0

  • IMPROVEMENT: JavaScript now uses wp_enqueue_script() and wp_add_inline_script() per WordPress.org directory guidelines
  • IMPROVEMENT: Removed all inline script blocks from PHP code
  • IMPROVEMENT: Dynamic data passed via wp_localize_script() for better code separation
  • IMPROVEMENT: admin_enqueue_scripts hook properly implemented with page filtering
  • CODE: Complete refactoring of admin assets system

1.6.0

  • SECURITY: Log file moved to wp-content/uploads/cfbcolorvivo-logs/ with .htaccess protection
  • SECURITY: IP anonymization in logs for GDPR compliance
  • SECURITY: Removed error suppression operators (@) with explicit checks
  • SECURITY: Added index.php files to prevent directory listing
  • IMPROVEMENT: Full internationalization (i18n) support with cf-football-bypass text domain
  • IMPROVEMENT: Plugin header updated with all fields required by WordPress.org
  • IMPROVEMENT: Automatic log directory creation with protection
  • IMPROVEMENT: Better error handling for file writing
  • FIX: Version sync between plugin header and readme.txt

1.0.1

  • Added Cloudflare API Token support
  • Improved manual control button with confirmation
  • Sidebar with recommended links
  • Minor bug fixes
  • Better error handling and logging

1.0.0

  • Initial version
  • Automatic hayahora.futbol monitoring
  • Automatic Cloudflare DNS record management
  • Global API Key support
  • Admin dashboard
  • Integrated cron system