Marko Vasiljevic

Hello Lian,
Thank you for the information.
Glad to know the issue is resolved!
Thanks!

Hello

Thank you for your inquiry and I am happy to assist you with this.
This means that the memory_limit of 128M is being exhausted. There is no particular reason why this happens with the role other than Administrator.
What you should do is to increase the memory limit
To increase the PHP memory limit setting, edit your PHP.ini file. Increase the default value (example: Maximum amount of memory a script may consume = 128MB) of the PHP memory limit line in php.ini.

memory_limit = 256M
Alternatively, you can edit your .htaccess file (Not recommended see: Apache Performance: Disable .htaccess)

php_value memory_limit 256M
If you don’t have access to these files or lack the experience to make this change, you can contact your web host and ask them to increase your PHP memory limit.

Hello Mike.

Looking at your website I see

Object Caching 419/23626 objects using Memcached
Page Caching using Memcached 
Content Delivery Network via Amazon Web Services: S3: mvpproshop-media.s3.amazonaws.com
Database Caching 2/4883 queries in 14.265 seconds using Memcached (Request-wide modification query)
Served from: localhost @ 2021-03-12 10:06:23 by W3 Total Cache

Have you switched to a regular Memcached client and not autodiscovery?
If you check this article you need to Install the Memcached Client
That requires a PHP module amazon-elasticache-cluster-client.so
https://docs.aws.amazon.com/AmazonElastiCache/latest/mem-ug/AutoDiscovery.HowAutoDiscoveryWorks.html
There are the module for:
https://elasticache-downloads.s3.amazonaws.com/ClusterClient/PHP-7.3/latest-64bit
https://elasticache-downloads.s3.amazonaws.com/ClusterClient/PHP-7.2/latest-64bit
https://elasticache-downloads.s3.amazonaws.com/ClusterClient/PHP-7.0/latest-64bit
https://elasticache-downloads.s3.amazonaws.com/ClusterClient/PHP-5.6/latest-64bit
https://elasticache-downloads.s3.amazonaws.com/ClusterClient/PHP-5.5/latest-64bit
https://elasticache-downloads.s3.amazonaws.com/ClusterClient/PHP-5.4/latest-64bit
https://elasticache-downloads.s3.amazonaws.com/ClusterClient/PHP-5.3/latest-64bit
5:15
No 7.4 or 8.0 yet. No 7.1.

Thanks!

Hello Anna,

Thank you for your inquiry and I am happy to assist you with this.

Ah yes, the PHPSESSID. This makes caching a lot harder. Make sure that caching is disabled to logged-in users in Performance>Page Cache “Don’t cache pages for logged in users”

You can also add PHPSESSID in Performance>Page Cache>Advanced>Reject Cookies filed, save all settings and purge the cache.

Thanks!

Hello Mike,

Thank you for your inquiry and I am happy to assist you with this.

There is a possible issue in /wp-content/plugins/w3-total-cache/DbCache_WpdbInjection_QueryCaching.php lines 742-744.
Change the double-quotes to single:

$strings[] = sprintf( "%s%d", str_pad( 'Total queries: ', 20 ), $this->query_total );
$strings[] = sprintf( "%s%d", str_pad( 'Cached queries: ', 20 ), $this->query_hits );
$strings[] = sprintf( "%s%.4f", str_pad( 'Total query time: ', 20 ), $this->time_total
);

to

$strings[] = sprintf( '%s%d', str_pad( 'Total queries: ', 20 ), $this->query_total );
$strings[] = sprintf( '%s%d', str_pad( 'Cached queries: ', 20 ), $this->query_hits );
$strings[] = sprintf( '%s%.4f', str_pad( 'Total query time: ', 20 ), $this->time_total );

Try this out and let me know if this helps!

Thanks!

Hello Kevin,

Thank you for your inquiry and I am happy to assist you with this.

Thank you for your support and as I can see in the test, the results are amazing.  This chain response time is not incrementing, so it’s not 2.5 s but 650ms as you can see in the waterfall chart.

So there is nothing to worry about in this case as the time to interactive is 0.4 s

Thanks!

Hello Howard,

We’ve received both of your emails via the support channel and replied. Please continue the correspondence there so we can avoid duplicating the answers.

Thanks!

Hello Bart,

I am sorry about the issue you are experiencing and I am happy to assist you with this.

Without looking into the logs there is no way we can be 100% sure what might be causing this. Most likely is a memory issue on the server. So make sure that you are not using Database Cache and Object Cache if on a shared server and caching to disk. Also, check the size of wp-content/cache/ folder

There is also a possibility of a conflict with some other plugin so you may want to check that by disabling other plugins while W3TC is enabled.

Thanks!

Hello Chris,

I’ve replied to the email. Please continue correspondence there and follow the instructions so we can avoid sharing any private info on a public forum.

Thanks!

Hello Mike,

There is an example config wp-content/plugins/w3-total-cache/ini/dbcluster-config-sample.php

Once edited create /wp-content/db-cluster-config.php and paste the config there. It should work after these steps.

Thanks!

