pubwvj

I’ve been having this problem recently too. Akismet used to work fine for me. Now it is missing a lot of spam. I have gotten the error above and this morning after getting emailed about 608 spam I checked Akismet and saw:

“The key below was previously validated but a connection to akismet.com can not be established at this time. Please check your server configuration.”

but below that it says:

“All Akismet servers are available”

Much of the time Akismet is working and it has worked fine for years so I don’t think there is any problem with my host setup. Rather it appears to that the Akismet servers are intermittently down. This isn’t a one time thing but has been happening time-to-time for weeks.

I love the assistance Akismet gives when it works. Hope it gets back to business and smooths out soon.

Same thing here. Recently I’m getting a lot of spam comments that Akismet used to catch and is no longer catching.

I started noticing it either this August??? or fall.

I understand quite clearly what the color profile is. However WP is discarding it when WP re-saves files such as resizing headers. That is the bug.

Calm down. Take a deep breath.

This bug needs fixing. I’ll work around it by simply FTPing. However, as you noted, 60 Million other users are being affected too and many of them won’t know how to work around the problem. I simply want to report it so that it might be fixed. I can reproduce the error. I realize you can’t see it but the bug is still there.

I did carefully read those pages. They stated that WP is discarding the color profile. WP should not discard the color profile because by doing that WP is altering the colors the users will see. This is clearly a bug. Why are you attempting to block my reporting it?

I don’t see how the GD library would be an issue here.

WordPress uses the PHP GD Library module.

Yes, that was what I understood from you question and what I replied to the web host.

Apparently this is a known bug as per the WordPress page linked above. I would like to report it with my samples in the hope that this can get fixed. WP shouldn’t mess with the color profiles.

Thank you, WPyogi. So the problem is (from that thread):

“When WordPress resizes the image the colour profile is stripped out so the image looks different.”

and from the second link:

If the colors in your uploaded images appear different from the originals, make sure you are saving your images in sRGB before you upload them. The sRGB color profile will work the best for resized images on the WordPress.com servers. Keep in mind that some sRGB images still may have slight shifts in color when they are resized on the server.

The above indicates this is a known problem. It should get fixed. When I upload images via FTP avoiding WP messing with resizing them I get my colors, not WP’s alterations to the color.

I would like to report that as a bug in the hopes that this could be fixed. When resizing, saving, etc images WP should not be throwing away the color profile information since doing so will change the images color as demonstrated both in my samples and in the samples the user gave in that thread.

Where is the proper place to report that since the moderator Esmi does not want me to do that in the feedback forum?

I just got a response back from my web host on the question of the GDLibrary. They said:

Did you recently upgrade your WordPress version? What was it before?
I don’t see how the GD library would be an issue here.

Actually, it is there. You and many people might not have noticed it but the problem is real. I’m not asking you for help. I’m trying to report a bug. You’re blocking my attempt to give feedback because you either haven’t looked at the sample I gave or perhaps you are not able to see the differences – some people have less acute color vision. But the problem is real. Just because you can’t see it doesn’t make it go away.

I attempted to report it in the feedback forum and you deleted my post. It was not a duplicate. I had updated it with new information and noted that I was attempting to move the report to there since it was a feedback on a bug.

I would appreciate it if instead of blocking you would simply direct me where to report this.

Hmm… So perhaps 3.4 was when the bug got introduced. WP is definitely changing the colors in the header from the original pre-upload image. That is clear from the samples I provided. I can provide original sample files to help track down the problem. Is this the right place to report it or should I report it somewhere else?

What about with 3.6?

3.5?

At some point this changed because older WP versions didn’t do this. This is something new. I tried to move this discussion to the feedback forum since it is a bug. How do I do that? When I reported it there you deleted my post which explained I was attempting to move the thread.

Hmm… Yet it didn’t start happening until the new version of WP and it only happens with files WP edits such as the header uploads, not with my images which I independently FTP to my server and then display on my pages. Same image, one through WP which is munged and one through FTP which is fine.

I made a post with the same image as the header – different crop but it shows the same section. This shows the color problem. The post’s image was not manipulated by WP. The header was. The header colors are altered and dull.

For comparison, the sunflower picture below the header is showing the right colors. That is an image I FTPed to my server and then linked to as I normally do for images. So something that WP doesn’t resave is fine but something that WP processes ends up with muted colors. Makes October look like November.

I’m suggesting that as a WP needs to make a greater effort for legacy support.

Core should not change such that things that were compatible and followed the rules become incompatible. The theme 2010 is a prime example of this.

The engine can change but the themes and plugins that are the interface to the users, the readers, should be able to still be used.

Security =|= legacy issues.