Quantcast
Channel: wp-super-cache – WordPress.org Forums
Viewing all 3480 articles
Browse latest View live

delonanthony on "[Plugin: WP Super Cache] Google PageSpeed Insights suggests "Leverage browser caching""

0
0

I am using WP Super Cache plugin on my website http://www.prosoccerrebounder.net/ and I recently checked my site on google page speed insights. I am getting the following fix message

"Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network."

Can I fix this problem via WP super cache settings like through garbage collection?

My current cache timeout is 604800 seconds and timer is 604800 seconds too. I use Autoptimize plugin as well.

Anyone's quick help is appreciated.

https://wordpress.org/plugins/wp-super-cache/


intelly on "Inline Related Posts and Cache system"

0
0

Hi there,
Actually we are aware of it, and it is still under investigation. The thing is quite strange as we tested our plugin with many other cache plugins (such as WP Cache o WP Fastest Cache) and all works correctly. Our developers are working on it and we can keep you updated when a solution will be ready :)
Be aware we usually answer tickets on support@intellywp.com. Do you still need help? If yes, do not hesitate to contact us there.

myhero on "[Plugin: WP Super Cache] Google PageSpeed Insights suggests "Leverage browser caching""

0
0

I get the same - I think I'll be changing to W3 total cache

delonanthony on "[Plugin: WP Super Cache] Google PageSpeed Insights suggests "Leverage browser caching""

0
0

Any solution from the plugin developer or experts?

IntellyWP on "Inline Related Posts and Cache system"

0
0

Hi Guys,
I'll explain here how our plugin works.
IRP generate each page refresh new related boxes and this is done to improve the visitor engagements.

If once you have enabled the cache plugin, you will see the same posts, this means that your caching system also cache the related box results.
While if you see each time new related boxes this means that your page content is not cached.

Let me know if this helped you, Simon.

mauriciogarofalo on "Inline Related Posts and Cache system"

0
0

Yes Simon, it helps.

Maybe I got confussed. Cause some previous help that said:

"As you seen IRP is not cached due to we did a lot of performance test and we found that is not needed.
We prefer to show each time a different post to improve the visitor engagement."

So, if cached is enabled what you previous said is not implemented to cached pages. I thought that if cache enabled, every time someone open a page it is cached agaon for IRP new generated content.

By the way, excellent plugin. Would love to have option to disable underline in links.

Thank you.

IntellyWP on "Inline Related Posts and Cache system"

0
0

Great Mauricio,
To disable underline in links you have 2 different ways:
1. Edit the assets/templates/styles.html CSS file inside your plugin
2. With the premium version, you can define a different CSS due to each template has one CSS class so is very easy to edit (while with the free version the template name is randomly generated).

If you need some help let me know and will be a pleasure to help you, Simon.

edwardspek on "WP Super Cache not working - timestamps don't match?"

0
0

Had the same problem. Turning on CloudFlare development mode did indeed resolve the issue.

However, does this mean WP Super Cache is incompatible with CloudFlare (when not in development mode)?


Pothi Kalimuthu on "WP Super Cache not working - timestamps don't match?"

0
0

@edwardspek

As already mentioned...

At times, CloudFlare creates similar issues.

It doesn't mean WP Super Cache is incompatible with CloudFlare. In order to understand what's happening, you must understand how both work and what they actually do.

Short answer: You may ignore the timestamp error. Rest assured, things would work as configured.

If you are too concerned about timestamp error, then, setup "s-maxage" header to a very high value via .htaccess (or whatever the configuration your server supports) and configure CloudFlare to cache dynamic content too. By default, CloudFlare is set to cache static content only.

johnny_n on "[Plugin: Wordfence Security] File appears to be malicious wp-cache"

0
0

Hey, thanks @N Atta Kusi Adusei - nice advice to block the IP... one note for folks, since I had forgotten this - once you block the IP in 'Live Traffic', you switch over to 'Blocked IPs' to make it permanent.

andru26 on "WP Super Cache - Can't clear the cache"

0
0

Hello,

I have a problem with the homepage of this website: http://saviynt.com/

I am using WP Super Cache on it and for some reason the homepage was distorted after I minified some resources.

I un-minified the resources to fix the issue, but no matter what I do I am getting a cached version of the distorted page.

I tried clearing the cache, disabling the plugin and removing it, but the page is still loading the distorted version.

Please help removing the cache.

https://wordpress.org/plugins/wp-super-cache/

