New Extension: nGen File Field for FieldFrame

@Skyw1r3 it looks like that did the trick. I just did a gallery of 103 images with no problem. Thanks so much!

Anyone know how I can output the filetype and filesize? For some reason, Filesizer says it cannot read the file so hopefully Fred is hard at work with a variable that can do the work.

@Skyw1r3 Thanks for that fix - worked for me too. I was getting permission and memory errors but after commenting out those lines things seem to be working fine.

I’m having terrible speed problems using nGen FileField in a FF Matrix.

With a FileField enabled: Script executed in 24.7455 seconds 49 SQL queries used

Turn it off: Script executed in 1.8480 seconds 53 SQL queries used

Through some reductive testing, I believe I’ve eliminated any other cause of this - I’ve gone through and changed all other FF fields I’m using to text, but the slow page load remains.

Commenting out the Directory Iterator function speeds things up a lot, but it’d be nice if that feature didn’t slow everything to a crawl.

Ideas, anyone?

I have a problem with this extension, which has come up after using the plugin successfully previously.

I am 1.6.8 EE, php 5 etc etc. I am using the latest FF 1.3.0 and nGen 0.9.10. The plugin fieldframe works fine, and any other fieldtype is perfect. I have an entry before with nGen where I entered 10 images with no problem to a gallery.

I added a couple of images to a new entry and once saved, got a blank page. To test what is happening, I tried:

1. When I turn off the ngen by putting the field to text area, I get the array of my uploaded images in both my entries in the admin panel.

2. If I remove the nGen field by disabling it from the extension manager, I get a listing of the 10 images from the previous entry, but if I turn it back on, I cannot go into my previous entry in the admin panel it only gives me a blank white screen.

3. With nGen turned on, I cannot add a new entry to the weblog, as I get the blank screen as well. with nGen changed to text or some other FF type, I can add no problem.

GD library is installed and nothing has changed on the site, disabling other plugins does nothing. I even reloaded the nGen files to no avail.

Anyone have any ideas? Debugging turned on gives me nothing as I am getting the blank white screen with no information to go on.

I’m having the same problems as everyone else with DirectoryIterator, it kills my php-memory. Disabling it works, but it’s beautiful functionality that I’d love to have… is there any way to make this process more memory efficient?

I’m not sure if this error is specific to nGen File Field, but I have moved my site to a new domain and the template tag of any custom field using nGen File Field is being ignored. I’ve verified the path to my field types folder and the paths to my uploads folder. Images can be uploaded through the admin fine and the thumbnails even show up in the admin. I’ve also tried creating another FieldFrame field which worked correctly, so I’m stuck with thinking that this has to be something related to nGen File Field. Does anyone have any suggestions on what might be happening? I’m in a tight spot and really needing some help. Thanks for any help!

Getting a PHP Error similar to what others have posted:

[Wed Sep  9 13:13:56 2009] [error] PHP Fatal error:  Allowed memory size of 33554432 bytes exhausted (tried to allocate 11620 bytes) in /home/dandw38/public_html/dandwcontrol/extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php on line 842

Running: EE 1.6.7 (build 20090320) FF 1.3.3 nGen 0.9.10

Not sure how to modify the php.ini file on my host to up the limit to 64MB, currently at 32MB.

Thanks Brendan

This is not something the nGen guys can help you with- you need to look at your hosts help files or contact their tech support on how to up the limit- that or use smaller files.

Unfortunately the hosting provider will not increase the memory limit above 32MB as it’s a shared host.

It would be great if there was an exception built into the script so it doesn’t make the Edit/Publish page blank should there be this error.

There are however some large images in the directory being processed, so I have asked my client to download, process them all so they’re not so huge, and reupload.

Cheers Brendan

I’m suddenly getting an error when trying to publish/edit a post with a File Field - I don’t think I’ve updated anything recently to cause this problem, and both FieldFrame and Field Field are up to date.

Notice: getimagesize() [function.getimagesize]: Read error! in /...abbr.../extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php on line 10

Any suggestions?

Thanks,

I’m having the strangest problem… As soon as I make NGen File Field I can then no longer create a new weblog post with the linked Weblog. I can still edit posts with the NGen File Field activated, but I can’t create a new post.

I get a 500 internal server error in Firebug Net Panel.

I’m running a local server with MAMP. Any ideas?

If I go into my field groups and change the field to anything other than NGen, I can then add a post. I then have to go back and change the field settings so that I can edit the post properly

Was wondering if there was any progress on the next release? SAEF error handling (and this extension in general) is important to at least one project of ours (likely 2) and I would love to stick with it rather than going with a different solution. If a donation would help, I’d be more than happy to give one as this extension is invaluable IMO.

Thanks! .angie

This plugin looks super sweet! I have been having some troubles with MH File lately, and this looks like it could save my day. Thanks for sharing with the rest of us. :D

Here’s a quick piece of PHP code that I posted the other day to someone needing height and width.

I wrote a quick little plugin for that:

SizePlus