FlyWP Object Cache
Changelog

1.1.1

• Saving the settings rewrote wp-config.php even when nothing had changed. Every click on Save Settings rewrote the file: the plugin removed its own WP_REDIS_CONFIG block and inserted a freshly built one just above the /* That's all, stop editing! */ line, whether or not a single field differed. Because that is the same spot the plugin uses when it installs FLYWPOC_ENCRYPTION_KEY, a config block sitting above the encryption key was moved below it — constants changed places for a change nobody made. On top of that, every save copied wp-config.php — Redis password included — to a wp-config.php.flywpoc-backup-* file in the document root and deleted it again moments later. A save that changes nothing now writes nothing at all: no file write, no new modification time, no backup copy, no database write. The settings screen reports No changes to save instead of claiming a save happened.
• The config block now keeps its position. When the block is already present it is overwritten exactly where it stands, so neighbouring constants such as FLYWPOC_ENCRYPTION_KEY and WP_CACHE are no longer shuffled around it. The block is still inserted at the standard WordPress location when there is none yet, and the safety net around a real write — backup first, PHP syntax check afterwards, automatic rollback if that check fails — is unchanged.
• A Redis password containing $1, $0 or a backslash is now written to wp-config.php verbatim. The block is spliced in on byte offsets instead of through a regular-expression replacement, which used to expand those sequences as backreferences.
• The Settings screen is dark again, end to end. Since the screen was split off in 1.1.0 it rendered half converted: the header and the buttons were dark, but the page around them kept WordPress' light grey, and the text fields — Host / Socket Path, Port, Database, Username, Password, Key Prefix — were white with dark text, while the dropdowns right next to them were already dark. The plugin's dark styling is applied per admin screen, and the new Settings screen had never been added to that list, so WordPress' own form styling stayed in charge of exactly those controls it outranks. All five tabs — Connection, Cache, Performance, Advanced, Security — now use the same dark palette as the Dashboard. Field text, labels, hints and placeholders were checked against their real rendered backgrounds and all clear WCAG AA (lowest measured 6.29:1).
• Removed the "Settings" button from the Dashboard screen. Since 1.1.0 the plugin menu already lists Settings as its own entry, so the button was a second route to the same page. Nothing else on the Dashboard changed.

1.1.0

• Settings moved onto their own screen. The plugin menu now opens into Dashboard, Settings and License, the same split FlyWP Cache uses. Dashboard keeps status, statistics and the Flush / Reset / Enable actions; every configuration field moved to FlyWP Object Cache > Settings (admin.php?page=flywpoc-settings). The settings dialog that used to cover the dashboard is gone.
• Existing links keep working. The top-level slug is unchanged, so bookmarks to admin.php?page=flywp-object-cache still land on the Dashboard.
• Settings storage is untouched by the move: same fields, same nonce, same manage_options check, same flywpoc_settings option and the same wp-config.php write. Values saved before updating are read and written exactly as before.
• Tab deep links now point at the settings screen, e.g. admin.php?page=flywpoc-settings#flywpoc-tab-cache.
• The charts script is no longer loaded on Settings and License, which draw no charts.
• All remaining inline style attributes were replaced with classes in assets/css/admin.css.

1.0.3

• The plugin now reports the WordPress version it is tested against, so Dashboard > Updates shows “Compatibility with WordPress 7.1.1: Yes (according to its author)” instead of “Not tested”, and the plugin details screen no longer warns that the plugin has not been tested with your version of WordPress.

1.0.2

• Added license management: activate your site under FlyWP Object Cache > License to receive plugin updates.
• The plugin menu now opens into two entries, Dashboard and License, so the license screen is always one click away.
• Your license is revalidated automatically twice a day, and you can activate, refresh, deactivate or remove your key at any time.
• Plugin updates now require a valid license. Object caching itself is never affected: an inactive or expired license only stops updates, and your site keeps caching exactly as before.
• A temporary license server outage never deactivates an active license.
• Fixed: the admin screens are dark edge to edge again. After the plugin moved to its own top-level menu, the WordPress page area around the panel stayed white, so the dashboard looked like a dark card on a bright background. Dashboard and License now render on the dark canvas end to end.

1.0.1

• Fixed fatal "Allowed memory size exhausted" errors on sites with a very large number of distinct cache keys, such as large product or review catalogs.
• The request-local runtime cache and the prefetch key tracker now have configurable upper limits with FIFO eviction instead of growing without bound during a request.
• Requests that touch unusually large key sets now degrade gracefully with additional Redis round-trips instead of exhausting the PHP memory limit. Normal page loads are unaffected.
• Fixed an uncaught type error when cache operations such as getMultiple() and setMultiple() returned numeric array keys.

1.0.0

• Initial release: Redis object caching for WordPress and WooCommerce.
• Automatic selection of the best available Redis client, with support for TCP, TLS and Unix socket connections.
• LZF, LZ4 and ZSTD compression, PHP and igbinary serialization, and non-blocking asynchronous cache flushing.
• Prefetching, stampede protection and soft pruning to keep sites stable under load.
• Detection of conflicting object cache plugins, plus Relay support with active invalidation and flush events.
• Per-site hit ratio tracking on shared Redis instances and atomic flushing through server-side Lua scripts.
• WooCommerce session handling, multisite network admin support, and Query Monitor and Debug Bar integration.
• WP-CLI commands for connection status, flushing, statistics and drop-in management.
• Dashboard with real-time statistics, historical analytics and one-click drop-in installation or removal.
• Encrypted storage for the Redis connection password.