Merv on "[Plugin: WP Super Cache] Super Cache with Mod-Rewrite"

0
0

My host admins recommended enabling Super Cache with mod_rewrite which I did and it appears to be working. Then, I noticed this in advanced settings:

Since you are using mod_rewrite to serve cache files, you must choose a directory in your web root which is "/home/sellwithsoul/www/www/" and update the mod_rewrite rules in the .htaccess file.

The current directory is the default /wp-content/cache/

Is it necessary to define the directory in the root in this case and, if so, why?

Thanks for your guidance.
Merv

https://wordpress.org/plugins/wp-super-cache/

mojamba on "[Plugin: WP Super Cache] All cache being cleared on any post edit"

0
0

I have the same issue and I just read the related threads mentioned by graphicsxp and jciselectric, especially Issues 66 and 98 on github. I see that on the latter thread Donncha O Caoimh mentions the problem being related to using a static home page whereas on the former the issue is reported to relate to CPT with rewrite set to false. I use a static homepage and can confirm this is the issue for me as when I switched to posts display instead the issue went away. I cannot comment on the validity of the CPT issue. Hoping for a fix in the next version - any comment from the author(s) about whether that is a reasonable expectation or not? Until a fixed version is issued, the code referenced earlier in the thread suits my needs (but I understand why it might not be suitable for others).

Sergey9999 on "[Plugin: WP Super Cache] Google PageSpeed Insights suggests "Leverage browser caching""

0
0

Its bad that developers are ingoring this question all the time from thousends people. I think we must mark 1 star and change plugins.

mojamba on "[Plugin: WP Super Cache] Google PageSpeed Insights suggests "Leverage browser caching""

0
0

Sergey9999, have you tried to add browser caching directly to your .htaccess file (assuming you are on Apache-based server, which is the standard)? If not, try add the following:

##### EXPIRE CACHING - LEVERAGE BROWSER CACHING #####
<IfModule mod_expires.c>
ExpiresActive On
ExpiresDefault "access plus 1 month 1 days"
ExpiresByType text/html "access plus 1 month 1 days"
ExpiresByType image/gif "access plus 1 month 1 days"
ExpiresByType image/jpeg "access plus 1 month 1 days"
ExpiresByType image/png "access plus 1 month 1 days"
ExpiresByType text/css "access plus 1 month 1 days"
ExpiresByType text/javascript "access plus 1 month 1 week"
ExpiresByType application/x-javascript "access plus 1 month 1 days"
ExpiresByType text/xml "access plus 1 seconds"
</IfModule>
##### END EXPIRE CACHING #####

Sergey9999 on "[Plugin: WP Super Cache] Google PageSpeed Insights suggests "Leverage browser caching""

0
0

Thank you for your answer man, why developers dont do it in plugin options?

mojamba on "[Plugin: WP Super Cache] Google PageSpeed Insights suggests "Leverage browser caching""

0
0

Well, I can't speak for the developers but I can guess. Browser caching and page caching are different things. WP Super Cache is a page caching plugin, meaning the cache is maintained on the server and then shown to visitors. Browser caching is just directions (in this case, in your .htacess file) that tell a visitor's browser to cache different types of files. I guess the developers figure that is not their business or concern since it is a different thing entirely. Also, different users may want to set different expiration durations or even choose NOT to cache certain file types (because, for example, they will be modified very frequently) which would be difficult for the plugin to account for. And, not everyone uses Apache. Some use Windows, etc. Those are just some reasons that occur to me. I notice that the developer don't even write to your .htaccess file if you choose the mod_rewrite method, which they could do if they wanted to (other plugins do) so I presume they have made a decision at some point that there are good reasons to leave all things .htaccess related up to the end user. Again, I am not speaking with any authority, just telling you a few thoughts that occur to me.

Sergey9999 on "[Plugin: WP Super Cache] Google PageSpeed Insights suggests "Leverage browser caching""

0
0

mojamba, wow!!! This is the answer! I think you replied to many people that have the same question. Thk bro!

mojamba on "[Plugin: WP Super Cache] Google PageSpeed Insights suggests "Leverage browser caching""

0
0

Glad it helped. Good luck with the PageSpeed optimization.

sterndata (Steve Stern) on "[Plugin: WP Super Cache] Google PageSpeed Insights suggests "Leverage browser caching""

0
0

Mojamba: +1 on the thanks!

Viewing all 3480 articles
Browse latest View live




Latest Images