webaware

G’day mravat,

35 active plugins isn’t huge for an eCommerce website. My own shop has 38 active plugins, many very small, and I tend to minimise plugin use — but once you start installing eCommerce and forms add-ons, they mount up.

Your real problem here is that (at least) one of your plugins, or your theme, is abusing the transients API. If you can identify which one(s) that is, you might be able to switch to an alternative that isn’t doing that. The Transient Manager plugin can help you view transients stored in your options table, so check it out:

https://ww.wp.xz.cn/plugins/transients-manager/

It’s more in your interest to do that than to continue fighting the build up of transients in the options table. If they need clearing out more than once per day, that means they are impacting the performance of your website beyond merely growing the size of your database. Running the delete queries more often just means adding more database load, when you should look at solving the cause of the problem.

Beyond that, if you find you need to keep whichever plugin is causing the excessive growth in transients, I recommend that you upgrade your server to use a persistent object store like memcached or redis. When you use one of those with WordPress, transients are not stored in the options table at all.

But one thing more: it sounds like you’re resolving your problems by clearing the transients manually. Are you only clearing expired transients or all transients? If your transients build up is largely not expired transients, you will have problems even with memcached or redis. You will need to identify the cause, and fix that.

cheers,
Ross

G’day SD,

The best way to ensure no duplicate entries / transactions with Gravity Forms is to give the form a confirmation page to go to, not just confirmation text. That way, if the visitor’s browser reloads the page (e.g. they shut their laptop, then reopen it later) it will only reload the confirmation page and not try to repost the form.

https://docs.gravityforms.com/configuring-confirmations/

cheers,
Ross

G’day madhuresh,

That sounds like you have enabled HTTP_X_FORWARDED_PROTO for HTTPS detection, so deactivating the plugin will stop doing that for you.

You can add this code to your wp-config.php file somewhere near the top, and it will do the same job without the plugin being activated.

if (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && strtolower($_SERVER['HTTP_X_FORWARDED_PROTO']) === 'https') {
	$_SERVER['HTTPS'] = 'on';
}

cheers,
Ross

G’day zubkov,

Thanks for the bug report. Please try the latest version (1.0.16), it should fix this problem.

cheers,
Ross

G’day Thorsten,

No, this plugin totally disables emails sent via WordPress email functions. It does not discriminate.

cheers,
Ross

G’day daniocana,

Edit your wp-config.php file and add these lines near the top of the file:

if (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && strtolower($_SERVER['HTTP_X_FORWARDED_PROTO']) === 'https') {
	$_SERVER['HTTPS'] = 'on';
}

This does exactly what the plugin does when you select that fix.

cheers,
Ross

Did you deactivate the plugin also? When the plugin is activated, it disable emails. You need to visit the Plugins page and deactivate the plugin.

If you would like me to look at your website, please contact me via my support form.

cheers,
Ross

G’day deandid,

Do you have an object cache installed, like memcached or redis? If you do, you won’t see any new transients — they will all go into the object cache.

cheers,
Ross