Ok it turns out you were right, but I think this is going to be some sort of combination effect problem. ie several factors are involved in this equation. The only thing that stops the php error from occurring is deactivating WP Edit. I checked your server’s php settings and you have Xcache, Suhosin, ZendGuard and ionCube in the mix so I disabled each of those things individually and the php error was still occurring. You have ZenCache installed so I disabled ZenCache and tested things – same php error occurred. I found a coding mistake (left over code) in your wp-config.php file: define('RELOCATE',true); which I commented out. After looking at a lot of different things and changing php server settings and other plugin settings (ie turn on, off, deactivate, etc) the same php error was occurring. Deactived WP Edit and the php error is no longer occurring. I also upgraded to the latest WP Edit version that was just released and the same php error was occurring. So I will look at the WP Edit code some more, but this same php error is not occurring on my test site with WP Edit installed. So that leads me to believe the root problem still has something to do with your particular server and a chain reaction/combination problem is occurring.
This is important and may be the actual root source of the problem. When I turned off Xcache your php server info still showed that it was loaded. So that might mean that your server is hard loading Xcache from the server’s php.ini file and you cannot actually really turn off Xcache locally on your website. This is something that only your host support can tell you for sure if that is occurring and also check if Xcache is the root cause of the problem by disabling and enabling it. It is logically a very possible cause of this type of double loading problem.
- This reply was modified 22 hours, 56 minutes ago by AITpro Admin.
- This reply was modified 22 hours, 55 minutes ago by AITpro Admin.