New Extension: nGen File Field for FieldFrame

How can I get multiple file uploads without having to manually create multiple file upload fields?

How can I get multiple file uploads without having to manually create multiple file upload fields?

If you use this extension in conjunction with the FieldFrame extension then you can choose this File Field as one of the columns in a FieldFrame Matrix field type and you will be able to do just what you want. Oh and a whole lot more too 😊

Best wishes,

Mark

Hello, I’m having a problem with the nGen File setup- initially I used an nGen file field on it’s own and it worked perfectly- I decided to switch to a matrix set up (for multiple files) and now I get the following error whenever viewing an entry with one (or more) files uploaded…

Warning: Invalid argument supplied for foreach() in /usr/local/pem/vhosts/105642/webspace/httpdocs/system/extensions/fieldtypes/ff_matrix/ft.ff_matrix.php on line 775

PHP Version 5.2.5 ExpressionEngine v 1.6.7 Build: 20090320 FieldFrame (v.1.2.1) nGen File Field 0.9.10

FF Matrix field is product-main-image, col name is main-image:

{product-main-image}{main-image}{/product-main-image}

FF Matrix field is product-detail-image, col name is detail-image:

{product-detail-image}{exp:imgsizer:size src="{detail-image}" width="100" alt="{title}"}{/product-detail-image}

both inside same weblog,

{exp:weblog:entries weblog="product-details" url_title="{segment_1}" disable="member_data|pagination|trackbacks"}

just can’t figure out what’s what, any help is greatly appreciated.

Thanks-

EDIT- this problem is fixed by the post here: http://getsatisfaction.com/brandonkelly/topics/foreach_warning_on_line_775_of_matrix

However I still can’t get a file-loop to show anything… An nGen File Field functions on its own but when used within an FF Matrix, nothing…

After several successful implementations of nGen File Field I am getting the same error as ainsworth.

Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 10368 bytes) in /filepathtosystem/extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php on line 842

My host only allows 16 MB, but I’ve used this plugin on 3 other sites at the same host and this error has never popped-up.

It happened after I attempted to upload an image that turned out to be too large for my site’s memory limit. (This has happened in the past on other sites but it doesn’t cause persistent problems like this time) If I change what file upload location is used, the the edit page loads fine. It seems that the incomplete upload corrupted that file location.

I’m using version 0.9.10. The other sites I run that use the extension are running 0.9.8. Could there be something between these two versions that causes a sensitivity when an upload can not be completed?

This is used in conjunction with FieldFrame 1.1.2

Nah man the upload was successful- but like you said it’s just too large. That error is because its using too much memory to make a thumbnail. The reason it works when you change the upload folder is that there is no image to resize. You just need to use FTP and delete that file and start over using a smaller one.

Thanks to eyevariety and Fred who both suggested deleting the image from the server. That did the trick. That’s a huge relief. I love this extension.

Does anyone have a workaround for a PHP install that does not have the SPL Module installed? I am getting blank entry screens and traced that down to the new DirectoryIterator call in the extension at line 748 in ft.ngen_file_field.php - and I traced that back to the Standard Library.

Was butting my head on this one - thought it was memory issues, but increased that up and still got the blank entry – if I pull the snippet it works, but obviously can’t choose files from a directory on the server.

Thanks everyone, and great extension - this works locally on my machine, but not on the client’s server.

Marty Stake

I’m having an interesting issue I can’t seem to resolve. I have MSM running a few sites. On the primary site, nGen File Field works great. On a second site where I’m trying to create a custom photo gallery, I’m using it with FF Matrix and I keep getting this error when I try to publish a new entry:

MySQL ERROR: Error Number: 1064 Description: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ” at line 1 Query: SELECT * FROM exp_upload_prefs WHERE id =

If I change one of the FF Matrix fields to be something other than nGen File Field, I can publish with no problems. I also tried setting that field to be JUST File Field and it worked with no issues. I only see the error when nGen Field is set as one of the fields in FF Matrix.

Any ideas?

Oh, and I’m running:

EE 1.6.7 Build 20090515 Latest versions of Field Frame and nGen File Field

I also double-checked my upload preferences and I’m pretty sure they’re correct.

Thanks in advance! .angie

EDIT/UPDATE: When I encountered this issue it was on a different computer and browser. Not sure what the issue was but when I got back to my office it was working fine.

Oops

Apologies for not reading all 19 pages regarding this wonderful plugin before posting, but a quick question:

Can “or use existing file” be disabled? This is such a nice, clean plugin, but I’ve got a particular weblog/group of users who should not be able to see all uploads on the server.

Thanks!

Mark

Hello again.

I think this may be a Fieldframe problem again, like my other post about required field not working, which Fred pointed out is addressed (but without a solution yet) by Brandon Kelly on Get Satisfaction

However, what I’ve found now is that an error gets thrown if you have other non-FF fields that are required on the same form that includes an nGen file field.

Here is what happens:

Edit form has textarea (required) and ngen file field (not required).

If i don’t complete the required textarea and leave the file field blank when I try to save I get a ‘required field error message’ as expected. But if i add a file and try to save with the incomplete textarea I get this message:

Warning: getimagesize(/data01/xxxx/public_html/uploads/files/k) [function.getimagesize]: failed to open stream: No such file or directory in /data02/xxxx/public_html/manage/extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php on line 10

Warning: unlink(/data01/xxxx/public_html/uploads/files/k) [function.unlink]: No such file or directory in /data02/xxxx/public_html/manage/extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php on line 335

Fatal error: Cannot unset string offsets in /data02/xxxx/public_html/manage/extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php on line 340

nGen File Field 0.9.8 FieldFrame 1.2.1 EE 1.6.7

I’ve looked through this thread and not seen an explicit answer to this, so I guess I’m just going out on a limb to see if anyone can help me, even if it’s been answered before. I’m getting the PHP memory limit error, here is mine specifically:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 6592 bytes) in /home/ainswort/public_html/woodbrooknativeplantnursery/admin/extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php on line 842

This error comes up when you’re in the edit tab, and you click on an entry to try and edit it. The site still functions fine with what has been put in there before, but editing newer entries doesn’t work (in the weblog where the error first showed up, and in any weblog that uses nGen).

I’m getting the same error as ainsworth on a client site on EngineHosting, only it’s a 64M limit that’s being exceeded. I’m using 0.9.10. This is the response the client received from EngineHosting:

“Its not actually a hosting space issue but a RAM issue. The best option here would be to review the scripts and installs you are running and possibly change them around to use less memory.”

Is there anything I can do on my end (short of editing the extension) to allow my client to get access to their weblogs again?

One thing I found last night (hoping there is a fix) is that if you are using a directory with lots of big files in it (my dir had a bunch of big movie files inside), and if you click to edit an entry that uses that File Location, the CP just hangs for a while, spinning, and finally pops up.

I think it is the DirectoryIterator bits in the plugin - looking at all the files and creating that list for the “choose an existing file” dropdown. I commented that piece out – line 732 - 758 – and this alleviated the long wait time for the entry. Obviously, this gets rid of that list of already populated files, but it let the extension function like the old MH File Plugin. Maybe this could help ya.

Thoughts?

I think it is the DirectoryIterator bits in the plugin - looking at all the files and creating that list for the “choose an existing file” dropdown. I commented that piece out – line 732 - 758 – and this alleviated the long wait time for the entry. Obviously, this gets rid of that list of already populated files, but it let the extension function like the old MH File Plugin. Maybe this could help ya. Thoughts?

Brilliant – thanks! At least the weblogs are editable again. I’ll just let the client know I had to disable that part of the add-on.