bolonki

Why donncha call the option:

“Delete the cache only for the page where the comment was made”

just like you wrote above. I think it’s much more clear than talking about a “current page” (which lead the fellow user think you are referring to the Home page) or mention “refresh” (delete cache is less mysterious) and it’s clear the adjective “only” refers to the page where the comment was made rather than applying it to “refresh current page” which is very confusing.

BTW, the cron that’s supposed to trigger the Preload Cache is not working on my install (WP v3.5 with Nginx) and even when I manually do it by pressing “Preload Cache Now” after a while all pages are deleted for no reason (cron job does not work).

Regards

Thanks for your reply.

I still have various issues with SuperCache, but there is no doubt it is a great plugin, take a look at this graph and be proud: your plugin handles 8 thousand simultaneous connections on a single el-cheapo $59 euro/month server! Notice how green the graph is, Donncha like it? Happy St. Patrick’s my friend!

So Donncha, if you don’t use xCache and it’s not good for production use, why does your Super Cache plugin have a built-in link recommending the xCache for WP plugin? I followed your recommendation like a fool…

It’s under the “Easy” tab, with the headline “Recommended Links and Plugins”, number 6 says “Advanced users only: Install an object cache. Choose from Memcached, XCache, eAcccelerator and others.”

By the way, I upgraded to the latest version of SuperCache (v1.0) and it gave me the blank screen of death… looks like it does not like Nginx or something.

Thank you Scribu for your reply.

Removing Pagenavi and restoring the default previous/next system *got rid of the problem*, so it seemed your suggestion backfired. But I still want to use PageNavi because I want page numbers, not back and forth links.

Regards

Over at the WP Page Navi plugin are saying the problem lies with Super Cache plugin. This is a serious issue because it damages blog SEO by multiplying the number of URLs to the same page, really terrible.

Perhaps the issue is WP-SuperCache’s interaction with WP-PageNavi, as I see that both Hunt4Freebies and my site use that plugin for pagination.

On my blog random search strings ‘?s=RandomSearchTerms&sbutt=go’ are being added at the end of the normal pagination ‘/page/4/’ URL

Regards

Thanks LongTail, your plugin and support are greatly appreciated!

Hello LongTail, the JW Player is not displaying the Youtube thumbnail image, I tried several plugins that use JWPlayer (WP-JW-Plugin, Flash Video and your own JW for WP plugin) and none of them displays the thumbnail image on YouTube videos.

I also tried each of the plugins with different versions of the JW player, the latest 5.2, version 4.6 and an intermediate version, and neither plugin regardless of JW version shows the thumbnail image from YouTube. Most likely it’s a change on YouTube’s side, but it’s rather frustrating as Youtube is the premier video hosting site

Hey MichellIrons, there is a BIG difference: akismet and wp stats don’t try to STEAL your users away like IntenseDebate does, they recruit your users into their social network. Very gullible, “fanboy” naive people here, it’s a pity. Automattic bought the IntenseDebate company to exploit the weakness of WP in that area, not out of a desire to improve the open source side (it’s death to open source comment developement as far as WP goes) but out of an intense desire to make money. They tried to stop designers from selling “premium” themes, apparently they don’t apply the same ethics when they slowly colonize the open source platform with trojan commercial plugins like Akismet, Gravatar, stats, comments, and there is more to come will not be on open source. What’s the ethics of a COMMERCIAL plugin being distributed as DEFAULT on an open source platform? How about that blog that gets the real “plugs” on the Dashboard, shamelessly directing thousands of users to a blog with little content but chock full of AdSense? Why is it always THAT blog? But this money-making drive without ethics is not new, I remember when in 2005 Matt was caught stuffing hundreds of hideen links on this very site www.ads-software.com, the “sacrosanct” open source project.

Time for someone to fork out a LitePress like they used to have in 2006, imitate the Joomla move abandoning Mambo.

