plugin: Image Sizer

@okayyellow try this

{exp:imgsizer:size width="185" height="110" src="{image}" server_domain="http://www.mysite.com/"}

undocumented but it basically appends the domain to the image path on output.

The server_domain=”http://www.mysite.com/” trick works perfectly for me. (imgsizer - 2.5.6 & EE-1.6.8… not using MSM) Just what I needed. Thanks @lumis!!!!!

Hi:

After several years of having an EE license that has languished, I updated my site (1.6.8, not .9), and am plowing through Boyink’s terrific tutorials. In his chap. 13 (shoulda known!), he has us using Imgsizer, which I cannot get to work due to some path issue I cannot seem to wrap my head around. I mean, I see the path issue; I just don’t know the best practices method to resolve this.

This:

<a href="http://{url_title_path=products/detail}">{product_thumbnail}</a>

worked fine. However, after installing imgsizer, this:

<a href="http://{url_title_path=">{exp:imgsizer:size src="{product_thumbnail}" height="54" alt="{title}"}</a>

didn’t; I get the dreaded nothingness. The page renders as if the images simply don’t exist. It’s not an imagesizer install issue, per se; the debug pops this out:

-> Class Called: Imgsizer
-> Method Called: size
      imgsizer.user.src: <img src="http://www.domain.com/images/uploads/thumbtack_car_thumb.jpg" alt=""  />
      imgsizer.img[src]: /images/uploads/thumbtack_car_thumb.jpg
      imgsizer.img[base_path]: /home/content/l/u/c/USERNAME/html/
      imgsizer.img_full_path: /home/content/l/u/c/USERNAME/html/images/uploads/thumbtack_car_thumb.jpg
      imgsizer.Error: /home/content/l/u/c/USERNAME/html/images/uploads/thumbtack_car_thumb.jpg image is not readable or does not exist
      Returning No Results Content
-> Data Returned

Which indicates that Imagesizer is installed and attempting to do its thing. All of what’s shown is perfectly correct; the user.src path is correct, and returns the original thumbnail image (which I’m attempting to learn to shrink with Imagesizer in this Tute). The img[src] path is correct. However, the [basepath] and then the fullpath is NOT correct - it’s missing the subdomain name (sorry, should have noted, this is not installed in the root), so Imagesizer can’t find the original image, ergo can’t return the resized image.

I see the problem; the correct base_path should be:

/home/content/l/u/c/USERNAME/html/SUBDOMAIN/

But I can’t quite figure out how to correct this in the particular scenario in which I’m using it in the tutorial…in which I’m using “product_thumbnail” fieldname to indicate the source (which works, when used by itself).

I tried the “server_domain” trick shown above, but no joy.

I’m open to ANY suggestions? Not superstitious, but I hate being stuck on Chapter 13 without any daylight in sight! 😉

TIA,

Hitch

Hi Hitch, can you not use the base_path=”” parameter? That’s what I do when I have server path issues. I also tend to store my base_path in a Fresh Variable so that when I move the site I only need to update it in one place.

{exp:imgsizer:size src="{product_thumbnail}" height="54" alt="{title}" base_path="[server path here]"}

See Lumis’ docs for more info: http://www.lumis.com/page/imgsizer/

Hi Hitch, can you not use the base_path=”” parameter? That’s what I do when I have server path issues. I also tend to store my base_path in a Fresh Variable so that when I move the site I only need to update it in one place.

{exp:imgsizer:size src="{product_thumbnail}" height="54" alt="{title}" base_path="[server path here]"}

See Lumis’ docs for more info: http://www.lumis.com/page/imgsizer/

UNbelievable, I even read Lumis’ page and the notes/docs, and completely missed that. However, very cheerfully, I am able to tell you that that worked a treat, and thank you. I knew it was something I should know; I stared at it and saw the problem, but my brain just would not cough up the resolution. You know how it is: so much Boyink, so little Brain. 😉

Seriously: thank you!!

Hitch

Sometimes brains can be quite uncooperative, happens to me all the time. Glad you have it working anyhow

Hello,

Anyone having issues with Imgsizer + EE1.6.9 ?

The paths are correct however the {exp:imgsizer:size…} won’t spit out the correct <img> tag on “view source”.

