Jason

You could if you like go into the imsanity code and just change the setting at the top “IMSANITY_AJAX_MAX_RECORDS” from 250 to any higher number. It might cause the browser to hang at some upper limit – 250 is just a conservative limit. But I think several thousand would be possible.

I agree though a command-line utility would be the nice. If it’s purely disk space, then imagemagick can do that already, but it won’t update the wordpress “quota” amount unfortunately.

Hmm, can you check this out and see if there is any info in the debug console?

thanks

BRM appears to be a copy, the author credits Imsanity on the description page. I’m not sure if functionality was added or it’s just a branding change. Perhaps the author wanted a piece of the massive cash cow that is Imsanity!

Hmm, if you change the zero to a really large number like 100000 – does that make any difference?

It seems like a lot of people are having the issue – can you tell me the max sizes that you have configured? It seems in some cases setting the value to 0 might cause this.

You need to allot more memory for PHP – most likely a certain image is a bit larger than the rest and is causing PHP to use a lot of memory. Here’s some info on how to configure memory for PHP: https://stackoverflow.com/questions/4096582/allowed-memory-size-of-x-bytes-exhausted

The problem is that WordPress has a table called wp_meta and this is where it stores the info about the images, as well that is where Imsanity reads from. So your original images have been replaced but WordPress still thinks they are the new size.

To fix it you have to put the images and restore the DB as well, or at least the wp_meta table.

The original images generally aren’t used most of the time on a page, the Large, Medium and Thumb are the images that are used most of the time. So it doesn’t really hurt anything to have the mismatch besides being kinda an annoyance.

If you could post the output from the ajax post that would be great. Here’s instructions on how to do that: https://www.youtube.com/watch?v=YEYPsAj8TXI

I just added this in version 0.0.6 – using google’s free reCAPTCHA service. You can find it in the Settings page for SimpleSecure. Adding your reCAPTCHA Site Key and Site Secret will enable reCAPTCHA on your forms.

This is quite an odd error and it makes me thing that ESPN is doing something on the server to cause this. The reason I suspect it is because I created a feed-burner proxy to the feed at https://feeds.feedburner.com/espnmediazone/Evlx – and if you notice, it also pulls the wrong content. So that kinda takes HungryFEED out of the equation.

Perhaps they are checking the referring agent or something similar and defaulting to the main feed instead of the tags?

Thanks, unfortunately there’s no “official” way to determine where the images are coming from, so I’ve just made assumptions based on what I can see in my own WordPress installation. Apparently something has changed again so I’ll see what I can do.

It’s annoying that there is no official way to figure this out from the API, but perhaps I’ll figure something out. Thanks for the report.

It’s bit of a unique request, but it can be pretty easily done with a bit of custom CSS code like so:

.hungryfeed_item:first-child {
	display: none;
}

Imsanity isn’t really designed to provide social media graphics, it’s just designed to reduce the size of really large images.

it resizes to scale, so if you set max 200 x 200 then it will be maximum of that size – Imsanity won’t crop the images to be a square.

based on that query you might want to add “g4bad” to your CACHE_READ_WHITELIST and CACHE_WRITE_WHITELIST

If you go to the NLC settings page, there’s some instructions on how to debug using the SAVEQUERIES and DEBUGQUERIES settings.

I’d like to make it more simple to do with a control panel or something, but since the DB Drop-in loads itself prior to any plugins being enabled, and also because I wanted to avoid doing any DB queries for the plugin itself – so all of the debugging is done using constants in the wp-config.php file.