My concern is that WordPress is becoming Automattically buggier and more bloated with each new release, with CPU and DB queries quickly growing to ridiculous Drupal-like heights. At this rate, WordPress will only be a good match for blogs that have negiligible traffic or sites with major resources (like WordPress.com) but not for middle of the road sites. Even a simple thing like showing Recent comments is going to cost you one MySQL call per comment you want to show, you want to show the last 20 comments? Ok, that’s 20 MORE database calls. Meanwhile vBulletin creates pages with 9 queries total. What happened to “CODE is POETRY”? Good code may be poetry, but WP’s looking like a procedurally verbose rant! The leaders saw dollars and Automattically abandoned WordPress as an open source project.

Thank you Frederick. Care to share how do you use the concept on blogs?

Not sure what qualifies as a “practical case” to you, but I’m working on a site that has an immediate need for this, I’m not theorizing.

Fragment caching takes caching to the next level by allowing you to have a combination of dynamic and static content on the same page, which is extremely useful under heavy traffic because WordPress can easily make 100 queries to create a page, and if you have some “recent” something or statistics that change constantly due to high traffic, fragment caching will allow you to only run the couple of queries that update that stat (“most commented posts” for instance) instead of throwing another 100 queries at the server just because the stat changed.

The WP Widget Cache is actually an example of fragment caching, all those plugins become expensive very quickly, and fragment caching allows you to control the widgets so that they don’t need to be reprocessed just because something else changed on the page.

If you have a lot of traffic / activity, blog stats change all the time forcing to re-create the page and rendering caching ineffectual. For instance, if you are showing the most commented posts (with options to show day, 48 hours, week, month and year) with fragment caching you could set it so the daily stats show in real time and the others are cached recalculating only once at the end of the day. There is no point in calculating yearly stats on every hit.

Same for logged-in users, if you have a lot of traffic you could have a couple of thousand people logged in browsing the site and showing them dynamic pages will tax the server. With fragment caching you could point to the subset of the page that needs to be dynamic for the logged in users and serve the rest cached.

Since English is not my first language and my tech skills are very limited, perhaps you could read about Fragment caching on the Yii Framework for a more articulate explanation of fragment caching and granular controls like route, session, parameter, nesting (inside another fragment that is cached), etc.

I agree 100% with CactusCarl, it is very important to share opinions freely, funny that the plugin is called “intense debate”, apparently not allowed by moderators here.

I intensely dislike the commercial, non-open source nature of this plugin and I’m not even sure they should be listed here on www.ads-software.com as they are looking for a profit. How about me advertising my services here on www.ads-software.com for free? That’s what IntenseDebate is doing, this plugin operates like a trojan horse stealing users and content from your site, and no, it’s not free: you pay dearly with the statistics and users they harvest from your site.

This query optimization was done for WordPress 2.2, before the WP team Automattically stopped caring about the non-profit side of things, and I think they did it with Peter, one of the MySQL Performance guys.

But don’t blame the entire thing on WordPress, the THEMES are to blame for the excessive number of queries and of course the plugins you add. I recently tested a bunch of themes for queries and they ranged from just 13 to nearly a hundred! I tested this on a fresh 2.8 install with just one post.

At some point there was a project called LitePress, which was a WordPress plugin that took control of the blog improving performance dramatically. I think the team should put put out a bare-bones Lite version of WordPress, it would be a big success. WordPress started out as a futuristically simple publishing platform, now it is featureistically bloated and impractical.

So the performance issues are still there, you didn’t solve anything, just threw more hardware at it. Too bad nobody in the WP team cares about performance, otherwise they would have built caching into the core and develop it with fragment caching, etc. like a leading blog platform should do. Incredible that they keep adding bloat and caching is still a plugin (and pretty buggy too).

Hey Fitzpatrick, just took a look at your blog and SuperCache is not properly installed, so you are not reaping the performance benefits.

This is what is says right now at the bottom of your pages:

<!– WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! –>

So fix it and you’ll see a difference, right now your blog is making dozens of queries each time a page is requested.