Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 9000 bytes) in /nfs/c01/h04/mnt/1234/domains/mydomain.com/system/expressionengine/third_party/imgsizer/pi.imgsizer.php on line 555 What does this mean / how do I fix it? Using: {exp:channel:entries channel="releases" sort="desc" limit="1"} {exp:imgsizer:size src="{release-front-cover}”} {sized} {/exp:imgsizer:size} {/exp:channel:entries} In EE2.02.
I’ve had that happen before. Have you used this plugin before, or is this the first time? When I initially set it up I had something wrong in the path settings I believe. Recently I switched to ED Imageresizer, due to some errors I was getting like this. (Was trying to resize a 9 meg image, and kept getting these out of memory errors).
Roger that. Makes sense 😊. Anyone read or seen a comparison of the two, feature or performance wise? Been away for a while and not sure what the consensus is or if one of them is deprecated and/or tapering off in development. Always been happy with imgsizer but I thought I would ask.
If anyone wants to get the plugin to crop from the top rather than the centre, I ammended the following on line 598. Seems to work ok.
//imagecopyresampled($image_resized, $image, -$int_width, -$int_height, 0, 0, $adjusted_width, $adjusted_height, $width_old, $height_old);
imagecopyresampled($image_resized, $image, -$int_width, 0, 0, 0, $adjusted_width, $adjusted_height, $width_old, $height_old);
Basically replace -$int_height with 0.
I’m finally getting around to replace php thumb on a site and I use related entries to output the photos. Is it possible to use the related entries tag inside the URL parameter of the plugin to set the URL output? Also, would like to use a conditional too. I’ve tried parameter parse=”inward” and no luck.
I’ve placed the plugin into an embed so I can use related entries and a conditional to dynamically update the URL depending on some conditions. It would be great if there was a way to act on the URL in a dynamic way first and then set it in the plugin. The only way I could see doing that as is was passing variables into an embedded template – which really is a poor solution given the overhead of using embeds.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.