gaplauche

I’ve confirmed that LastPass for Chrome was the source of the problem for me as well. Thanks, Mike!

Permanently deactivating the extension isn’t an option for me, however; I use it heavily. I tried deactivating it, clearing the browser cache and cookies, then reactivating it, but that didn’t get rid of the problem.

I put in a support ticket with LastPass and here is what they said:

It sounds like LastPass may have over aggressively extra data on April 19th and is now autofilling the date for you. We ran into this issue previously but it is now fixed. However, you still need to recreate the issue for past issues. To fix this, please delete and resave the wordress entry in your Vault. Let me know if this works for you.

So I deleted the website’s entry in LastPass (saving the password elsewhere first), as suggested, then recreated it from scratch. This fixed the problem for me. No need to stop using LastPass.

You might also want to log into your account on lastpass.com, go into your settings, and look in the “Never URLs” section. Delete any reference to the problematic website, if any are there. I had done this before contacting LastPass and it didn’t resolve the problem for me, but who knows — you might need to do it in addition to LastPass’s solution.

I am using LastPass with Chrome, but I only have this problem with one of my several websites.

Oops. Sorry, I posted in the wrong thread.

I’m experiencing the same problem on just one of my websites. When I try to update a post or page, it gets unpublished — the status changes to draft and the month changes to April.

I haven’t been able to determine the cause of the problem yet or how to fix it.

I’m experiencing the same problem on just one of my websites. When I try to update a post or page, it gets unpublished — the status changes to draft and the month changes to April.

I haven’t been able to determine the cause of the problem yet or how to fix it.

So a solution would be to uninstall Jetpack Lite, then use a plugin like Clean Options to clear out the old Jetpack Lite settings before installing it?

@tschaplin I just tried Jetpack Lite 3.0.1 and it’s working fine. 3.0 did give me the OP’s error, however, even with Jetpack installed first on WordPress 3.8.

My WordPress installation is a one-click install on DreamHost, unmodified by me, running the Thesis 2.1 theme.

I’m running the most recent version of WordPress, 3.8, and got the error.

Same here. Even after installing Jetpack first, installing and activating Jetpack Lite causes the error described by the OP.

Assuming Jetpack Lite gets updated to fix this problem, is the new design philosophy going to be as lightweight as before? I’ll end up with two plugins instead of one. Is resource usage going to be heavier now that Jetpack Lite is suppressing most of Jetpack’s features instead of being slimmed down version of Jetpack?

Yeah, my posts aren’t auto-tweeting at all.

I can confirm the same problems and the same warning with Pretty Link Pro on my website, prometheus-unbound.org. Is there a fix imminent?

Same here. Running WP 3.5.1 and Thesis 2.0.3.1.

Me too, on a client site I’m setting up.

It didn’t require that for me.

I’m seeing the same problem with the tag cloud widget in my sidebar. Either the first 45 or the last 45 alphabetically depending on whether I have ascending or descending selected. The counter option for database selection is not working.