Joseph Scott

I’ve just deployed an update to the Jetpack devicepx code to address this. The updated version shouldn’t generate any console log items and still fix the issue with Firefox + Retina squished images.

@cjbos that code is definitely some JavaScript voodoo. Oddly enough that code was added to fix a problem with squished images on Firefox when used on a retina screen. I can’t claim to fully understand why it fixes the issue on Firefox ( I have a few theories though ), but the results confirmed that it did fix the problem. Chrome did not have the problem with squished images.

After several test runs I’ve been able to reliably reproduce the console log errors ( I end up having to restart Chrome after each JS code change, if I don’t the errors won’t come up, even after changing back to the original JS code that cause them ). However I’ve only seen them on Chrome, I haven’t seen any console errors in Firefox ( currently on version 48 ).

I’ve started running tests with permutations of this code to look for a combination that will both fix the Firefox problem, and not generate console warnings. So far they have been tied together, fixing one breaks the other. Still looking though.

I’ve deployed an update to devicepx-jetpack.js that restores the ‘resize’ and ‘srcset’ feature that I’d reverted, with a small change to the logic. It now only applies if there is no ‘srcset’ attribute on the img tag. This fixed the shrinking image issue in my tests.

Thank you for reporting this. I was able to reproduce the problem, there is some interaction between a recent change to devicepx-jetpack.js I made and some themes. While I track this down I’ve reverted the change to devicepx-jetpack.js.

I haven’t been able to reproduce what you’ve described either. If it does turn out to be an issue with a particular browser (or browser plugin) drop a note to [email protected]. If they can reproduce it then they’ll be able to come up with a fix.

Hi, I see that akismet is not free anymore?

Akismet has always been free for personal sites and had paid options for non-personal sites.

As others have mentioned if you don’t want to use Akismet there are some alternatives. I prefer Akismet, but I’ll admit to some open bias there ??

The most obvious alternative is to moderate all comments. Depending on the volume of spam and the time it takes them to review all of them they may find that $5/mo is a pretty good trade off.

Try the admin.php file from Akismet plugin -trunk at https://plugins.svn.www.ads-software.com/akismet/trunk/admin.php

You should contact Akismet using https://akismet.com/contact/ to find out the status of your account.

Akismet doesn’t interact with your email account, it only checks comments submitted via WordPress for spam.

This message means what it says, for some reason your WordPress isn’t able to reach akismet.com in order to validate the API key (and likely to check comments for spam).

Your hosting provider is generally in the best position to track down why your site is not able to make HTTP calls to akismet.com any more. Common reasons for this include a firewall/proxy/router that is blocking the request, PHP configuration that disables HTTP calls.

Version 2.5.3 of the plugin is available at https://downloads.www.ads-software.com/plugin/akismet.2.5.3.zip

If your host isn’t willing to update versions of PHP that have officially been deprecated years ago then it is time to start looking for a better host.

The proper fix is to upgrade from PHP 4 to PHP 5.2 or higher. WordPress no longer supports PHP 4.

When you are viewing the Akismet configuration page are you using an administrator account?

On the issue of being marked as spam, have you checked the comment history to make sure Akismet was what marked it as spam? If it is, are you logged in when you leave a comment?

The Akismet plugin error means what it says. At one point your WordPress install was able to reach akismet.com to verify your API key and check comments for spam. It now isn’t able to do that. Your hosting provider is in the best position to track down why your WordPress install can no longer make HTTP requests to akismet.com.

I saw you tagged this and the other thread with ‘akismet’. Was there something specific about the Akismet plugin that was causing problems?