Jack Yan

Jeremy, I also discovered if I add ?ak_action=reject_mobile to the end of the URL, this also works. That led me to wonder if the Jetpack mobile theme was incompatible, but deactivating it made no difference.

Hi Jeremy: thank you, I’d be happy to.

https://lucire.com/insider

I haven’t begun disabling other plug-ins yet (I was about to give that a go), but I have tried the Twenty Twelve and other default skins, and cannot see the related posts yet.

Would definitely like to know the answer here, too; using Nginx and experiencing something similar (and I have tried the things lordsnake has).

Hmm, now I can’t like stuff using the Facebook ‘Like’ or ‘Share’ buttons. I wonder if this is all related.

Hi tanaylakhani:

I now have this error, too, after upgrading to 4.2.0.

The URL on my blog is https://jackyan.com/blog/wp-admin/admin.php?page=really_simple_share_options.

The buttons still show, and, as far as I can tell, the settings I had previously are still there, so it’s not a big drama, but I thought I would report it.

Gosh, you guys could have come back to me on this.

For others who have this problem in future:

1. Re-download Jetpack. (Bear in mind I already had this latest version.)
2. Re-upload Jetpack.
3. Deactivate Jetpack.
4. Reactivate Jetpack.
5. Reauthorize Jetpack and reconnect it to WordPress.com.

It seems Jetpack “forgets” your details after a few years.

OK, the stats are totally dead: nothing at wordpress.com for days apparently.

Does no one have a clue? All my other WordPress sites are fine. Just the most important one isn’t.

The last plug-in update was July 13, but stats died on July 20.

Bump: any clues here?

I’ve had the one API key since I joined many years ago, so the above error message completely surprises me. What do I do?

I am the owner of the API key and I am visiting that page—but there is no way for me to grant access to myself.

Both WordPress and Jetpack are at the latest version.

John, I guess there’s no reason to, since Disqus will take care of the spam filtering. I think the only thing to check is whether we can get Akismet again should we abandon it.

From Disqus: ‘Disqus uses its own anti-spam software to smartly combat comment spam. It was designed to learn over time and becomes increasingly accurate with your moderation activity. Spammers are a prolific bunch, and thus there is always some chance that newer techniques may initially get past the anti-spam.’

I decided to keep both and just have Akismet sitting there. I’m no tech but I imagine if Disqus is doing all the work, there won’t be much load for Akismet just to be there. Maybe someone more knowledgeable can confirm that.

The answer is yes. The key is to export the WordPress posts—pro tip, do it in chunks. Disqus has an import and provided the username for the main site and the WordPress section are the same (Disqus gives you the opportunity to merge them), they will integrate properly.

Disqus has a pretty good FAQ at its own website.

Deleting that file and folder worked. The error message went away but now W3 is demanding that the cache directory be re-created. Once done, all is well.

I have the same issue now. ??

May I ask if there’s a way to do the same—limit the number of thumbnails—when using Tiled Galleries as a widget? Currently my library has 17 but I only want it to show 10.

Thank you, Krishna! That has done the trick.

PS.: I have deactivated all other plug-ins, and activated Jetpack, to no avail. I get the same error.