Announcement: New plug-in SuperSizer

[JeremyBASS]

Oh yes for sure it works well with the news mod, in fact I have one site that is nothing more than the news mod with images coming from supersizer... it's just you have to do it by size.. like 200x150... what’s the tag you are trying? 

[clj83]

Well, what I am trying to do is setup my news fesubmit with a few image upload boxes without having my disk space at my host filled with ridiculously large photos from the authors who are creating the news posts.

I have everything setup and it all works fine I was just waiting before adding supersizer because I was under the wrong impression that the next release would include an update to allow the original image file to be over written with the same image but of a smaller file size.

Dimension wise I think I will be fine as there is lots of helpful documentation about supersizer but am I right in thinking that even if I use supersizer to alter the pixel dimensions the file size will still be the same or the original file will still be in the cache?

Thanks

Chris

[JeremyBASS]

At this point yes the original is still there... I didn't have time to add that, and I needed to get the parts out I released for a paying client.  The overwrite is on the list.. Just didn't quite get the time it take to make that happen.  cheers - Jeremy

[NikNak]

Hi Jeremy

I have been appraising a lot of different rescaling scripts trying to find one that makes it easiest for my client. For me, the main thing is ensuring that if an image is overwritten, then the script can tell and regenerates the thumbnail. Only one script of the several I have found does this (Google 'dynresize').

I think expecting a client to go and delete the cached file is a bit awkward.

Is this extra functionality something you think could be incorporated? I would prefer to use a plugin supported by the cmsms community

Many thanks

Nik

[JeremyBASS]

By default if you put up an image, and it gets sized and cached... and then you change the base image keeping the same name (let’s say we are trying to cause it to fail) supersizer checks if the base file is new and recreates the cache for you.. the client needs to do nothing at all..

So in short, yes…  it has done this  from near the beginning.  Hope this helps.. Cheers -Jeremy

[NikNak]

Great stuff!!  - I was confused by the instructions on the wikii where it said:

Q: I need to delete that photo, but it has the same name.
A: Go to the filemanager and look for SuperSizerTmp folder. You can delete that one file out... or if you need to just delete the folder. It will rebuild its self.

Thanks again

Nik

[JeremyBASS]

Ha, yes that was written before the auto update was added.. thanks for pointing that out.. I'll change it when I can.. Cheers -Jeremy

[monghidi]

Hi Jeremy

I have followed this post carefully and got SuperSizer working beautifully on my site! Thanks a TON for a great plug-in!

I wonder though (did I miss it somewhere along the way in this post?)....can I have SuperSizer resize images when they are uploaded?  I have logged-in frontend users submit blog posts (works great). On the output (viewing summary and detail) any image they attached is resized through your plug-in. BUT...the original "BIG" image is still there in the filesystem, of course. I fear these big images will grow beyond my server's capabilities. People are throwing stuff up from their cameras and the files can be huge, as you know.

So...I hope you see what I mean lol! A front end user logs in. Posts to the blog. Attaches an image or two. Those images are re-sized and the original big one discarded. Make sense?

Is that possible?

Again, THANK YOU tons for this great tag, at least it works fine on the output! 

[JeremyBASS]

Well I'm working on a resize original... but as for a resize on upload.. this is what you would want to do.. lower in the post it shows how to use supersizer in a udt.. so what you want to do is to make a udt and attach that to an event... Today, I'll be writing one to be attached to news so when one of my clients posts their articles (on the event) the resized image will be done right off...

The resize origin is on it's way.. I just need to finish my paid work first.. but I promise.. right now it's just deleting the origin so it's half way there... -J

[JeremyBASS]

All right... pre release...

new param!!!

overwrite=true

{supersizer path="uploads/feusers/Untitled-1.jpg" height="100" alt="SMOOTH" overwrite=true cacheBuster=true Quality=55 filter="SMOOTH" farg1=50 }

Now with this.. the passthru is inherent... so passthru  always true when overwrite=true ... all other params should work just fine..

Please test..  and test it well...  and don't use on a mission critical site.. this is just a test... I want feedback that it works as it does for me... and lord forbid I forgot something and you nuke images you can't replace

This will make it perfect for modules to access for there own use... for you to use in udts... there is nothing you can't join this with.. if it has images.. You can get full control on them...

Cheers and enjoy
jeremyBass

[JeremyBASS]

I plan I releasing this over this weekend.. if someone can test that would be great.. thank you... Cheers -Jeremy

[monghidi]

JeremyBASS thanks,

I've just been testing it locally and it seems to be working very well for me. I'm using it to "permanently" re-size images that front end users attach to blog posts. The original image is overwritten now and replaced by the "supersized" one, in exactly the right spot.

You must have also fixed something else along the way? I no longer get errors about a foreach at line 549 in function.supersizer.php ... (I had been simply suppressing the errors). ANyway it looks like a champion of a plug-in! Really so useful that it begins to solve one of the biggest issues out there once a site is configured and put into play, which is users (even back-end ones) having to deal with image sizing.

Just firing wildly in the air...but... I have a couple of sites where if we could only have *every* image uploaded *never* be larger than "x", that would clinch it. 

Thanks, JeremyBASS! I'll let you know how the rest of the testing goes but it looks like a winner so far. Kudos to you!

[JeremyBASS]

Super to hear.. I have made all the errors output in an array now so that you can turn them off with the showErrors=false .. in that I also tried to light things up and knock out any and all errors.. You’ll notice that 0.9.x is about 10kb lighter and has total of 5 more params to wield... and if you look here you’ll see  (down at the bottom below the like 70 supersized images) that there is one that alerts you that you have uploaded a bad image… I had a client upload a .jpg that was really a .psd better believe that was some fun to figure out..

Hopefully this is getting good and strong enough for the core.. That is the aim.. One stable light weight image handling solution

[clj83]

Hey,

So this looks perfect and I am trying to test it but I have not used supersizer before and I guess I am not doing it right. I am trying to use it with a news image custom field. This is the original non supersizer code,

{foreach from=$entry->fields item='field'}
{if $field->name == 'Image1'}
file_location}/{$field->value}" alt="{$entry->title|cms_escape:htmlall}" />
{/if}
{/foreach}

And this is my attempt with supersizer,

{foreach from=$entry->fields item='field'}
{if $field->name == 'Image1'}
{supersizer path="uploads/news/id39/griMONTA_ROSA.jpg" height="168" overwrite=true cacheBuster=true Quality=70}
{/if}
{/foreach}

I have just hardcoded the path for now because the overwrite is my main concern. The tag works and the image is resized and the quality adjusted however it does not overwrite the original. It creates a new photo in the tmp supersizer directory with a new unique file name like this,

"griMONTA_ROSA.-w0-h168-p0-F-S1.jpg"

How do I get it to first put the new file in the same directory as the original and secondly overwrite the original?

Any help greatly appreciated.

Thanks

Chris

[JeremyBASS]

Oh boy.. um.. I have to ask.. you use the one from the pre-release below right?  No error shown? The fact that it made the temp file is not right... it should have only overwritten it... hmmm.. Well let me know because everything looks right.  You should have seen the image output as something like



also as a side note... I think I'm going to make alt="" be a part of the default output... This change well only effect people that are not putting  alt="" in there...  alt="" is needed to have a w3c valid doc. 

Let me know for sure that you used the right version from the post below..  monghidi shows it to work.. So I'm hoping this is if not.. add the debugIT=true and post the output plz...

Cheers
jeremyBass