DOCS:
how to use ad system
https://forum.tagdiv.com/ads/
example of putting your own ad code in the header box
<div class="td-visible-desktop">
</div>
<div class="td-visible-tablet-l">
</div>
<div class="td-visible-tablet-tp">
</div>
<div class="td-visible-phone">
</div>
DOCS:
how to use ad system
https://forum.tagdiv.com/ads/
example of putting your own ad code in the header box
<div class="td-visible-desktop">
</div>
<div class="td-visible-tablet-l">
</div>
<div class="td-visible-tablet-tp">
</div>
<div class="td-visible-phone">
</div>
Well… you realize that the purpose of that lineup in the robots.txt file and hence the words “disallow” are intended to tell Google and other bots what *not* to spider or look at (e.g., friendly blocking).
Anything you don’t want blocked shouldn’t be there.
Anything you do want blocked should be.
Some people have just taken to removing all that stuff for WordPress.
For instance my code in the examples from my optimization sticky effective disable trackbacks.
If you don’t have an affiliate (“aff” ?) folder — no need to block it.
If you don’t have a cgi-bin folder … why block it?
With “search” — I am not sure yes/no on whether that should be blocked since technically you do want Google to “discover” your search to add the new site search hinting.
For instance the Yoast site got rid of all of those items entirely.
So, upshot — unless you KNOW WHY you’re blocking something, why block it?
Some hosting companies have an old default robots.txt template that gets built “for you” which is how you might have ended up with that — but in most cases, really not needed now.
Those are only “guidelines” anyway — they don’t really block anything except those ‘bots that adhere to your “request” not to look in those folders. They are not actually “real” blocks against anybody.
Weird. Perhaps you have some caching turned on conflicting with that, and so serving up old version of image.
This image is pretty big
http://evolvehype.com/…ploads/2015/03/ehlprodivision-100×65.jpg
254 KB (260,690 bytes)
with a quality factor of “50” — and images re-generated
generally speaking the size would/should be roughly 3 KB
perhaps you have some aggressive caching turned on? YOu need to turn that OFF before running the regenerate-thumbnails …
also make sure your functions file has the RIGHT code to do that — check it against my optimization sticky at top of forum as my code from functions.php is also there.
It does work 🙂
I usually look at the support issues for the plugin before trying it at all …
doesn’t look very promising based on this … not updated since 2013 — also worrisome as anything pre WP 4.1 and new field updates in WP 4.2, might not be best choice for any caching/optimization duties …
https://wordpress.org/support/plugin/wp-widget-cache
I guess it depends on what kind of widget you’re caching …. probably a dbase query to load related posts wouldn’t work; nor would “latest posts” probably.
Not sure if WordPress caches any of that by default, e.g., checking for latest comments EVERY time page is loaded, or once per hour or what.
Good idea … not sure how to execute that …
this is kind of interesting and I have not yet had time to try this out — since you asked 🙂 :
http://generatewp.com/use-transients-speed-wordpress-widgets/
