plugin: Image Sizer

Hmm, am I being a bit simple here? 😊

I am trying to get this plugin up and running in EE2.0.1 without much luck…

I have followed the installation instructions, manually created the cache directory and set it to 777.

On looking in the Add-Ons->Plugins menu I can see ImageSizer 2.6 (and I can access the tag info via the title link)

I have placed in my template the following:

{exp:channel:entries channel="rentals" dynamic="off" orderby="date" limit="3"}
   {rental_image_01}
   {exp:imgsizer:size src="{rental_image_01}" width="220"}
{/exp:channel:entries}

I added the first tag to ensure that the image uri is correct (it’s a file upload field restricted to images only), and it displays the path on the page fine. The image itself however doesn’t even try to appear, and there is nothing on the page source to indicate that the plugin has done anything.

Have I done something wrong, or forgotten to do something important?

Cheers,

Gordon

Sometimes EE tries to format your field or there’s something else wrong. When this happens to me I usually try to put it in a regular img tag and see what happens. For example:

{rental_image_01}

Yesterday I had a case where I did that and found it was putting in paragraph tags because I had the field formatting set as ‘XHMTL’ instead of ‘None’.

Thanks, I had already checked this but forgot to add to my op. As the custom field that is driving this variable is of type ‘file’ it isn’t adding any additional markup. But I will keep that in mind for future quirks, cheers!

Any other ideas on the plugin not functioning correctly?

Gordon

Is it working in a standard img tag?

Is it working in a standard img tag?

Sorry I didn’t really answer that well did I, yes it’s working fine in a normal <img> tag.

Okay, convinced it’s a plugin issue, I just tried adding this to the page…

{exp:imgsizer:size src="/images/uploads/rentals/Fastnet_001.jpg" width="220"}

…and it’s not displaying a known good image.

This might actually be a base_path issue but it will be hard to trace as I am setting the site up on a cPanel ~username account until it’s ready to point the proper domain name to.

Hmmm, getting a fatal on just one entry? Thought maybe it was the image (file size or it being corrupt), but can’t figure it out. I try adding a different image that works on another entry, but still getting the error? Thoughts?

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 36000 bytes) in /var/www/vhosts/domain.com/httpdocs/system/plugins/pi.imgsizer.php  on line 554

Forgot to mention also, that I deleted the entry, and then created a new one

I’ve had this before a number of times…One time it was because I left out a necessary parameter. If that’s not it, try one of these parameters:

base_path= (optional) by default the base_path is set by ExpressionEngine to your webroot you may override this by altering this value to something like “/web/htdocs/lumis.com/” base_cache= (optional) the base cache folder is where all your cache images are stored within sub directories of your base cache folder by default it is base_path+”/images/sized/” you can change this to anything you wish as long as it points to a folder structure in your sites document root example: base_cache=”/web/htdocs/lumis.com/sized_images/”

I’ve come across something I can’t seem to figure out for the life of me. I’m using FF Matrix with nGen File Field and Imgsizer. The issue is with the Imgsizer setup.

The website indicates;

1: put plug-in in plug-ins location :blush:
2: create a cache folder in your images folder called "sized" /images/sized/
3: make sure you "sized" folder is writable (chmod 777)

Which I created at the path /uploads/albums/sized/. (777) I also created the upload directory to /uploads/albums/ in the Upload prefs.

But when I upload a file, it creates /uploads/gallery/filename.jpg INSIDE the previously mentioned folder, AND now, due to weird permission stuff, is not allowing me to delete the file that was resized deep within these folders.

I’ve burned through a few different folders thinking I missed something simple, but I can’t figure it out, and now I have 3 folders that I can’t delete even from my MediaTemple CP.

Driving me nuts.. any ideas?

Updating from Image Sizer 2.1.2 to 2.5.6 fails and causes EE Plugin Manager to go blank I’ve just updated from 1.6.7 to 1.6.8 and, now, going through extensions, modules, plugins, etc. to be sure I have most recent versions. Previous version installed for Image Sizer was 2.1.2. No matter how I do it - via the CP or manually - 2.5.6 causes the cp plugin manager screen to go blank. Copy back 2.1.2 - all is well. 2.5.6 - and screen goes blank again.

