Joseph W

Hi @wplz, thanks for reporting this issue to us!

Do users still have problems logging in after dumping the caches or did that fix it?

Was the site already running W3TC version 0.10.1 when Learndash was updated or was it modified following the changes to the Learndash files?

We appreciate any additional information you can provide us regarding this situation so we can start making the appropriate adjustments on our end.

Hi @gezginorman,

Sorry to hear about the new mixed content warnings and our team will help you get this problem fixed as best we can.

If the mixed content warning only started appearing after the update then you can try using the previous plugin version to see if that works as expected. There are no vulnerability updates present in the recent version, so you should be able to use it without any security concerns until we can figure out what the problem is and release a fix.

We would also appreciate if you could provide us with the W3TC configurations you are using on your website so we have a better understanding of how to replicate this issue.

I hope this solution works for you and please let us know if there is anything else that we can do to help!

Hi @patjk,

To disable the Minify and CDN items in the Debug section, you will first have to enable both Minify and CDN in your General Settings.

Once each one is enabled you should then be able to interact with the check boxes that appear in the Debug section.

I hope that helps you get those Debug items disabled and let me know if you have any other questions.

Hi @diplatis,

You can find /wp-json in Statistics > Cache Fill and this screenshot demonstrates what you should see.

You can also view the wp-json information by pulling up yourdomain.com/wp-json in a browser to get the full output of that directory.

Let me know if I can help with anything else!

Hi @nickmade,

Sorry to hear you are having some trouble uninstalling W3TC and I hope that we can help.

I will talk to the development team about this problem and any additional information you can provide related to error log messages or other plugins used on your site will help us narrow down the cause quicker.

In the meantime there are some other steps you can try to get W3TC uninstalled and I suggest taking a backup of your site before making any further changes to your files.

Try replacing your entire .htaccess file with the WordPress default to ensure there are no other rules present there.

Next, rename your plugins directory in /wp-content to prevent any potential conflicts from other sources.

Lastly you can try replacing all of WordPress core files using a WP CLI command:

wp core download --force

Once those steps are finished manually remove any remaining W3TC folders and files.

Replacing the .htaccess and the W3 plugin details should not cause any breakage, but following the above steps will help us diagnose whether or not a more pervasive problem exists.

Please let us know how your attempt to uninstall goes and if there is anything else that we can do to help.

Hi @emporio3,

Sorry to hear about the problems with your WooCommerce categories, we are happy to help in any way we can.

What settings do you currently have enabled in W3TC? Getting a list of what you are using will help us determine settings that you can tweak to get this working.

Thank you for your patience and I hope we can get this sorted out quickly.

Hi @macobserver,

It looks like the line referenced in the errors you provided
/wp-content/plugins/w3-total-cache/PgCache_ContentGrabber.php:359
is actually a newline character in the most recent version of W3TC. I recommend running any available plugin updates to see if that addresses the errors you are seeing.

Please let us know if that fixes the problem or if there is anything else we can do to help.

• This reply was modified 5 years, 6 months ago by Joseph W.

Hi @patjk,

I am happy to help you get your Debug settings working correctly.

Enabling a particular feature in your General Settings will allow you to interact with its debug controls and get it deactivated. Once debug mode is turned off for that item you can disable the feature back in General Settings if you do not intend to use it on your website.

Hopefully that helps you get Debug Mode disabled on your website and please let us know if there is anything else that we can do to assist you.

I am sorry to hear that @lesca3dscan.

Did you try purging the cache after disabling the setting to cache /wp-admin/? While disabling does stop it from happening, if cache files still existed, you could have been seeing those instead, hence the issue seeming to remain for you and not others.

Please let us know if we can help any further, and thanks for trying our product!

Hi @40andholding,

I am happy to answer any questions you have about working with W3TC.

The first thing I suggest is to turn off Minify in your General Settings to see if that fixes the problem with the quotations.

If that does not work please let us know what settings you have configured so we can troubleshoot this problem further.

Thank you for bringing this to our attention and I hope that we can get this sorted out for you.

Hi @foolography, thank you for reporting this bug to us!

I have created a GitHub issue with the developers on your behalf to begin investigating this bug, and I urge you to subscribe to the issue to get progress updates as soon as they occur.

Thank you again for helping us improve W3TC!

Hi @macobserver,

I am sorry to hear you are getting those errors and I have not seen this particular problem before. I have reached out to the development for some additional help and I hope to get back to you soon with a solution.

Hi @diplatis,

There are no related response headers to see if the REST API is being cached, but you can view what is being cached in the Statistics page and check wp-json.

Please let us know if you have any other questions, we are always happy to help!

Hi @kul86,

There are couple settings you can change that I believe will help you get this working.

The first thing I suggest is configuring the Cache Preload settings under the Page Cache options. Enable automatic priming of the cache and use the default interval, that way all of your pages will be refreshed every 15 minutes and the new cache information should include the updated currency data.

Another option is to exclude the pages that contain the currency widget from the cache entirely and that control is located in the Advanced section of the Page Cache settings.

Hopefully these solutions work for you and please let us know if there is anything else that we can do to help!

Hi @saskso,

Unfortunately there is no documentation for filters exposed by W3TC, but we are happy to provide any advice we can.

What exactly are you referring to and trying to achieve by setting up a global preconnect http header for your image CDN?