Cheers!

Hello, Anyone having issues with Imgsizer + EE1.6.9 ? The paths are correct however the {exp:imgsizer:size…} won’t spit out the correct <img> tag on “view source”. Cheers!

Hi, @Valon Sopi:

Can you show us what the input is, and what is output as the correct img tag? IOW, what is is supposed to be, and what is being generated? Was it working for you in 1.6.8?

Hitch

Hi Hitch,

The input is the standard one {exp:imgsizer:size src="{photo_upload}” width=”200” height=”100”} — The output is blank (i.e. no <img> tag)

Any thoughts? I don’t see many people having this issue.

BTW — {photo_upload} is file-upload custom field / Mark Hout’s File Extension.

Cheers.

Hi Hitch, The input is the standard one {exp:imgsizer:size src="{photo_upload}” width=”200” height=”100”} — The output is blank (i.e. no <img> tag) Any thoughts? I don’t see many people having this issue. BTW — {photo_upload} is file-upload custom field / Mark Hout’s File Extension. Cheers.

Hi, Valon:

Well, I know I had bupkus (nothing) for output when I had my problems. Did you set up your cache file? When you set debug on, what does it say? That’s how I figured out why I was getting a “Returning No Results Content” problem, which you can see an example of in my post in the debug code.

Hitch

Ah, well of course it works now.

Cheers for the nice simple tip man.

This is what happened: I’m hosting the site on a subfolder off of httpdocs // so, imgsizer was looking for the cache folder on httpdocs (which, surely enough couldn’t find) — Never had this problem before, because I was working on the EE site installed directly on httpdocs (no subfolder).

To fix it all — I manually created the cache folder with 777 permissions.

Here goes a beer your way!

Cheers 😊

Ah, well of course it works now. Cheers for the nice simple tip man. This is what happened: I’m hosting the site on a subfolder off of httpdocs // so, imgsizer was looking for the cache folder on httpdocs (which, surely enough couldn’t find) — Never had this problem before, because I was working on the EE site installed directly on httpdocs (no subfolder). To fix it all — I manually created the cache folder with 777 permissions. Here goes a beer your way! Cheers 😊

Kewl! Glad I could help. Thanks for the beer!

Hitch

Hello All,

Fresh Install of EE 1.6.9 and imageSizer v2.5.6…makes my plugin page via control panel blank…first plugin installed on fresh install of EE.

Remove imagesizer and all is fine again…

I have read that 2.5.5 works…but I have no link.

Any Ideas?

thanks

matt

I’m using imgsizer to build thumbnails off of images hosted on Amazon S3. I don’t need the thumbnails stored on S3, just the originals. So i’m using the remote=”on” parameter, but whenever i submit the S3 image in the imgsizer tag, my entire page comes back blank. I’ve turned on debugging, but don’t even get that on the test page. literally nothing. Testing it with images from flickr works as intended. Just dropping the S3 image in a simple <img> tag on the page works fine as well, the issue is processing it in imgsizer, from what i can tell.

any tips? I’ve followed AJP’s instructions here: http://ellislab.com/forums/viewreply/731058/, and still not getting anything back.

thanks!

Maybe being able to specify by corner, and when not specified, it will default to middle?

{exp:imgsizer:size image="{image}" width="322" height="197" alt="{caption}" corner="top-left"}

or

{exp:imgsizer:size image="{image}" width="322" height="197" alt="{caption}" corner="bottom-right"}

Hmm.. Maybe i will look into it later, i personally don’t see the use at this moment, but if i have the time.

I think this is a great idea. As others have said. I like the “top-left”, “bottom-right” approach. If you ever have time it would make a welcome addition, as others have noted previously.

Thanks for the excellent plugin!

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 9000 bytes) in /nfs/c01/h04/mnt/1234/domains/mydomain.com/system/expressionengine/third_party/imgsizer/pi.imgsizer.php on line 555

What does this mean / how do I fix it?

Using:

{exp:channel:entries channel="releases" sort="desc" limit="1"}

{exp:imgsizer:size src="{release-front-cover}”}

{sized}

{/exp:imgsizer:size}

{/exp:channel:entries}

In EE2.02.