Jason

ok thanks for that – i was able to reproduce the problem. It’s pretty weird – I’ll have to do some research to see what’s going on. In the meantime, if you need to get it working, perhaps changing one of the settings I guess..?

I don’t know if this is what you are doing, but here is what happens on my test install

https://www.youtube.com/watch?v=ZK9du-JIU5o

Do you by any chance have any other plugins installed? I have a default WordPress install of 4.4 and the media library editor seems to work normally with Imsanity installed.

The “original” size image is rarely used anyway, so it doesn’t really make any difference.

Just make sure you have your imsanity size limit set to a size that is not too small for big screens Personally I think 2000px is more than enough for just about any screen. But if you have an image that is supposed to fill up the entire browser window (like a full screen header) then you can still add -noresize to your image filename and Imsanity will leave it as-is.

I tested the feed url of “https://www.whtop.com/rss.reviews/netfirms.com” and it seems to work just fine.

Make sure your URL doesn’t have any special characters in it (look at it in Text View to be sure). The only other thing I can think of is that WordPress might be out of date?

Cool glad you got it working – thanks for posting a follow-up in case anybody else has the same issue.

Hmm, I don’t really know what the issue could be – I’ve never seen it happen before. There must be something unique about your setup, but I can’t see what the problem might be unfortunately.

Hmm I don’t think this error is coming from Imsanity, but Imsanity is catching it. There’s no text that matches that in the Imsanity codebase or WordPress itself. Is it possible that GD isn’t installed or configured correctly, or perhaps there’s another image-related plugin?

Imsanity works on multisite installs – I have it running on my own server right now.

GD is a bundled extension with PHP. I’d be curious to know how or why someone ends up with a PHP installation that doesn’t have GD?

glad to hear it – that would be a good option. I’ll look into that and see if it would be easy to do. It’s kinda weird because the DB drop-in that controls the cache happens at such a low level in the WP workflow – before any of the page rendering even happens. That’s the reason why I put all the settings in wp-config instead of a UI. Clearing the cache might be ok to do at the UI level though.

Thanks for checking the plugin out!

Hmm it’s possible i might just have to remove that setting and have “images uploaded via pages” and “images uploaded elsewhere”

The problem is that WP doesn’t officially provide any way to tell where the uploads came from. I’ve put in hacks and such that I’ve observed that *usually* detect where the upload came from. But the WP developers seem to insist on fiddling with things from one version to the next. I’ve fixed this issue about 5 times already and I’m just not sure it’s worth it to me to keep guessing what they’ll do next!

Generally if you need to keep the high-resolution images, then Imsanity is not a good plugin for you.

However, many specialty plugins have their own upload system which skips the normal WordPress API and, in which case, anything uploaded into that plugin might be ignored by Imsanity (you should test this to be sure though).

Lastly, any image that you add “noresize” to the name will not be resized. For example my-image-noresize.jpg – that filename tells imsanity to ignore that file.

the transparency is only removed if you specify that you want PNGs converted to JPGs. JPGs don’t support transparency so what was happening previously is that transparent parts of the PNGs were getting converted to black. There’s really no way to know what color the transparency should be, but white is probably the going to the best guess most of the time. Certainly better than solid black.

If you have a lot of PNGs with transparency, then it’s definitely better to leave that setting off, and Imsanity will just keep the files as PNGs and preserve the transparency.

It actually would need to be the other way around – UPME should update their plugin so that it fires the wp_handle_upload hook and then it will work with any image processing plugins (including imsanity).

What can I say, I like dark, creepy imagery! Also I’m a lousy graphic designer. But I understand some people don’t want to see the image which is the reason for the setting to hide it.