Same issues here… Some serious bug with 0.9.2.4
I updated to 0.9.2.4. I immediately noticed problems, with error messages, etc.
I then reverted back to 0.9.2.3. No error messages, etc.
But when I view the bottom of my home page, I no longer see the caching metrics I usually see in the comments. When I ran with debug, it wasn’t even caching my homepage, saying that the trailing slash prevented the page caching from occuring.
I use to see the following before .4, now after reverting to .3, I see nothing. Please help!!!
Rich
<!– Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/
Minified using disk
Page Caching using disk (enhanced)
Database Caching using disk
Object Caching 1620/1621 objects using disk
Well, I figured out why I’m missing all the data I use to see in the comments.
I tweeted about W3TC from the plugin admin pages, and that seems to be some trigger that hides that info. I’m not sure why…
is_supported() is now true on my site, so it changes the comment data output…
Anyone know why?
Rich
if ($this->is_supported()) {
$buffer .= sprintf(“\r\n<!– Served from: %s @ %s by W3 Total Cache –>”, w3_escape_comment($host), $date);
} else {
$strings = array();
if ($this->_config->get_boolean(‘minify.enabled’) && !$this->_config->get_boolean(‘minify.debug’)) {
require_once W3TC_LIB_W3_DIR . ‘/Plugin/Minify.php’;
$w3_plugin_minify = & W3_Plugin_Minify::instance();
$strings[] = sprintf(“Minified using %s%s”, w3_get_engine_name($this->_config->get_string(‘minify.engine’)), ($w3_plugin_minify->minify_reject_reason != ” ? sprintf(‘ (%s)’, $w3_plugin_minify->minify_reject_reason) : ”));
}
if ($this->_config->get_boolean(‘pgcache.enabled’) && !$this->_config->get_boolean(‘pgcache.debug’)) {
require_once W3TC_LIB_W3_DIR . ‘/PgCache.php’;
$w3_pgcache = & W3_PgCache::instance();
$strings[] = sprintf(“Page Caching using %s%s”, w3_get_engine_name($this->_config->get_string(‘pgcache.engine’)), ($w3_pgcache->cache_reject_reason != ” ? sprintf(‘ (%s)’, $w3_pgcache->cache_reject_reason) : ”));
}
I tweeted about W3TC from the plugin admin pages, and that seems to be some trigger that hides that info. I’m not sure why…
Well, “is_supported” is linked to the “I’ve tweeted” checkbox in the General tab of W3TC.
Here’s proof that it is linked :
function is_supported()
{
return ($this->_config->get_string('common.support') != ''
|| $this->_config->get_string('common.tweeted'));
}
You can uncheck “I’ve tweeted” I believe.
“is_supported” means something like “I offered support to the author of the plug-in, therefore he is rewarding me by removing nag messages from the bottom of my pages”. But apparently you don’t consider it as a reward 🙂
Yes, I saw this code and understand it is the trigger.
My question is *why* is this a trigger to hide potentially valuable/interesting information that previously was shown in the comments? It makes no sense to me.
I’d rather not uncheck the “I’ve tweeted” thing, since it will probably show the nag popup again (though I haven’t tried this).
I’d rather not uncheck the “I’ve tweeted” thing, since it will probably show the nag popup again
The nag popup will show, but on this popup, there is a “Don’t show this message again” button.
My question is *why* is this a trigger to hide potentially valuable/interesting information that previously was shown in the comments? It makes no sense to me.
I think I explained already. What you call “valuable/interesting information” is actually an intrusive and unwanted ad. I personally hate it. I spend hours minimizing the size of my HTML files, and then W3TC stupidly inserts 5 lines of ad on bottom of these files.
That’s why W3TC rewards users who have tweeted/linked, by removing the ad.
I see your point. I was relying on this info as debug info, instead of turning on the debug mode and was always using this info.
In any case, I hope .4 is fixed soon. I turned on debug in .3, and realized my home page isn’t even being cached because of a trailing slash in the URI. I think this is fixed in .4, but had to revert because of other issues it has. Looking forward to the caching of my homepage soon.
Rich
One more thing that happened is that WordPress SE0 plugin lost half of its settings.. had to go back and reconfigure again.
I’m sure Frederick is working on a fix
