MS Img Saver FieldType for FieldFrame

Sorry for all the posts just noticed the most important thing now. I was only uploading fairly small images so when looking at the uploaded file I thought the file-size was still the same. It appears this is incorrect. I just uploaded a much larger image yet all I got was the small thumbnail image which does open and then another file which was still a small sized file and nowhere near the original file size.

Also is this supposed to rename the images as I was uploading an image called Picture 1 which was a PNG file but it was getting renamed to picture_1.png. Is there any way (when this is all uploading correctly) to keep the names the same? I know that spaces aren’t great in image names but I had a capital letter in there and it changed that too.

Best wishes,

Mark

Thanks for all the feedback so far Mark 😊. The way I have this setup is you decide what dimensions the outcome of the picture is going to be. It doesn’t save the original picture that you uploaded. It resizes/crops to your specifications and then deletes the original file keeping the modified one. If the image is smaller than what you have specified in your settings, it doesn’t touch it, that way it won’t blow up and distort a small photo to your specified dimensions. Now if you only put it lets say 300 width then the height will be variable depending on the original size of the photo. It keeps the same aspect ratio as to not distort the file. If you put in both height and width it will crop the photo to again, keep aspect ratio.

Due to the security guidelines that EE has in place when building addons, I have to run the file name through a function to strip out bad characters and get rid of spaces.

The whole purpose for this add-on is for developers to give their clients the freedom of uploading images to change their content but not give them enough rope to hang themselves (i.e. upload a 5meg picture that is 3000 x 5000 pixels big and totally ruin their website. Believe me…I’ve had that happen before ><). So you put those dimension settings in place and that will never happen 😊. I don’t think you should have to worry about the name of the file as all you have to do to get the full URL to the image is use the custom field name in your template, the extension will do the rest 😊.

Hi Cody, Thanks for the update. Going to give it a try now. I seem to be spoilt for choice now what with your IMG Saver and now the nGen File Field, what’s a man to do? 😊 Best wishes, Mark

Ahh damn, didn’t know nGen was doing that. Guess it totally negates what I just did 😕. Ahh well, guess it was a good learning experience.

Hi,

When trying to upload a jpeg file I’m getting the following:

Fatal error: Call to undefined function imageantialias()

If it’s a gif file I get:

Warning: imagecolorsforindex() [function.imagecolorsforindex]: Color index 255 out of range in /home/www

png’s load just fine.

Installed versions alongside the bundled ff’s from Brandon FieldFrame 1.0.0 + MS Img Saver 1.0.1 + LG TinyMCE 2.0.1 + nGen File Field 0.9

-Ruud-

Hmm.. I don’t have files with the .jpeg file extension, all of mine are .jpg so I’m not able to test that out.

As for the gifs, I just uploaded 10 different gifs and all of them worked. Maybe your GD is not up-to-date on your server? Are you able to use the extension Image Resizer? I’ve taken my image manipulation from his code.

Yes I’m running the Image Sizer plugin as well… So that’s kinda weird if it’s sharing the same code.

I’ll have to notify my host on the GD though. in themean time I’ll try to create some different filetypes later and see if I can upload them. Might give a hint on where it fails in the process.

• R -

Edit: Unanimated gif’s seem to work! I tried an animated one previously. jpg/jpeg still throws me the imageantialias() error.

Hi,

Some more info on the GD side.

GD library: GD Version: 2.0 or higher FreeType Support: enabled FreeType Linkage: with freetype T1Lib Support: enabled GIF Read Support: enabled GIF Create Support: enabled JPG Support: enabled PNG Support: enabled WBMP Support: enabled XPM Support: disabled XBM Support: disabled JIS-mapped Japanese Font Support: disabled GD library functions: getimagesize [o.k.] imagealphablending [o.k.] imagecolorallocate [o.k.] imagecolorallocatealpha [o.k.] imagecolorat [o.k.] imagecolorsforindex [o.k.] imagecolortransparent [o.k.] imagecopy [o.k.] imagecopymerge [o.k.] imagecopyresampled [o.k.] imagecreatefromgif [o.k.] imagecreatefromjpeg [o.k.] imagecreatefrompng [o.k.] imagecreatetruecolor [o.k.] imagedestroy [o.k.] imagefill [o.k.] imagefilter [not installed] imagegif [o.k.] imagejpeg [o.k.] imagepng [o.k.] imagerotate [not installed] imagesavealpha [o.k.] imagesetpixel [o.k.] imagesx [o.k.] imagesy [o.k.] imagetypes [o.k.]

As mentioned allready, I can now verify that; .png and unanimated gif’s work fine. jpg/jpeg’s keep me from using this extention to it’s full extend.

-R-

I have… a different problem to everyone else. 😊

Edit: Never mind, tracked down the problem to cache issues between dev and live.

We are running into a different issue. We can use the MS Img Saver field type within the fieldframe matrix. However, we have been unable to use the field successfully on its own (outside of the matrix).

We are running on EE version 1.6.7. with FieldFrame 1.1.3. and we have CP JQuery set to use JQuery 1.3.2 and the JQuery UI 1.7.1. We have installed the MS Img Saver field type version 1.0.1.

I have verified that the image is uploaded into the tmp directory and is successfully resized and a thumb image created. However, upon saving the entry, the destination subdirectory is never created, in turn the files are not moved and the field in the exp_weblog_data table is not updated.

After spending a couple of hours disabling extensions, etc. believing I might be experiencing a conflict with another extension, I finally managed to isolate where the problem appears to occur. The class property field_array does not appear to be populated when the function submit_new_entry_absolute_end() code is performs the process that moves the file.

To verify this behavior, I added a stand alone ms img saver field and a ff matrix field that contained a ms img saver field and a text field as custom fields to my testing section. Different names were given to each of the fields. For the test I populated both ms img saver fields, each had a different image. Running my debugging statements showed that $this->cell_array contained data and $this->field_array did not contain data. The images for the matrix field were moved to the correct subdirectory, the images for the standalone field remained in the tmp directory.

Has anyone else run into this situation or have any ideas how to resolve the issue?

This extension is in bad need of a rewrite and it also needs to be updated to take full advantage of the new FF features. I’m not able to do this at the moment since I have other projects I need to finish up first. I’m not giving an ETA either since I like to stick to Elislab’s policy on that topic haha.