billrose

Thank you Sean!

Hi. The update did not fix my problem. Any suggestions?

Hi iLen. Have you been able to correct the problem yet? Please let me know. Thank you.

Hi iLen. I am using a theme called Salient that I purchased from ThemeForest.com. It seems that Yuzo is detecting post content in both areas of my site (main content and sidebar), but I do not want it in the sidebar. Do you know how to fix this? Thanks.

@mcguive7 Thanks for the reply. Perhaps I need to find another solution since those options are beyond my ability.

If anyone else has suggestions I am open to hearing them. Thanks.

Was having the same problem but solved it by deactivating the ‘WP User Avatar’ plugin. Must be a conflict. Hope this helps some of you guys.

I had the same issue yesterday. This thread solved it for me.

https://www.ads-software.com/support/topic/w3tc-0928-killed-my-backend?replies=4

Also, you have to delete (not just disable) the CloudFlare plug-in to make the error message go away.

@m Asif Rahman – Thank you, that solved it for me.

@andersvinther2 – Appreciate you detailing the steps. I needed that!

I’m getting this same error message myself, but haven’t yet taken any action with CloudFlare. I first want to understand whether this error message is true… Does CloudFlare really not offer me anything beyond W3TC? I would question that simply because the W3TC plugin is likely the one delivering that error message.

UPDATE: Nevermind. I just found this which negates my conspiracy theory.
https://blog.cloudflare.com/w3-total-cache-w3tc-total-cloudflare-integrat

Thanks esmi. I’ll give it a try and report back.

– deactivating all plugins to see if this resolves the problem. If this works, re-activate the plugins one by one until you find the problematic plugin(s).

– switching to the Twenty Eleven theme to rule out any theme-specific problems.

My concern would be that the plug-ins and theme settings would be ‘forgotten’ if I deactivated then reactivated them, causing a heck of a mess to clean up afterward. Is that concern unfounded?

– resetting your custom permalinks back to the default setting via Settings -> Permalinks. If this works, then set a custom permalink structure back up again.

I’m looking to solve this problem without making any changes to the existing permalink structure because of the potential negative SEO implications.