darrencss
Forum Replies Created
-
@tacoverdo
So what you’re saying, effectively, is this isn’t going to be changed?OK, I have several sites all on genesis themes and the issue is replicated on all sites to a varying degree.
This is an example where some pages have the issue and some don’t. Cache has been fully refreshed.
http://decoratingadvice.co.uk/If it’s still there, please post the link to the page you’re seeing this problem on.
To achieve what exactly? It’s still there, just believe me.
It’s not a caching issue
I find the feature really useful as I have a very bad memory. Everytime I update the plug-in (see below) I instantly forget I have done so – so it’s helpful to be reminded – constantly.
I just wish every plugin creator would follow suit. Just think how wonderful that would be!
It’s also worth adding how grateful I am that Yoast always push out updates full of bugs, life would be so boring otherwise.
Keep up the good work guys!!!
Forum: Plugins
In reply to: [WP Super Cache] Levarage browser caching using WP Super CacheYou have to do it externally, as you say, via htaccess
In main site settings are the WordPress Address URL and Site Address URL set to https: ?
The problem is that to get a definitive answer you’ll need to experiment with different set ups, and this could be costly?
I’ve heard all kinds of theories about this problem and they all sound plausible. I guess you just have to go with your instincts and see what happens?
Some CDNs allow you to add a canonical header which would mitigate this concern. Some don’t.
However, if your images are now being referenced to the CDN domain you’ll want google to be able to crawl that.
Personally, I think you can do more harm than good blocking stuff in robots.txt. I mostly agree with this thinking:
https://yoast.com/wordpress-robots-txt-example/In your themes functions.php just add:
function wpseo_cdn_filter( $uri ) { return str_replace( 'http://example.com', 'http://cdn.example.com', $uri ); } add_filter( 'wpseo_xml_sitemap_img_src', 'wpseo_cdn_filter' );Replace ‘http://example.com’ with your site url and ‘http://cdn.example.com’ with your CDN url.
(See bottom of the page here)
https://yoast.com/wordpress/plugins/seo/api/You may need to update a post or 2 for the xml sitemap to be refreshed.
If you want to check it’s working go to > /sitemap_index.xml > /post-sitemap.xml > View page source
On the robots.txt issue I wouldn’t worry so much. Let google crawl everything.
Forum: Plugins
In reply to: [WP Super Cache] Mobile Device SupportThe mobile device support is for when you have another plug-in which generates a mobile version of your site.
This predates the adoption of responsive design. I agree the details are lacking and it is confusing.
Forum: Plugins
In reply to: [WP Super Cache] Mobile Device SupportYou can leave it disabled.
Forum: Plugins
In reply to: [WP Super Cache] preload mode is not working at all.I stopped using preload and instead:
In advanced settings > Expiry Time & Garbage Collection
Cache Timeout: 432000 seconds
Scheduler Interval: Once DailyIndividual pages expire after 1 week and are re-cached when a visitor lands. Over time you’ll have a full cache and be refreshing a only few pages, at most, each day.
It works much better and places much less load on your server
I think this is a legacy feature that predates ‘responsive’ templates so you should be able to leave this unchecked?
It would be nice to get a definitive answer but I don’t see any disadvantage.
See related post here
https://wordpress.org/support/topic/plugin-wp-super-cache-what-does-the-mobile-device-support-option-doForum: Plugins
In reply to: [WP Super Cache] google page speed improvementYou should see an improvement in the page speed result but only for pages that have been cached.
Which leads to the second question: A page won’t be cached unless it’s been viewed by a visitor other than you. You can use the pre-load option if you want all pages to be cached at once.