CMS Made Simple Forums

What you want is  errors=false    .. this will do what you’re asking.. it's default is true as once it's setup right the only time you'll see and error is if you upload a corrupted file ie: a .pds that has a file name as .jpg which most don't know that most OS will open it up and you see the image but browser will not.  Hope that helps.. Cheers -Jeremy

Jeremy, thank you! I had a message: "Fit doesn't work with percentage", but this was not produced by editor, but by me Solved now and will use errors = false as well.

i have a question about the filenaming of supersizer.
when i have a image called then the supersizer generates that is not the best for SEO. especially for google image search.
is it *somehow* possible to nearly maintain the imagepath? for example with a clone: surly the filename isnt unique anymore but thats not important because every image has a different filename. but it would be a great advantage to maintain the path and filename. people who are using this feature should be aware of that.
a good parameter for that might be keepfilename="true" ?!
the only problem is when you are using more then one instance of supersizer with the same source image. then it might be better to handle it that way: for images with paramter width=120 or for images with paramter width=800
what do you think?

Um... I'll see what I can do.. but for now you can always use the overwrite param. It's check is light weight and would mostly do what you’re asking in preserving the path. Also now that I think on it, you can put in the subdir param and build that path your self.. that would be better then overwrite IMHO .. Hope that helps some. Cheers -Jeremy

ok, how is overwriting works in detail? just to understand it:
when i upload a image 800x600 and want supersizer to scale it to 120x120 then it overwrites the sourceimage?
and when i want to use the same image at another place in 300x200, then i get a very bad quality. do i understand it right? what has then priority? i mean it then would scale back and forth? up and down? from 120x120 to 300x200 and back again? that would a problem i think

nicmare wrote:ok, how is overwriting works in detail? just to understand it:
when i upload a image 800x600 and want supersizer to scale it to 120x120 then it overwrites the sourceimage?
and when i want to use the same image at another place in 300x200, then i get a very bad quality. do i understand it right? what has then priority? i mean it then would scale back and forth? up and down? from 120x120 to 300x200 and back again? that would a problem i think

In short your right, overwriting is a do once forever type of function.. but this is why I also suggested using the subdir param. since no module I know of less gallery has SEO paths like that I'd think you'd have an easy time using the subdir, but in case you need to pull it from something, like CGBlogs or something you can use pathinfo();

you may be able to do something like subdir=$entry.image|pathinfo->dirname .. now I didn't test that and you may have to assign the $entry.image|pathinfo first then access it like foo->dirname ... something like that.. That should give you a starting point. I have been thinking about a better way, but I'm just not 100% there is a shorter more flexible fit.

Cheers -Jeremy

JeremyBASS wrote:I have looked at that before when adding the crop, but I have ruled out due to a few reasons.. one being the weight it'd take to do it (almost doubling the footprint),  and you can reproduce that same effect with css and js... have a lookies http://www.hellscanyonsportfishing.com/ ... I think the next addition well be joining images... but I'm not sure on that as well.  I want this to be as light as I can since it's suppose to help speed sites up, not just make our lives easier sorry I would have to pass on that one. Cheers -J

just wanted to ask if you could integrate this. because firefox does not support rounded corners on images. unbelievable, yes, i know…

I will put it in the module I'm making.. it's supersizer in module form. Very simple to use, profiles, and will handle many things like this, watermarking, rotation, filtering out adult photos and much much more.. so in short yes but not in supersizer. I'm hoping that I'll have this module out in a few weeks with the ScriptDeploy module. It'll be called MediaDeploy ... Oh and there will be a jquery crop tool in there. I know it don't help now but it'll be soon .. Cheers -Jeremy

wooohooo. are you challenging with CGs magicimage module?

Not really, and well I had mine first which we had talked about it but I just didn't push it out before his is all.. and he has a different tack on how something like this should work.. mine is well, meant for me and my cleints and how they think. Also to work with my module line I've got coming down the pipe inculding the fontin module and auto embeding for css and js and all templates while being fully exportable/importable in ScriptDeploy. Same base idea with two needs I'd guess.

yes, i tried out his module and well… i am back to supersizer . keep going this good work jeremy

JeremyBASS wrote:...filtering out adult photos...

How in the heck do you do that?

Oh cant wait for complete "Deploy" suite

@nicmare thanks I'm glad to hear people like my work always nice to hear.

@Wishbone that is a secret there.. but.. it's pretty good, lets you just do a % target where you get to flag images the look to have nudity in them. Later face blurring/tagging and hooks like that will come too if I the time for those sub modules. But I have the adult content filter now.

@uniqu3 you will love the Exports, make a whole template with js/flash and all, full module setups, and even admin themes all in one export. But more on this is to come.

JeremyBASS wrote:@Wishbone that is a secret there.. but.. it's pretty good, lets you just do a % target where you get to flag images the look to have nudity in them. Later face blurring/tagging and hooks like that will come too if I the time for those sub modules. But I have the adult content filter now.

You must have to put many, many hours into testing a feature like this.