plugin: Image Sizer

I resolved this by using the Extract URL Plus plugin from Dan Walton: Here is my code:

{exp:imgsizer:size parse="inward" src='{exp:zm_extract_url_plus show="%file_path"}{topleft_pic}{/exp:zm_extract_url_plus}' width="280"}
{sized}
{/exp:imgsizer:size}

Hey,

We are using the plugin and it is really faster than PHPThumbs, and caching is also great. I have still one question. In one field called description we have multiple images. Is it possible to get all those images rendered by this plugin? Now the plugin only does the first image in combination with the extract plus plugin.

regards,

Apologies if this was asked before… Can you change the location of the cache directory - so it’s in a separate directory then all the “uploads”?

Reason being that when users use the native File Upload feature and are browsing existing images in the upload directories - all the cached images show up in the list (and I don’t want that).

Am I missing something here?

Open the plugin file and around the line 49 you can find something like this: $cachPath = “cache/”;

Thanks Gabriel. That helps.

Apologies if this was asked before… Can you change the location of the cache directory - so it’s in a separate directory then all the “uploads”? Reason being that when users use the native File Upload feature and are browsing existing images in the upload directories - all the cached images show up in the list (and I don’t want that). Am I missing something here?

Being able to define this would be awesome but would require an extension no?

Apologies if this was asked before… Can you change the location of the cache directory - so it’s in a separate directory then all the “uploads”? Reason being that when users use the native File Upload feature and are browsing existing images in the upload directories - all the cached images show up in the list (and I don’t want that). Am I missing something here?

Being able to define this would be awesome but would require an extension no?

Having imgsizer create writable cache folders all over was causing lots of permissions issue with deployment for us, so we modified the plugin so it creates all the cache images in one spot (recreating the dir structure within).

So if you use imgsizer on /images/these_images/this_pic.jpg, it gets cached at /cache/images/these_images/this_pic-200x200.jpg

Is that what you’re looking for?

Having imgsizer create writable cache folders all over was causing lots of permissions issue with deployment for us, so we modified the plugin so it creates all the cache images in one spot (recreating the dir structure within). So if you use imgsizer on /images/these_images/this_pic.jpg, it gets cached at /cache/images/these_images/this_pic-200x200.jpg Is that what you’re looking for?

Sounds like that would be perfect. I just don’t want the cache folder inside the corresponding uploads folder - that way they don’t show up in the images list when a user is browsing the images via EE’s native File Upload function.

Thanks for your reply, by the way.

Mark Terpstra I did the cache folders inside each images folder instead of having a singular cache folder to prevent file name collisions.

one idea i have been considering is having a singular cache folder with sub folders that matched the name of the folder that the original image was in.

Mark Terpstra I did the cache folders inside each images folder instead of having a singular cache folder to prevent file name collisions. one idea i have been considering is having a singular cache folder with sub folders that matched the name of the folder that the original image was in.

That’s exactly what solution we came up with. We modified the imgsizer plugin to do this, and it has really worked great for us. It solved alot of problems.

Let me know if you’d like me to email/PM you our modified code, I’d be happy to!

Without sucess in another place in the forum, i will try here, the “official support”…

Anyone here integrate the image output imgsizer plugin with some javascript slideshow? If i use a “static” image, all works ok, the new resized image its created ok. But when insert this same code in a small piece of javascript, the plugin dont renderize the images!

i’m using the simple tag in code below:

{exp:weblog:entries weblog="noticias" disable="member_data|trackbacks|pagination" status="Destaque" orderby="date" sort="desc" limit="5"}
<div class="contentdiv">
{exp:imgsizer:size src="{noticia_imagem_principal}" width="400" height="300" class="imagem_destaque"}
{sized}
{/exp:imgsizer:size}
<span class="noticias_titulo_capa"><a href="http://{title_permalink=site/ver_destaque}">{title}</a></span>
<span class="noticias_texto_destaque">{noticia_resumo}</span>
</div>
{/exp:weblogs:entries}

I tryied too with the simple tag, but without sucess too:

{exp:weblog:entries weblog="noticias" disable="member_data|trackbacks|pagination" status="Destaque" orderby="date" sort="desc" limit="5"}
<div class="contentdiv">
{exp:imgsizer:size src="{noticia_imagem_principal}" width="400" height="300" class="imagem_destaque"}
<span class="noticias_titulo_capa"><a href="http://{title_permalink=site/ver_destaque}">{title}</a></span>
<span class="noticias_texto_destaque">{noticia_resumo}</span>
</div>
{/exp:weblogs:entries}

The javascript in question is this: Featured Content 2.4

So far the mostest simple script with i see it in this category, one time with i just need to generate the content in the divs… Any help or code to share?

just used this for the first time - dead easy to use and configure - now going to try and combine with a lightbox.

I’ve found a bug with image sizer.

someone has been uploading images with a filename like “image1.jpgasd.jpg”, and this isn’t getting parsed by imagesizer.

it’s seemed to be counting the first .jpg order of characters as the extention. “image1.jpgasd.jpg” - doesnt work “image1j.pgasd.jpg” - works “image1jpgasd.jpg” - works

Hope that explains the problem…

timkelty, I’d be happy to make use your code on my projects. ;)

Mark Terpstra I did the cache folders inside each images folder instead of having a singular cache folder to prevent file name collisions. one idea i have been considering is having a singular cache folder with sub folders that matched the name of the folder that the original image was in.

That’s exactly what solution we came up with. We modified the imgsizer plugin to do this, and it has really worked great for us. It solved alot of problems. Let me know if you’d like me to email/PM you our modified code, I’d be happy to!