Announcement: New plug-in SuperSizer

[monghidi]

Good question as to which version you are using...I initially made the same mistake, grabbing the one from the forge and of course that didn't work. You need the one attached to JeremyBASS's post above!

[clj83]

Hey,

Sorry, I have found the problem. Yes I did download the version from beneath the JeremyBASS forum post above but I did not notice when I uploaded it through Cpanel that the file ended with a .txt file extension therefore even though I selected overwrite original it didnt because it was a different file extension so my images where still using the old supersizer.

Sorry! I have just had a quick check and it seems to work now. I will do some more testing now and let you know if I come across any bugs.

Thanks again and sorry for my mistake.

Chris

[JeremyBASS]

super... I'll be publishing later today.. -J

[NikNak]

Hi Jeremy

I'm trying the latest supersizer from the forge with cmsms 1.6.6 (and also tried the version a little earlier in this post)

When I upload an image with a space in its file name, supersizer changes the temp file to have %20 instead of the spaces. However, if I then try and view these tmp files, they cannot be found by the browser. If I replace the %20 with spaces or any other character then they can be found.

ie /uploads/SuperSizerTmp/Frangipani%20Flowers.-w720-h300-p0-F-S1.jpg is in the file manager but if you click on it to view it, the %20 is replaced by a space in the URL bar and then the browser cannot find the file.

This is when you use the URL only functionality - not tried any other methods.

Sadly, it's a bit of a deal breaker  -  is there a fix Jeremy?

Thanks

Nik

[JeremyBASS]

Sorry for the delay there was gone all of last week for fam things.. add the passThru=true.. (located in the posts lower here)... this will tell a few things right off... if there was a problem you would have seen an error... also this is addressed below.. Some modules pass the spaces funny so it's an issue with what comes in IIRC.. Hope this helps clear it up... -J

[NikNak]

Hi Jeremy

I have tried the same operation from outside the gallery module and it works fine, so you're right - it's how the Gallery module is dealing with the space.  Now I just need to work out how to sort that little (or big) problem.

Thanks for the steer.

Nik

[Jos]

I didn't follow this tread, but is there something I have to change in Gallery??

[NikNak]

Hey Jos

It's a problem I'm having using supersizer with gallery.

My Gallery template uses this:
{supersizer path=$image->file height="300" width="720" crop=true URL=true Protect=false  passThru=true Assign=resizeImage}

But if the filename has a space in it, then there are problems.
The Supersizer tmp file becomes:
/uploads/SuperSizerTmp/Frangipani%20Flowers.-w720-h300-p0-F-S1.jpg
If you then try to view that file, the %20s are replaced with spaces and the file can no longer be found.

If I try the supersizer on the same image just in the body content, it all works fine.

Thanks for replying so quickly.

Kind regards

nik

[Jos]

Should I put a rawurlencode on the filename then?

[NikNak]

Hi Jos

I'm not a programmer so I can't say if this is the right course.

If you tell me the line of code to change in the gallery module, I'll try it out and let you know if it works. Would that be ok?

Thanks

Nik

[JeremyBASS]

yeah... I'd start with rawurldecode...  -J

[porridj]

Code: Select all

{if isset($entry->image1)}
{assign var=Photo value=$entry->image1}
{assign var=Item value=$entry->id}

{supersizer path="/uploads/news/id$Item/$Photo" height="450" Subdir="$Item"}

{/if}

Using this...breaks my page. It strips everything out of the and i dont know why.  If the path is not correct then the page displays correctly but gives me the "There is a path issue with the orginal image! Does this look right?" error.



using the last supersizer file

[kendo451]

porridge, please include the entire page template you are using too, so we can look at that.

[JeremyBASS]

it got solved over in the IRC, he had his php mem limit set to low, and he had protect=true... fixed those to and it works

Cheers -Jeremy

[porridj]

Aye, there was an image I put in as a test which I had forgotten about. It was 1.9 MB and it was breaking at that image, but because it was further down the page I just wasnt checking it. I thought the problem was the 2nd image which had protect=true on (well it wasnt set, so I assume the default is true) and that wasnt displaying...but because the image size i was setting etc it just didnt display...

It was just poor observation on my part really for not spotting the big image file!

Maybe it is worth adding an error message in for errors like that so that idiots like myself can easily spot where we are going wrong. Just an idea

Cheers for the help