Joseph W

You’re welcome @erico2!

Getting access to your website will be the easiest way for us to figure out what might be going on here, but exchanging login information in these forums is not permitted.

The best way for us to get an idea of what might be going on is to take a look at your Site Health information. In your Dashboard go to Tools > Site Health and then select the Info option at the top of that page. You will then have the option to copy that information and paste it in this thread.

Thank you for bringing this problem to us and I hope that we can get it sorted out for you soon!

• This reply was modified 5 years, 3 months ago by Joseph W. Reason: forum policies

Hi @erico2, sorry to hear about the problems getting the remote storage settings working correctly and our team is happy to help in any way we can.

We are currently unable to replicate this exact problem on our end and one thing you can try is temporarily deactivating the other plugins on your website. It is possible that something is interfering with the settings when you attempt to save them.

If possible, could you also send us the list of the plugins that you’re running on your website? You can quickly get the full list by copying the output of the Info page using the Site Health tool. https://user-images.githubusercontent.com/5925563/68695771-acea2900-0549-11ea-9e62-0c3e1566a507.png

I hope that helps get everything working for you and please let us know if there is anything else that we can do to help!

Hi @courtheye, I am happy to help you get your background styled as expected.

If you want to change the scaling and background settings for mobile and tablet devices then the best way to achieve this is by using custom CSS rules through your website’s Customizer.

Media queries are a CSS option that we can use to target only mobile and tablet screen sizes. The following code will create the media query and tell your website to only run the code contained within it at the appropriate screen sizes.

@media (max-width: 991px) {

}

Now that the Media Query is set up we can begin adding our rules to change the styling of the background image. Use the CSS selector body.custom-background to make sure your rules only apply to the element that controls your background image.

@media (max-width: 991px) {

body.custom-background {

}
}

Now you can begin adding your rules inside of the CSS selector. Use the background-size and background-position rules to make the desired changes.

@media (max-width: 991px) {
body.custom-background {
background-size: contain;
background-position: center;
}
}

The contain setting tells your background image to only stretch as far as the screen width will allow and the entire image should be visible.

If you want to replace the background image with a solid color you can use the following rules to remove the image and set a custom color for your background area. Replace the provided hexcode with any valid color hex you think will best fit your design.

@media (max-width: 991px) {
body.custom-background {
background-image: none;
background-color: #999999;
}
}

You can also use this rule to remove the margins and padding that applied by default to your Call to Action widget and decrease the size of that area.

@media (max-width: 991px) {
.palette-primary .call-to-action {
padding: 0;
margin: 0;
}
}

I hope that CSS lets you create the design you want and please let us know if there is anything else our team can do to help!

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

Hi @vvalladolid, thanks for sharing that information!

In your list of plugins I see a few related to backups/migrations and security, one of those could be interfering with the backup generation process. You also have multiple page building and caching plugins as well which might be creating some additional conflicts that are disrupting backup creation.

Try temporarily disabling those and generating a new backup to see if that fixes the problem.

Sure thing @benoitroubert! I will add a note in the description stating that we should extend the functionality beyond Google Analytics and apply the changes to other external script sources as well.

Hi @benoitroubert, thank you for the feature idea!

I created a GitHub issue on your behalf with the development team to review and consider adding your feature to a future release. You can also subscribe to the request in GitHub directly to get notifications for any new developments on this feature.

Thank you again for your suggestion!

Hi @diplatis,

Under the PHP requests section you should see the Cache Fill option which you can then open to see /wp-json.

I hope that helps you locate the information you need regarding the REST API and let me know if I can do anything else to help.

Hi @autosoftbv,

The value set for W3TC_DYNAMIC_SECURITY cannot be random and needs to be a static value due to variable matching requirements. I found this Gist from one of the plugin developments stating that as a requirement.

Unfortunately the fragment caching ability is only available in the Pro version and will not function correctly if you are using the community version.

Let me know if you have any other questions, I am happy to help!

Hi @autosoftbv,

Thank you for your question and I am happy to help in any way I can.

You can wrap your custom loop with ‘mfunc’ in your footer template to tell W3TC not to cache that section of code, but there is some setup required.

The first thing you will need to do is add the W3TC_DYNAMIC_SECURITY constant to your wp-config.php.

define('W3TC_DYNAMIC_SECURITY', 'useanyvalueyoulike');

Once that constant is created you can wrap the custom loop in your footer with mfunc and the security constant.

<!--mfunc <?php echo W3TC_DYNAMIC_SECURITY; ?> -->

your custom post loop here

<!--mfunc <?php echo W3TC_DYNAMIC_SECURITY; ?> -->

I hope that helps you keep your employee quotes randomized and please let me know if you have any other questions.

Hi @prabasjalakai,

Sorry to hear about this problem with your custom plugin and our team will help as best we can. I have reached out to the developers directly for some more insight on this problem and hopefully they can provide me with some suggestions for you.

Any additional information you can provide on this situation, such as error log information, will help us reach a solution quicker and I hope to have something for you soon.

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

Hi @emporio3,

The first thing I recommend trying is to disable Minify then purge all your caches. Hopefully that lets you work with your categories properly, but let us know if there is anything else we can do to help!

Hi @saskso, thank you for following up with this issue.

When using Disk: Enhanced as your caching method, the headers are iterated over and added within https://github.com/W3EDGE/w3-total-cache/blob/master/Cache_File_Generic.php#L100 which would need to be extended to allow the functionality you intend, such as including or excluding specific items from being added to the header.

Caching methods other than Disk: Enhanced do not have this limitation, so I would suggest to use an alternative method if possible.

I have also created a feature suggestion with the developers to add your requested filter functionality in a future version.

I hope that this information helps you make the customizations you need to work with your image CDN and please let us know if there is anything else that we can do to assist!

Hi @greghy, I am happy to answer your question!

The default lifetime of the Page Cache is 3600 seconds and the controls to change that expiration time are actually located in the HTML & XML section located under Performance > Browser Cache. Changing the ‘Expires header lifetime’ will alter the duration of time before your pages are flagged as stale and get regenerated in the cache.

I hope that answers you question and please let us know if there is anything else we can do to help!

Hi @arlinaite,

I am happy to answer any questions you have about working with W3TC and I apologize for any confusion you might experienced so far.

The Cloudflare extension only offers basic integration with their system and focuses solely on cache management through their API. Other than configuring your API token, the only available control in W3TC that interacts with Cloudflare is the ability to purge their caches and this can be found by selecting the Settings option under Cloudflare in your list of Extensions.

However I would like to ask, what kinds of settings your were expecting to find following the extension activation? We are always looking for new features to add to W3TC and your feedback will go a long way to helping us improve our plugin.

I hope that this information answers your question and I look forward to hearing back from you!

Hi @macobserver,

Yes, it could be a bug with how the newest version handles the header info and we would appreciate your help if possible.

When did you start seeing these errors? Did they only start appearing after updating W3TC to the latest version or were there other configuration changes that occurred before this happened?

If it is a bug with the latest version of W3TC then you can try changing to the last stable version to get rid of there errors until we are able to determine the correct solution.

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