Demi

I turned off the Minify option completely and the Fatal Errors in my logs stopped to appear. Also I investigated my older error logs and I discovered that this issue was persistent before WordPress 4.0 upgrade. Therefore, I can conclude the following with 100% certainty:

.
1. After WordPress 4.0 upgrade CDN is no longer working in the dashboard despite the fact that the option “Disable CDN for the following roles” is not enabled.

.

2. When used, W3TC Minify option produces PHP Fatal Errors which are recorded in the server error logs but not manifested on the frontend thus they’re not breaking the site. They contain the following message: “Call to a member function get() on a non-object in …/wp-includes/cache.php on line 113”

.

3. When used, W3TC Minify option strips the comments that W3TC is generating at the end of the html.

I know… Jesus. I’m just pointing to a discussion with exactly the same problem in mind where a caching plugin is involved. Just a thought, in hope you can extract some info to make W3TC better.

Here’s another one: https://ww.wp.xz.cn/support/topic/plugin-wp-super-cache-call-to-a-member-function-get-on-a-non-object-in-cachephp?replies=24

Okay I will send you a note. For points 1 and 3 I’m 100% sure it’s W3TC fault. But for the second point I need to monitor the errors for a day.

I switched minify to Disc and the errors now appear on an hour or two. They’re not so frequent as they were. But I need to observe this over high traffic period to confirm it. Also I need to rule out YARPP because that plugin is also utilizing cache.

It is in the first block of the sitemaps config page. “Notify Search Engines about your sitemap or your main sitemap and all sub-sitemaps now.”

Are you absolutely sure you’ve included this option in 4.0.5 since I don’t see such a thing. I only see Notify Google about updates of your Blog, and Notify Bing (formerly MSN Live Search) about updates of your Blog. But those are not new options and they don’t do manual ping at all.

That is the “Override base URL” field. See here for instructions.

There’s no “Override base URL” field in the settings page in 4.0.5. Along with that playing with .htaccess is not an option for some users… or most of them I would say.

One person confirmed that these options do not exist in 4.0.5. Can someone else chime in and take a look at this please?

Sorry I can’t reproduce the problem with the missing pages. The SQLs are nearly the same, and they also don’t change (so they should always produce the same result).

You should try on a site with thousands of URLs… created over 5-6 year period. In almost every sub-sitemap (monthly archive) there’s 1-2 posts missing. I’m not sure what’s causing this but it’s 100% there.

3. Also, after the update, I couldn’t change the priority for categories until I realized that you have to change the priority for tags if you want to change the priority for categories.

Conclusion: The priority feature for categories is not working.

That is fixed now @frederick, but W3TC 0.9.2.8 has some other issues:

1. Scheduled posts not working at all. W3TC is messing up with the crone.
2. Single pages/posts can not be cleared from the cache. If I want a single page to be cleared I have to clear the whole page cache (thousands of pages).
3. Consumption of APC memory is doubled (database caching), presumably because you’ve changed the way queries are handled now.