I’m getting exactly the same problem. Brand new install of EE 1.6.8 and 2.5.6 (not the EE 2.0 version) just kills the plugin page. Anyone got any tips? Or 2.5.5? Thanks!

I’m still getting a blank plugin page when I install 2.5.6. The other plugins are the standard EE installation defaults. If I remove Imgsizer the plugin page returns as normal, so it is the problem somehow. The target folders are set to 777 - I don’t know what else I can do. I’ve used it in other installs previously and it was fine, but this has me flummoxed! Any advice? Or can anyone kindly email a version of 2.5.5 for EE1.6.8 to david [at] hyphen [dot] net - thanks!

I’m having the same problem… 1.6.7 + 2.5.6 blanks my Plugin page.

I don’t get it.

Without base_path:

{exp:imgsizer:size src="{image_1}" width="120"}
{sized}
{/exp:imgsizer:size}

(0.163035) Tag: {exp:imgsizer:size src="http://work.something.com/test.de/uploads/product-images/my-image-1.jpg" width="120"} (0.170724) imgsizer.user.src: (0.170911) imgsizer.img[src]: /test.de/uploads/product-images/my-image-1.jpg (0.170935) imgsizer.img[base_path]: /var/www/work.somethingCOM/htdocs/ (0.171014) imgsizer.img_full_path: /var/www/work.somethingCOM/htdocs/test.de/uploads/product-images/my-image-1.jpg (0.171254) imgsizer.img[base_rel_path]: /test.de/uploads/product-images/ (0.171376) imgsizer.full_pathinfo dirname: /var/www/work.somethingCOM/htdocs/test.de/uploads/product-images (0.171402) imgsizer.full_pathinfo basename: my-image-1.jpg (0.171426) imgsizer.full_pathinfo extension: jpg (0.171449) imgsizer.full_pathinfo filename: my-image-1 (0.172256) imgsizer.Error: could not create cache directory! Please manually create the cache directory /var/www/work.somethingCOM/htdocs/images/sized/test.de/uploads/product-images/ with 777 permissions

With base_path:

{exp:imgsizer:size base_path="/var/www/work.somethingCOM/htdocs/test.de/" src="{image_1}" width="120"}
{sized}
{/exp:imgsizer:size}

(0.082289) Tag: {exp:imgsizer:size base_path="/var/www/work.somethingCOM/htdocs/test.de/" src="http://work.something.com/test.de/uploads/product-images/my-image-1.jpg" width="120"} (0.086412) imgsizer.user.src: (0.086524) imgsizer.img[src]: /test.de/uploads/product-images/my-image-1.jpg (0.086537) imgsizer.img[base_path]: /var/www/work.somethingCOM/htdocs/test.de/ (0.086582) imgsizer.img_full_path: /var/www/work.somethingCOM/htdocs/test.de/test.de/uploads/product-images/my-image-1.jpg (0.086606) imgsizer.Error: /var/www/work.somethingCOM/htdocs/test.de/test.de/uploads/product-images/my-image-1.jpg image is not readable or does not exist

You can see, with base_path i get “test.de/test.de” in the url.

1. http://work.something.com is the subdomain.
2. /var/www/work.somethingCOM/htdocs/ is the folder on the server where the domain points to.
3. test.de is the folder where EE2 is in.

Ok i don’t know why but its funny. I have to set the base_path and the base_cache.

If i set:

base_path="/var/www/work.somethingCOM/htdocs/test.de/"

i get:

/var/www/work.somethingCOM/htdocs/test.de/test.de/

So i tryed:

base_path="/var/www/work.somethingCOM/htdocs/</code></pre>
But then the cache path is
<pre><code>/var/www/work.somethingCOM/htdocs/images/sized/</code></pre>
So i also need to set the cache and it works:
<pre><code>base_path="/var/www/work.somethingCOM/htdocs/" base_cache="/var/www/work.somethingCOM/htdocs/test.de/images/sized/

I have no explanation for this behave????