Novra Object Cache.
Your questions answered.

No. Every Novra Object Cache Early Bird plan is a one-time payment. There is no recurring subscription and nothing to cancel.

Yes. Personal is $79 instead of $158, Business $149 instead of $298, Agency $249 instead of $498, and Enterprise $399 instead of $798.

Personal covers 1 website, Business up to 5, Agency up to 25, and Enterprise an unlimited number.

Yes. The bundle covers both plugins in a single one-time purchase: $119 for 1 website, $229 for 5, $379 for 25 and $599 for an unlimited number.

Log in to My Account for your purchases, available downloads and license keys.

Yes — 30 days, full refund, no conditions beyond the Refund Policy. Send your request within 30 days of purchase and include your order or invoice number.

It stores the WordPress object cache in Redis instead of letting WordPress rebuild it in memory on every request. All Redis traffic runs through the PhpRedis extension, and the plugin adds compression, the igbinary serializer, prefetching, stampede protection, soft pruning and analytics on top of it.

Download the plugin from your account, install and activate it in WordPress, then open Novra Object Cache → Settings and fill in the Connection tab. Use Test Connection first, and only then switch to the Dashboard and press Enable Cache.

No. They work on different layers: Novra Cache stores finished pages, Novra Object Cache stores the internal objects WordPress builds while assembling a page. They are sold separately and as a bundle, and neither one requires the other.

Yes. The plugin detects WooCommerce and reports its cache groups, including the WooCommerce session groups, separately in its statistics. On multisite it adds the blog ID to every key, registers a network admin screen and supports site-specific flushing.

No. Every plan is a lifetime license, paid once. The license gates plugin updates and nothing else — caching keeps running either way, the object-cache.php drop-in contains no licensing code at all, and a failed check against the store never revokes an active license.

Yes. Deactivate the license on the License screen of the previous website before activating it on the new one. If deactivation fails, you can remove the saved key locally to enter a new one — that does not release the server-side activation, so manage any remaining activations in your account.

PHP 8.0 or higher, WordPress 6.0 or higher, a reachable Redis server on 5.0 or higher with 6.0 or higher recommended, and the PhpRedis extension. igbinary is recommended but optional.

The activation hook checks the PHP version and the presence of the redis extension. If either is missing, the plugin deactivates itself again and stops with an error message. And as long as no drop-in is installed, WordPress simply keeps using its non-persistent in-memory cache.

It works wherever those requirements are met: a reachable Redis server and the PhpRedis extension in PHP. The plugin is not tied to a specific host, but on shared hosting without Redis there is nothing for it to connect to.

Yes. A value in Host / Socket Path that starts with a slash is treated as a socket path, any scheme prefix is stripped, and the port is ignored for socket connections.

Yes. The schemes tls://, rediss:// and ssl:// in the host value switch the connection to TLS, and setting tls to true inside WP_REDIS_CONFIG does the same. When the host carries no port, TLS falls back to 6380. Note that without your own tls_options the built-in defaults disable certificate verification — pass your own options for production, which needs PhpRedis 5.3.0 or newer.

Username and Password map to Redis 6 ACL credentials. For a classic requirepass setup, leave Username empty and fill in Password only. The legacy constant WP_REDIS_PASSWORD is still read and also accepts an array of username and password.

Test Connection on the Settings screen runs a real connection attempt against the values currently in the form and prints the error text Redis returned when it fails. Use it before installing the drop-in, not after.

Every key a site writes carries this prefix, which is what keeps two WordPress installations apart on one Redis database. On activation the plugin generates novra-object-cache: followed by the first eight characters of an MD5 of the site URL. The field shows the prefix without its trailing colon, and an empty field regenerates the site-specific default.

LZ4 is the default and is marked as the recommended balance of speed and size. LZ4 and ZSTD are marked (n/a) when your PhpRedis build does not expose them; LZF and None are always available.

