New Extension: nGen File Field for FieldFrame

@Bud Parr - A few of us have run into this issue, a short solution, keep in mind it’s not a pretty solution but it works for now.

Solspace Gallery Solution

Hey, thanks, I’ll check it out.

Moderator’s note: Merged as per request.

After setting everything up in a sub directory on a domain (http://www.mydomain.com/sub/…eefiles…) an error is thrown when uploading a file using either the Cp or SAEF.

“The upload path was incorrect.”

Using a FTP program you can find the file uploaded to the right folder as set up in the ‘File Upload Preferences’.

When you peek under the edit tab, the entry is made, there even is mention of the file uploaded. However it added a second /sub in the url -> http://www.mydomain.com/sub/sub/path_to_uploadedfile/

So far I have * Used Lodewijks’ File module or the CP file upload -> no errors are generated, * Verified the path in the CP settings and SQL table -> both point to the correct location, * used small & biger, jpg- and gif’s -> both generate the error using the file field.

Anyone has ideas on this behavior ?

FieldFrame (v.1.1.2) nGen File Field 0.9.8

EDIT This was supposed to go into the New Extension: nGen File Field for FieldFrame thread. Admins can you please transfer.

I’m having an issue with the nGen File Field on a SAEF when used inside an FF Matrix field.

Whenever I add a new row, a bunch of lowercase “n“‘s appear. 3 of them below the File input, and one below the link to use an existing file.

This only happens on rows added, not to the initial one.

It’s almost like it’s not recognizing the \n for new line in the php code and just outputting those n’s.

This is with nGen File Field 0.9.8 and FieldFrame 1.1.2 on ExpressionEngine 1.6.7 with MSM.

Apologies if this has been mentioned already (this thread is getting fairly long now), but is there any plans in the pipeline for adding similar functionality to MH File extension, whereby under File Upload Preferences there are additional settings. Namely “Keep originals” and “delete from server”.

I have maximum height and width set under the standard settings, and these are currently being ignored by File Field, so users can upload silly sized images - there’s currently a 7Mb image on the server (in the real world client education simply doesn’t work!).

Whereas MH File would resize to whatever was specified in File Upload Preferences, create a new file and delete the original ‘huge’ upload.

First, to the guys at nGen, thanks for creating this field type. I’m hoping you can shed some light on the following:

I have a fresh install of nGen File Field v. 0.9.8. Can create the field type, shows up in the publish and edit pages, I can browse and select an image, but when I upload the picture and submit the entry, I get the following message:

Fatal error: Call to undefined function imagecreatefromjpeg() in /path removed/extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php on line 783

I thought it might be an issue with Publish Tweeks, but uninstalled that and still doesn’t work. Tried a gif and got the equivalent error for the “imagecreatefromgif” function. Any thoughts on what’s triggering the error?

Thanks!

EE 1.6.7 Publish Tweeks (v.0.8) FieldFrame (v.1.0.8) MD Markitup (v.1.6.1) Edit Tab AJAX (v.1.2.2) jQuery for the Control Panel (v.1.1.1) Gypsy (v.1.0.6) Playa 2.0.6

I’m having two distinct issues.

1) When trying to upload an image via file field, there is an additional /sub thrown into the url. Ex: www.example.com/subfolder/images is showing as www.example.com/subfolder/subfolder/images

I have quadruple checked that the file upload path settings do not contain errors.

2) When using file field in a matrix where I would like to select more than one image from existing files on the server, I am unable to “choose an existing file” beyond the first row of the matrix. Attempting to do so in the second row tosses my view up to the top of the publish/edit screen. I scroll back to the field in the matrix to find that nothing has happened.

Is anyone else finding this?

I’m also getting this issue on a new install of nGen File Field

Fatal error: Call to undefined function imagecreatefromjpeg() in /path removed/extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php on line 783

I’d like to second Twobelowzero’s suggestion for respecting the maximum height and width set in the file upload preferences. I use Image Sizer to resize images before displaying them, however I recently had a content manager accidentally upload an image that was so large the server hit its memory limit when trying to resize the image. This could be avoided by a height and width limit.

With that said, this is a fantastic plugin that solves many problems. Thanks to nGen for the good work.

Is there a quick hack to enable image sizing? I tried using imgsizer and after chasing down a weird error for the past few weeks I’ve come up empty. My solution was to use the the nGen File Field along with the image sizing preferences but this apparently isn’t supported!

Anyone? I’m supposed to launch this site on Friday!

I’m getting a big fat blank page when I try to publish an entry that uses the file field.

Another site I am developing is fine and it is using the same extensions. Very strange.

Ah it does that if the “Server Path to Upload Directory” is wrong.

Perhaps a warning would be nice!

@Twobelowzero + @Scheffey Regarding the image dimension settings, you can use the file size setting to limit things. So you can prevent 7MB images from being uploaded by setting the max file size to 1-2M. This will usually avoid crazy images and memory issues. We may still look at adding that feature in future however, but no promises.

…when I upload the picture and submit the entry, I get the following message: Fatal error: Call to undefined function imagecreatefromjpeg() in /path removed/extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php on line 783

Thanks to a PM from Fred, and Brandon Kelly elsewhere, who identified the issue. The new server didn’t have the GD library installed. So if anyone ever runs into that pesky fatal error above, confirm that GD is installed.