Skip to main content
Tips & Tutorials

Flarepipe: Email and WordPress 7.1: A Compatibility Note

• Tom Morton

As of August 29, the Flarepipe Email for Cloudflare listing on WordPress.org declares “Tested up to: 7.1”. The plugin version is still 1.2.1, nothing in the code changed, and there is nothing you need to do. This post is here because “tested up to” is a line that causes more confusion than it should, and because a core release is a good moment to check one leftover from the rename.

What “tested up to” controls

The value lives in a single line of the plugin’s readme on WordPress.org. WordPress does not test anything against it. The author declares it, WordPress trusts the declaration, and two things read it. The plugin directory shows it on the listing page, and the Add Plugins screen inside your dashboard compares it against your running version. If your WordPress is newer than the declared value, the plugin card shows “Untested with your version of WordPress”, and some managed hosts fold that into their auto-update policies.

So when 7.1 shipped, every plugin that had not bumped the line started showing that warning to 7.1 sites, whether or not anything was broken. The bump is us saying we have run the plugin on 7.1 and it behaves. The commit that did it changed one line in one file.

What we checked

The free plugin has a small surface area, which keeps this list short. We installed 1.2.1 on a fresh 7.1 site and went through everything the plugin does:

  • Activation, including the table it creates for the email log.
  • The settings screen under Flarepipe in the admin menu: saving the account ID, sending domain and API token, and the masked fields when the credentials come from wp-config.php instead.
  • The Send Test Email tool, with the result landing in the log.
  • A real wp_mail() call from a password reset, intercepted and delivered through Cloudflare.
  • The email log, its 100-entry pruning, and the Export CSV button.
  • The dashboard widget.

The plugin’s integration points with core are the pre_wp_mail filter, the HTTP API for the call to Cloudflare, the Settings API for the admin screens, and a dashboard widget. None of those changed in 7.1, which is why the code did not have to.

The leftover to check: wp-config constants

If you installed the plugin before July under its old name, you may have followed our advice to keep credentials out of the database by defining them as constants in wp-config.php. Version 1.2.0 renamed every identifier in the plugin to the flarepipe_email_ prefix and migrated your settings, logs and stored credentials automatically. The one thing a migration cannot do is edit your wp-config.php, so the old constant names stopped being read in 1.2.0:

define( 'FLAREPIPE_CF_ACCOUNT_ID', 'your_account_id' );
define( 'FLAREPIPE_CF_API_TOKEN', 'your_api_token' );

Those are the current names. If your file still defines the WPFLAREMAIL_CF_ versions, the plugin ignores them and falls back to whatever is saved in the database. The tell is on the settings screen: when the constants are picked up, the account ID and token fields are masked and read-only. If they are editable, your constants are not being read. Rename them, reload the settings page, and the fields should lock.

The same release renamed the log retention filter. If you had raised or disabled the 100-entry limit, the hook is now flarepipe_email_log_retention_limit; return 0 from it to keep every entry.

If you still see the warning

The compatibility value reaches your site through the same plugin information feed that delivers update notices, and WordPress caches that feed for twelve hours. A site that checked shortly before the bump will keep showing “Untested” until the cache turns over. Opening Dashboard > Updates and clicking Check Again forces a refresh. If you live in the terminal:

wp plugin update --all --dry-run

shows the current state without changing anything.

Pro, Max and Ultra

The premium plugin at 1.2.1 hooks the same points in core and carries the same prefix migration. It updates through our own updater rather than WordPress.org, so there is no readme line to bump and no warning to see. Nothing changes for you.

Why we keep the surface small

A WordPress core release is the moment a plugin pays for every clever thing it did. Flarepipe: Email hooks one filter, makes one HTTPS call per message to your own Cloudflare account, and writes one row to its own table. There is no SMTP library to keep current and no bundled framework. That choice costs us some features in the free plugin and buys you upgrades that are boring, which is the only kind of upgrade a transactional email plugin should have.

If anything about 7.1 does look off on your site, the troubleshooting guide covers the common causes, and the support page reaches us directly.