CMS Made Simple Forums

uniqu3 wrote: {supersizer path="uploads/news/id$id/$image" unique='true'}

i am not sure if this script is related to your issue but afaik you should avoid using vars in "".
heres my example which i use in cgcalendar where Flyer is my image upload field:

Update:
ok i captured the paths as in your example but with no success

{capture assign='pathfrom'}{root_url}/uploads/news/id{$id}/{$image}{/capture}
{capture assign='pathto'}{root_url}/uploads/slider{/capture}
{supersizer from=$pathfrom to=$pathto unique="true" strip_tags="true"}

And the error:

Warning: imagejpeg() [function.imagejpeg]: Unable to open '/www/htdocs/w0085095/demo/http://demo.i-arts.eu/uploads/slider' for writing: No such file or directory in /www/htdocs/w0085095/demo/plugins/function.supersizer.php on line 259

The only thing that has changed is that i have http://demo.i-arts.eu in the path but yes this is not correct path at all.

Update: changed path to to="uploads/images", now i get another error.

Warning: unlink(/www/htdocs/w0085095/demo/uploads/images) [function.unlink]: Is a directory in /www/htdocs/w0085095/demo/plugins/function.supersizer.php on line 576

Warning: imagejpeg() [function.imagejpeg]: Unable to open '/www/htdocs/w0085095/demo/uploads/images' for writing: Is a directory in /www/htdocs/w0085095/demo/plugins/function.supersizer.php on line 259

Hello, sorry, been gone for a bit.. so..

{capture assign='pathto'}{root_url}/uploads/slider{/capture}
  that needs to have the full name IIRC .. id{$id}/{$image} needs to be added..
ie: {capture assign='pathto'}{root_url}/uploads/slider/id{$id}/{$image}{/capture}

I will need to check thou.. I need to get some things done but I hope I'll be able to look in to this later today.  Cheers -Jeremy

Sorry everyone - post removed

Was having very confusing issues but they have sorted themselves out - (am still confused as to how)

Nik

I was using fillHW=true on the older supersizer.  I upgraded to the newest version and it no longer works.

Has this been replaced by fill_attr ?

Thanks,
Ken

Hi everyone, I've read the entire post looking for a solution to my problem and nothing.

I'm using:
* Gallery 1.4.1
* SuperSizer 0.9.4
* CMSMS 1.8.2

I'm using SuperSizer to reduce the file size of uploaded images via FTP. But I'm facing several issues:

First tried using this as suggested:

file width="800" URL="true"}" title="{$image->titlename}" rel="gallery">thumb}" alt="{$image->titlename}" />

and I get this as the resulting HTML code

" title="100_2659.JPG" rel="gallery">

First I don't know why I get that <img src=" and second the extremely long name 100_2659.-w800-h0-p0-q85-F-----S1-c.jpg?1287093486

If i just eliminate the SuperSizer it all returns to normal and works.
Could someone please help me on this. I've tried several ways to get around this with no luck at all.

Thanks in advance.

Mr. Bacan

The latest version of supersizer has all lower case attributes.

Change URL="true" to lowercase.

I'm home sick, I'll get back to these, and I saw the BR. I'll get to this in a few day when I'm well .. cheers -Jeremy

@kendo451

Change URL="true" to lowercase

Thank you so much, that solved my main problem. Now the gallery is working as it should.
But I'm still struggling with the long name issue. The auto-generated images on uploads/SuperSizerTmp/ folder are extremely long.

Original name:
100_2659.jpg

SuperSizer name:
100_2659.-w800-h0-p0-q85-F-----S1-c.jpg

Why could that be?

Thanks again for your help.

Mr. Bacan

That's on purpose. Ask Jeremy why.

It seems like the filename contains some certain params.
So it won't be overridden if you show the same image twice but with different params.

Good morning..

@mr.bacan  this

Original name:
100_2659.jpg

SuperSizer name:
100_2659.-w800-h0-p0-q85-F-----S1-c.jpg


This in short is to let you have as many versions of the same image in all different ways.. and also .. so that at a glance you can grab all the images that have w800 (800 px width).  But if you don't like that there is a param to remove that.


@kendo451

Has this been replaced by fill_attr ?

Yes you are correct  and I'll have to go back and look at you BR..


Cheers -Jeremy

Jeremy, thanks for alerting me to this great plugin. I have read through this thread and it is clear that SuperSizer can be very powerful in the hands of those who know what they're doing

What I would love to be able to do with SuperSizer is manipulate images that are inserted into a {content} block by users via TinyMCE. I understand that this would involve using SuperSizer in a UDT that does some sort of find/replace operations, and attaching the UDT to an event. Sadly, I'm a designer rather than a programmer and I don't (yet) have the skills to do this. If someone with programming chops can help I'd really appreciate it.

Two uses of SuperSizer that I think would be very handy...

1. For when you trust users to enter sensible width/height attributes via TinyMCE: find the height/width parameters set in TinyMCE and replace the tag with a SuperSizer tag that resizes the image to that width/height.

2. For when you want to set specific sizes and filters for images in a particular {content} block: if an tag has a class="MyGrayscaleImage" output SuperSizer tag with "x" parameters, if an tag has a class="MySquareImage" output SuperSizer tag with "y" parameters, else output SuperSizer tag with "z" parameters.

This sort of funtionality would solve so many of the headaches I have with clients taking a carefully designed template and messing/uglifying it up with huge, randomly-shaped images

Newsletter Made Simple allows you to use Smarty tags, plugins and module calls in the Email templates.

This is extremely useful, as for example, you can have a product summary template that randomly puts three products from a certain category in the header or footer of your email Newsletter.

The problem is, I can't get supersizer to work in NMS.

I think the reason is that NMS is processing the email template in a php file within the NMS module directory.  Supersizer expects to be in the CMS root.  So it can't find the paths.

Jeremy, do you know of a way around this?

@kendo451  I'll do a test.. see if I can make it work in NMS.. cause to be honest.. I swear I tested that and it worked..

@cerulean  I'm not sure I 100% fallow your question..

I'll get back. tk -J