Hello, are there any plans to support Object Cache (Redis).
The issues that the lack of support is causing are too many to bear.
Also please remove these licensing calls every time we login in to admin. Earlier today your licensing service was down and we could not enter the admin. The errors logged were something like this.
2025/09/09 04:21:22 [error] 5200#5200: *1296 FastCGI sent in stderr: “PHP message: WP_Error Object
(
[errors] => Array
(
[http_request_failed] => Array
(
[0] => cURL error 6: Could not resolve host: cloud.tagdiv.com
)
)
[error_data] => Array
(
)
[additional_data:protected] => Array
(
)
)
; PHP message: PHP Fatal error: Uncaught Error: Object of class WP_Error could not be converted to string in /home/1463218.cloudwaysapps.com/hvwkzdyqhn/public_html/wp-content/plugins/td-composer/includes/tdc_check_domain.php:151
Stack trace:
#0 /home/1463218.cloudwaysapps.com/hvwkzdyqhn/public_html/wp-content/plugins/td-composer/includes/tdc_check_domain.php(108): tdc_check_domain->check_domain()
#1 /home/1463218.cloudwaysapps.com/hvwkzdyqhn/public_html/wp-content/plugins/td-composer/includes/tdc_check_domain.php(41): tdc_check_domain->set_is_domain_active()
#2 /home/1463218.cloudwaysapps.com/hvwkzdyqhn/public_html/wp-content/plugins/td-composer/includes/tdc_check_domain.php(56): tdc_check_domain->__construct()
#3 /home/1463218.cloudwaysapps.com/hvwkzdyqhn/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_js_generator.php(18): tdc_check_domain::init()
#4 /home/1463218.cloudwaysapps.com/hvwkzdyqhn/public_html/wp-includes/class-wp-hook.php(324): td_js_generator()
#5 /home/1463218” while reading response header from upstream, client: 2a02:587:3215:e800:f91d:ec3d:d5eb:60cf, server: wordpress-1463218-5518663.cloudwaysapps.com, request: “GET / HTTP/1.0”, upstream: “fastcgi://unix:/var/run/fpm-hvwkzdyqhn.sock:”, host:
Hello,
The Object Cache (Redis) should work perfectly fine with the theme. Just make sure that if you’re on a shared hosting environment, you configure the Redis settings properly in your wp-config.php file. This guide can help:
https://kb.hosting.com/docs/configuring-wordpress-to-use-redis
Please note that key verification doesn’t occur during login. It happens when you try to use the theme builder, access theme updates, install a demo, check the “My License” tab, or browse cloud templates.
If there’s an issue related to key verification and Redis caching, one potential fix is to delete the Redis object cache file that was created. In 99% of cases, this resolves the problem.
Thank you!
Hey Calin,
this is not the case anymore. Wit the latest version of Redis you have an issue.
We are using the plugin version 1.24.5 of Objec cache Pro and ever since the update to 1.24.x we keep getting the message:
“No update needed
Your site’s database is up to date!”
If it tells you something, it is a similar issue with the login/membership section in TagDiv.
There are numerous posts here about this mulfunction and your recommendation that you do not support Object Cache.
Here is a related link from the time when we could login to our sites, but optin builder had issues.
https://forum.tagdiv.com/topic/password-reset-link-not-working-in-optin-builder/
It will be great if you can tell us which keys to exlude. Most likely the new prefetch implementation is the culprit.
Hi,
For the issue related to the license key check, I recommend excluding that process from Redis object caching, you can try this code https://pastebin.com/PgCB3rap Please add this code to your child theme’s functions.php file.
If the issue persists, you can temporarily disable Redis during admin login as a fallback method to ensure access. This can help prevent lockouts when the licensing server is unreachable or when caching interferes with admin functionality.
if ( is_admin() && isset($_GET['redis_off']) ) {
define('WP_REDIS_DISABLED', true);
}
I have also notified a developer about this situation when he has time to check.
Thank you!
Disabling REDIS at will it is not the optimal solution.
As said before the issue has to do with prefetch.
Here is an example of how we exclude various “keys” for the transients and the pods framework.
Please ask your development team to provide us with the keys they are using regarding authentication (in both newspaper and optin-builder) so that I can test them.
define('WP_REDIS_CONFIG', [
'non_prefetchable_groups' => [
'transient',
'PodsAPI/_load_objects',
'pods_post_type_storage__pods_pod',
'pods_post_type_storage__pods_field'
],
]);
Hi,
I have sent this information to a developer and I hope he can provide me with a solution. If I hear back from him I will let you know.