The value the plugin itself defaults to is 0, meaning no expiry, and 0 is not one of the listed dropdown options. So an untouched form that you simply save stores 24 hours instead. That is expected, not a bug.

Look in wp-config.php. When WP_REDIS_CONFIG or NOVRA_OBJECT_CACHE_CONFIG is defined, its values override the saved option for every key it contains — the Settings screen still saves your change, and the constant keeps winning.

Yes. The configuration is resolved in a fixed order: WP_REDIS_CONFIG first, then NOVRA_OBJECT_CACHE_CONFIG, then the legacy WP_REDIS_* constants, and only then the option row in the database. Recognised keys include host, port, database, username, password, prefix, timeout, read_timeout, compression, serializer, query_ttl, maxttl, retries, prefetch, split_alloptions, stampede_protection, soft_pruning, async_flush, debug, log_level and analytics, plus tls and tls_options.

Changing the serializer changes the on-disk format of every stored value. The plugin flushes the cache itself when this setting changes, because otherwise the existing entries could no longer be unserialised.

Because it is a status panel, not a form. It reports one of three states — no password configured, password stored in plain text, or password encrypted and secure — and offers a single Encrypt Password Now action over AJAX. Zero fields is by design.

It can be. Encryption uses AES-256-GCM, and encrypted values are recognisable by their ENC: prefix in wp-config.php. The key belongs in NOVRA_OBJECT_CACHE_ENCRYPTION_KEY as a base64-encoded 32-byte value; without that constant the plugin generates a key and stores it in the database, which keeps key and ciphertext in the same place. Keep the key — the password cannot be decrypted without it.

WordPress loads wp-content/object-cache.php before plugins, and that file is the object cache. Enable Cache on the dashboard copies the plugin’s own copy into place and flushes Redis afterwards. Until that file exists, nothing is stored in Redis.

The plugin carries a list of conflicting object cache plugins — Redis Object Cache, WP Redis and Object Cache Pro. If one of them is active, an admin notice appears and Enable Cache refuses to install the drop-in until it is deactivated.

Before installing, the plugin reads any existing drop-in and checks whether it is its own. A foreign drop-in is never overwritten — the install is refused with a message instead.

The status check parses the version out of the installed drop-in and compares it against the running plugin version. Run Enable Cache once after a plugin update to refresh the file, or use wp novra-object-cache enable on the command line.

Deactivating removes the drop-in, provided the file identifies itself as the plugin’s own — the pre-rename marker is recognised too, so an old drop-in is cleaned up as well. Uninstalling additionally deletes the plugin’s settings option.

Tools → Site Health → Status. The plugin registers ten tests there, covering the connection, the drop-in, the configuration, Redis memory usage and eviction policy, the Redis and PhpRedis versions, cache errors, cache state and database transients.

Yes. wp novra-object-cache enable and disable manage the drop-in, status, test, info and groups report on the connection, flush and flush-group empty the cache, watch refreshes statistics in place, and diagnostics and health produce reports. clean-transients and prune-queries handle maintenance.

Run wp novra-object-cache health. It checks exactly the things that usually cause it: evicted keys from memory pressure, transients still sitting in the database, overall memory usage and whether compression is active.

First check that wp-content/object-cache.php exists — the Object Cache Drop-in test in Site Health answers this in one line. If it is missing, Enable Cache may have been refused by a conflicting plugin or a foreign drop-in. Also check whether WP_REDIS_DISABLED or NOVRA_OBJECT_CACHE_DISABLED is switched on in this environment.

The updater caches the version information it fetched from the store in a transient for three hours, and that cached answer is read before any request is built. Pressing Check again on the Updates screen does not help, because it only refreshes WordPress’s own update_plugins transient. Delete the plugin’s own transient — its name starts with fsl_ and ends in _version_info — and the new version appears immediately.

wp novra-object-cache diagnostics --format=json writes a complete report you can attach. Add the plugin, WordPress, PHP, Redis and PhpRedis versions, what you changed last, and the exact text of any error message.