techdruid

Thanks mohammad. I hadn’t even considered it was just WP Cli, as Infinite WP was also having trouble updating the accounts, I just assumed it was across the board. Oops. But yes. I updated WP Cli and I’m not getting the error anymore.

I may be on to something. I’ve got the same error occurring on multiple sites on the same server, but not on other servers. More investigating required apparently.

I’ve got this same error message. And I had thought that I’d be in agreement with you Samuel Wood (Otto) on downloading the ZIP and overwriting. But in doing so, I’m still having the problem. Hrm. I will try once more to upload a complete 4.4 of WordPress to see if it works after the second try.

Where is the delete button for this thread. I guess I just needed to post here so that the solution would present it to me. Obvious mistake on my part.

oh wow. I just realized I had an extra curl_init in there. Ooops. Removing that doesn’t fix it, but I’m trying a couple of other things now.

SortOrder seems to be tied into the constant contact API. I even tried to manually modify the sort order in the database for the widget, and yet the widget still defaults to no sort order at all, except for the sort order delivered by the constant contact API.

Bummer. After spending several hours trying to *finally* implement my Constant Contact signup form the way I wanted to implement it, I’m forced to back-off and NOT implement Constant Contact yet again.

sigh… I certainly can’t devote the time to program my own WordPress plugin. But I can’t display 5+ list options and not have it sorted properly. It just looks unprofessional and difficult to sort through for my customers.

I’m just now looking into this myself. I’m having the same problem.

One of my customers had this same problem this morning. Here was my fix.

1) Restored from the backup from 30 hours ago.
2) Upgraded the NextGEN Gallery by Photocrati plugin to version 2.0.33.
3) Upgraded WordPress to version 3.7

All is well. Thanks to others who indicated NextGEN as the likely culprit. Saved me the hassle. ??

Richard

Um… really? In reading the initial post, this problem I encountered seemed very much similar to the original poster. And if I had went to post an entirely new topic, I think I would have missed a potential interaction with someone experiencing a similar problem. From what I can see, the original poster has not resolved the problem, so this seemed like the most appropriate place to post.

Your instruction to post a separate topic seems counter intuitive, and could potentially result in multiple posts on the same topic without resolution because we’re not communicating with each other.

Weird. I just went in and made 2 additional changes, and now the revisions checkbox is there in the screen options. I swear I had already made 2 revisions. though those two revisions were prior to adding the WP_POST_REVISIONS to the wp-config.php file.

I just encountered this problem on a fresh install of WordPress using Fantastico via cPanel, then upgrading to 3.6 using the WordPress update feature. No plugins enabled at all. I’ve updated the page a couple times, and also defined the “WP_POST_REVISIONS” to true.

Well, I went ahead and made a backup copy of the old plugin from one of my websites. Though I’m hesitant to use it until I understand what happened to the plugin on the WordPress site.

https://techdruid.com/2011/12/14/what-happened-to-wp-recaptcha/

Looks like this may do the trick by using jQuery.

https://stackoverflow.com/questions/910850/jquery-assign-onclick-for-li-from-a-link

Sure would be nice to have an answer to this question. I to am looking to add an onclick to the normal WordPress menu at the “li” level of the menu item.

Hi waltzingmathile,

That change I suggest will help display the “text” field on the profile. But may not actually have anything to do with the warning messages.

It is possible those errors happened on the first signup, and maybe they won’t happen again. have you tried signing up a second person as a test?

I never truly tracked down the exact cause of the error. I can only speculate.

One example of what the error could mean is that the script/program is expecting numbers, but received alpha-text (a-z) instead. I doubt that’s the exact problem, but that’s basically it in non-computer language.