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;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?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)
Update: We’ve decided to pass on using Image Sizer and are looking into Channel Images at this point. http://www.devdemon.com/store/detail/channel_images
I just recently upgraded to EE 1.6.8 (I know I’m behind) and am running into problems with this plugin. The plugin installed correctly but will not resize any of my images, in fact it doesn’t even show them. Does anyone have any idea as to why this may be happening?
I too am having a memory error issue. I am using version 2.6 on EE PB 2 build 20100215
The error is as follows:
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 9000 bytes) in /home/jrich/jeremiahrich_system/expressionengine/third_party/imgsizer/pi.imgsizer.php on line 555
Edit I did speak too soon, after taking a good look over my code, I realized I was missing a closing ” after the width tag. Kind of weird that it would report itself as a memory error, but whatever. Thanks for the amazing plugin, it is going to help with my design a ton!
I think this is an excellent plugin and it took some time to get it to work but it is simple and just plain great. I have a few questions though about how to use it.
Is it possible to give a set width on 200px and give a max hight of 300px? So if the image is width 200 and height 250 then there is no cropping, but if it exceeds 300px in height that there will be an automatic crop?
Is it possible to adjust from where the cropping should start? If I want the cropping to be from left side, right side or from the center. How do I adjust that?
Thanks for any help and love the plugin. Janus
1. Is it possible to give a set width on 200px and give a max hight of 300px? So if the image is width 200 and height 250 then there is no cropping, but if it exceeds 300px in height that there will be an automatic crop? 2. Is it possible to adjust from where the cropping should start? If I want the cropping to be from left side, right side or from the center. How do I adjust that? Janus
Neither request is built in, but…
Yep, this has been done as a hack, but you’ll have to go back through this thread to find where. It was a minor amend to the php code I believe.
There’s been mention of this previously in the thread, there’s a slim chance someone identified the code to crop from the center and gave examples, although I can’t be sure without going through the thread.
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!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 stuck by this and really need to get Image Sizer working. I’m wondering if this is a PHP error - my server is running PHP 4.4.9. Is the 2.5.6 version of Image Sizer compatible with this? If anyone has a copy of an earlier version of Image Sizer that is compatible with PHP 4.4.9 I would be really grateful if you could email it to david [at] hyphen [dot] net - thanks so much!
+++ SOLVED +++ Peter, a very helpful EE user, sent me Image Sizer version 2.5.5, saying that “v2.5.6 has a pathing issue which I can replicate if I have EE installed in a sub-folder”. I installed 2.5.5, gave the plugin permissions of 777 and it works perfectly! Thanks again Peter!
I am not getting the greatest quality out of some of my gif images. They are coming out pretty grainy/dithered. Is there anything I can do to increase the quality for gifs? I know there is a quality setting for jpgs. Or is this more an issue with the GD image framework and how it handles gifs?
I’m having some issues with 2.5.6 and I’m not sure how to address them. Specifically, I’m getting this below in template debugging and I’m really even sure where to start.
(0.170234) Tag: {exp:imgsizer:size src="/assets/images/uploads/fpo-home-banner.jpg" width="880" alt="My Title"}
(0.170360) No Closing Tag
(0.170412) Processing Tags
(0.170444) Plugin Tag: Imgsizer/size
(0.170461) Including Files for Tag and Modules
(0.173398) Beginning Final Tag Data Processing
(0.173418) Calling Class/Method: Imgsizer/size
(0.173501) -> Class Called: Imgsizer
(0.173533) -> Method Called: size
(0.173585) imgsizer.user.src: /assets/images/uploads/fpo-home-banner.jpg
(0.218691) imgsizer.img[src]: /assetsimagesuploadsfpo-home-banner.jpg
(0.218714) imgsizer.img[base_path]: /home/dbtadmin/www/
(0.218745) imgsizer.img_full_path: /home/dbtadmin/www/assetsimagesuploadsfpo-home-banner.jpg
(0.218779) imgsizer.Error: /home/dbtadmin/www/assetsimagesuploadsfpo-home-banner.jpg image is not readable or does not exist
Any help I could get would be appreciated.
I’m getting a strange issue I can’t figure out for the life of me. I moved my website from one domain to another domain, and I set up everything exactly the same. However, the image sizer is not working at all. Nothing shows up for the simple tag:
{exp:imgsizer:size src="{member-logo}" width="140" alt="{title}"}
I even put in the direct link to the image, and still, nothing shows. All my paths are correctly set, “sized” folder is created with the right permissions, imgsizr plugin is in the plugin folder… yet, nothing. Any idea what’s going on?
eclectiv, Not sure if this will be very helpful, but whenever that happens to me I always test it by putting in a regular HTML img tag to the original image to make sure the image is showing up properly. Most the time that flushes out the problem for me.
I’ve also made stupid mistakes where I’ve had it within another plugin’s tags that kept it from working. Hope that helps some.
OK, cool. I updated it from an old version for a website today…so it was originally using ‘cache’ folders inside the image locations directory. Moving to the new version I had hickups with errors when the ‘sized’ folder was initially set to 755. I changed it to 777, and the errors went. Maybe it’s just the initial setup that it requires 777, then you can change 755 once it’s created the /sized/images/… directory within it.
I’ve now set back to 755 and it seems to be fine.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.