J.D. Grimes

Are you using the latest version of CubePoints? The database table name is now cp not cubepoints.

Thank you for the help, Mark. This is now fixed.

It turned out that admin-ajax.php was password protected. I made an exception for it, and now things are working great!

Yes, I am seeing the “0”.

I have the whole /wp-admin/ behind a second password, but I don’t think that it’s causing a problem. The live traffic is working perfectly.

I am using 3.5.2. I checked that file, and the variable is there:

//Clears next scan if scans are disabled. Schedules next scan if enabled.
/*879*/		if($err){
			return array('errorMsg' => $err);
		} else {
			return array('ok' => 1, 'reload' => $reload, 'paidKeyMsg' => $paidKeyMsg );
		}

That probably has nothing to do with the problem though.

Here is what is in the “detailed activity” section after about 12 hours installed:

[Feb 06 01:46:32] Scheduled Wordfence scan starting at Wednesday 6th of February 2013 01:46:32 AM
[Feb 06 05:48:29] Scheduled Wordfence scan starting at Wednesday 6th of February 2013 05:48:29 AM
[Feb 06 08:51:33] Scheduled Wordfence scan starting at Wednesday 6th of February 2013 08:51:33 AM

There is nothing in the “new issue” area.

Here’s a tutorial I wrote on it.

It turned out that this was actually caused by a problem with the configuration of PHP on my server. I was unnecessarily using mbstring multibyte function override. Now that I have set that back to 0, the error is gone.

Sorry for the false alarm. ??

Okay, I think that I have fixed this. It was a problem with the PHP configuration on my server. I was using the mbstring.func_overload directive, and that was causing some problems. Once I set it to mbstring.func_overload = 0, everything works fine!

Thank you for walking my through this! I am so glad to get this figured out!

Actually, I am still getting the error. I just tried it in another browser. My browser was just using the cache.

Okay, I just removed them. I am not getting the error now. But it did get logged several times last night.

A plugin. Which I still have disabled… ??

You said that you aren’t having this problem on any of your WordPress instals. Do you have PHP error reporting set to log PHP Warnings? And are you using PHP 5.4?

Should I keep plugins deactivated, or do we know enough that I can activate them again?

Thanks for walking me through this so far. I appreciate it. ??

P.S. Above I said that the error occurs on the /feed/ page for a page that has no posts, I meant comments/posts. Actually, if you visit the feed for any page/post it logs the error, whether it has comments/posts to display or not.

The error occurs when a /feed/ page is visited that doesn’t have any posts to display. Visiting efieldguide.com/feed/ doesn’t seem to give the error, since it has posts to display. So I guess either something isn’t set up properly, or the values need to be checked with empty() before they are used in those places.

Sure: https://efieldguide.com

It’s not pretty with everything disabled.

Unfortunately I am still getting this error. However, I figured out that the problem was not wp-cron. The error occurs whenever any of the /feed/ pages are visited. I guess it has something to do with RSS instead?

I still have all plugins deactivated and the 2012 theme activated.

I can create the error by visiting any of the /feed/ pages.

I tried loging in via another browser, and then checked the access logs, and wp-cron didn’t run. So I guess now I just have to play the waiting game. I will keep checking the access logs.

I did have a small issue when I upgraded to 3.5. The wp-includes folder wasn’t writable. But after I changed the permissions the install went fine. Maybe I missed something though. Hopefully this has fixed it. We will see. ??