Hello Mike,
With W3TC PRO you may use a cluster of MySQL servers when a single MySQL instance can’t handle all your traffic.

Choosing a Database Caching Method in W3 Total Cache

Thanks!

Hello,

I am sorry about the issue you are experiencing with the images and I am happy to assist you with this.

Can you please disable the settings one by one in Performance>general settings, save the settings and purge the cache after each setting is disabled and see which one might be causing the issue?

Thanks!

Hello Kiem,

Please make sure to check this link for assistance with this and also check the Performance>Install page for more details.
Thanks!

Hello Aninda,
Thank you for your inquiry and I am happy to assist you with this.
Are you trying to setup FSD CDN or just serving the static assets from the AWS?
Can you please share the screenshot of the settings in Performance>CDN>Configuration: Objects?
Thanks!

Hello Michael,

I am sorry about the issue you are experiencing with mixed content and I am happy to assist you with this.
I would recommend completely removing and re-installing W3 Total Cache, including all residual files:
1. Purge Cache
2. Deactivate and Delete Plugin
3. Check .htaccess File (make a backup)
W3TC will create many directives in the .htaccess file to control the caching behavior. Each section will start and end with comments like “#BEGIN W3TC Page Cache core” and “#END W3TC Page Cache core”.
Ensure that no residual entries are leftover in your .htaccess file after deleting the plugin.
4. Delete wp-content files and folders
– cache folder
– w3tc-config folder
– object-cache.php (if exists)
– advanced-cache.php (if exists)
– dbcache.php (if exists)
– upgrade folder
– delete w3-total-cache folder in wp-content (if exists)
5. Delete Cached Files from CDN (if using CDN)
Besides deleting all the relevant files, if you use CDN then ensure to purge the cached content from your CDN. This is necessary when you enabled minify option in W3TC settings. You should delete the minified and combined scripts and CSS files from your CDN server to avoid the site breaking on the browser.
6. Go to your wp dashboard and re-install W3 Total Cache

Once enabled, Enable the settings one by one, save all settings and purge the cache after each setting is enabled, and make sure to check your website.
Also in Page Cache, make sure that the option “Cache SSL (HTTPS) requests” is enabled
I hope this helps!

Hello Mitchell,

The provided steps need to be taken first in order to access your dashboard. So to access your dashboard you need to manually delete those files from the server following the steps provided.
Once those files are deleted, you can then access the dashboard and re-install W3TC and making sure that OC and DB Cache are not enabled.
What hosting support did is most probably disabled the plugin by renaming it in the wp-content/plugins/
The problem is that the settings you enabled are still in wp-content/w3tc-config/master.php and the cached files are in the /cache/ folder.
Thanks!

Hello Mitchell,

I am sorry about the issue you are experiencing and I am happy to assist you with this.
Can you please completely remove W3 Total Cache and re-install it and once the plugin is reinstalled make sure that Object Cache and Database Cache are not enabled in the General settings especially if on shared hosting and if caching to disk and see if the issue persists:
1. Check .htaccess File (make a backup)
W3TC will create many directives in the .htaccess file to control the caching behavior. Each section will start and end with comments like “#BEGIN W3TC Page Cache core” and “#END W3TC Page Cache core”.
Ensure that no residual entries are left over in your .htaccess file after deleting the plugin.
2. Delete wp-content files and folders
– cache folder
– w3tc-config folder
– object-cache.php (if exists)
– advanced-cache.php (if exists)
– dbcache.php (if exists)
– upgrade folder
– delete w3-total-cache folder in wp-content/plugins/ (if exists)
3. Delete Cached Files from CDN (if using CDN)
Besides deleting all the relevant files, if you use CDN then ensure to purge the cached content from your CDN. This is necessary when you enabled minify option in W3TC settings. You should delete the minified and combined scripts and CSS files from your CDN server to avoid the site breaking on the browser.
4. Go to your wp dashboard and re-install W3 Total Cache, and as I mentioned, make sure that Object Caching and Database Caching are disabled if on shared hosting plan and if caching to disk.
Thanks!

Hello Hannah,

Thank you for your inquiry and I m happy to assist you with this.
In order to be able to use the Opcode caching method (APC/APCu for example ), you need to make sure that the PHP extension is installed on your server. Only then you will be able to choose it from the Page Cache Method: list.
However, I would advise keeping the Page Cache Method: on Disk: Enhanced as it providing the best results when it comes to Page Caching.
Thanks!

Hello Steven,

Thank you for your inquiry and I am happy to assist you with this.
The notification you are seeing suggests that the CDN is not enabled in Performance>General settings:

So make sure that the CDN option is enabled and Stackath is selected under the CDN type, save all settings, and purge the cache.
Also, make sure to check this article about how to setup Stackpath with W3 Total Cache.
Thanks!

Hello Emmanuel,

As I’ve already replied via the support channel, to access the premium support for W3 Total Cache, please navigate to your wp dashboard, Performance>Support, and purchase the Performance Audit solution.

After that, we will provide you further instructions in the Premium support email chain.

Thanks!