well may-be I can add some math that says, files size x estimated process constant /php mem limit < 1 equals true... then not process the image, go to the pass-through with an error. This would do one thing thou, it'd be running every time till the error is taken care of. Otherwise it only takes the time the first time.
May-be I can just infer this state without the math but atm I can’t think of a way... The issue is that when the error occurs, the reason for the head dropping out as you saw was that everything stopped processing, and with that I can't pass an error after the failed image processing due to lack of memory.. I have to predict the fail state. I'll see what I can think of... May-be I'm over thinking it...
Cheers -Jeremy
Last edited by JeremyBASS on Tue Mar 23, 2010 3:15 pm, edited 1 time in total.
Great feature, which I want to use in the News Module. To every article, there is a photo shown. Therefore I've set a custom field which is called image_1 and that's how I used to implement it in my site:
So there is already a rawurlencode in it. I didn't look back when I introduced this, but it must be there for some reason (bug report?) Do you have this in your code also?
hmmm... I thought it was the larger file that was the problem, however, it appears as though it is not that...possibly something to do with cmyk/rgb or something. i cant look into it properly at the moment to give you a better diagnostic as i leave my job tomorrow and have shed loads to do.it was wiping out the again with a 500k image when the memory limit was set to 10...unless heart have some kind of limit which I cant control?
i am using the supersizer about 10 times on one page...that is probably the problem...so i can have as many photos as i like, up to a certain size? does that help?
Last edited by porridj on Thu Mar 25, 2010 4:16 pm, edited 1 time in total.
...upped the memory limit to 60M and it worked, I didnt realise the supersizer would need the total memory of all the files its referencing put together...makes total sense in hindsight though.
Hope this helps other daft people like myself
Last edited by porridj on Thu Mar 25, 2010 4:17 pm, edited 1 time in total.
jeremy, thank you very much for this awesome plugin. would you be so kind and update your very first post? last update was on 23 Dec 2009. and i assume you added some new features which are not included in the first post?! and did not follow every post here. THANKS
oh.. dang.. I've been so under water with work.. it's on my list.. but the major new one is the overwirte param.. now you can overwrite the original which is good to make a udt and attach it to an event and size images on upload... ect.. I still need to release it lol.. gosh I'm behind.. didn't help that I had a raid crash yesterday... -J
Since no one answered me so far and I don't think that nobody has a clue how to solve this problem I dare posting my post again
Would be lovely if anyone has got a similar problem or a guess!
Greez Opa
opawaldburger wrote:
Hi!
This is a great feature, which I want to use with the News Module. Next to every article there is a photo shown (already, but so far with a big resolution).
So far I've set a custom field which is called image_1 and implemented it this way in my site:
What is outputting with {supersizer path='$location/$image_1'} .. stet... you can't use {supersizer path='$location/$image_1'} the ' does let the var process.. use {supersizer path="$location/$image_1"} try that with the dbl quote... there is at least 4-6 people in this post alone that have posted code for news and have it working so that is mostly like it... HTH cheers -J
I have an excuse I didn't look trough every post here so I used the search, which didn't show me a single post concerning "SuperSizer News". So I thought that there might be none... Thanks for you help so far