New Extension: nGen File Field for FieldFrame

Bug? SAEF uploading is not showing errors associated with file upload Preferences

Details:

I have my file upload preferences set for max file size of 512k. Uploading anything larger through the CP will show the red error at the top as its suppose to. However, when I upload the same image through an SAEF, no error shows and the page submits taking my users to my thank you page. The image does not save to the server. If I upload an image under 512k through SAEF all works fine.

Using: EE v 1.6.8 Field Frame v.1.3.0 nGen File Field 0.9.10

Those of you experiencing issues with exif_imagetype() please check if you have any small or empty files in you file upload location(s). exif_imagetype() requires the file to be at least 4 bytes to do it’s thing. I’ll be working on adding code to avoid this situation in the next release.

Please PM me if this doesn’t apply to you and the issue persists.

Has anyone had issues with nGFF and MSM? I’m using the following code to pull out an image I’m storing alongside a news item on a second site, and every other field is pulled out OK, just not the nGFF field…

{exp:weblog:entries site="default_site" weblog="news_and_events_rag" disable="categories|member_data" sort="desc" limit="6" paginate="bottom"}
...
{news_image}
...
{/exp:weblog:entries}

I’m using the same field group on a weblog on the default site and it’s pulled out OK, it’s just this one…

Thanks,

Fred kindly fixed my issue - I had an errant field in the second site that had the same name as the one I was trying to pull out in the first…

Those of you experiencing issues with exif_imagetype() please check if you have any small or empty files in you file upload location(s). exif_imagetype() requires the file to be at least 4 bytes to do it’s thing. I’ll be working on adding code to avoid this situation in the next release. Please PM me if this doesn’t apply to you and the issue persists.

I had an empty file within my upload location - deleting this file solved the error.

Thank you very much! patte

Getting following errors after moving development version to live site.. checked most things, seems odd, works fine on the development server. Any ideas anyone?

Warning: mkdir() [function.mkdir]: No such file or directory in /home/.economizing/goldsman/alangoldsman.com/admin/extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php on line 714

Warning: chmod() [function.chmod]: No such file or directory in /home/.economizing/goldsman/alangoldsman.com/admin/extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php on line 715

Notice: Undefined variable: _SESSION in /home/.economizing/goldsman/alangoldsman.com/admin/extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php on line 722

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /home/.economizing/goldsman/alangoldsman.com/admin/extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php on line 722

Fixed it… so dont worry. Was actually the path to the folder somehow has changed back to the original.

I was getting the dreaded white screen of death on the Publish page when using nGen File Field with only a few upload destinations and not others. It was driving me nuts until I noticed that removing all PNG, GIF, and JPG files from the folder made it work just fine!

I checked my mimes.php and it does indeed have PNG, GIF, and JPG listed there, so…why doesn’t it like image files??

Could someone please verify that the nGen file field shows errors if an uploaded image exceeds the file size set in the upload preferences? I’m not receiving any errors on my SAEF but the image doesn’t upload if it exceeds what I have set. So it appears there may be a bug related to error display.

Hey Fred,

I love the plugin. Thanks so much for making it. I made a mod to it that I thought you might be interested in, and you might want to include in a future version.

var $default_site_settings = array(
    'ngen_file_show_existing' => 'yes'
);

function display_site_settings()
{
    global $LANG;
    $SD = new Fieldframe_SettingsDisplay();

    $r = $SD->block('Settings');
    $r .= $SD->row(array(
            $SD->label('Show existing files?', ''),
            $SD->radio_group('ngen_file_show_existing', $this->site_settings['ngen_file_show_existing'], array('1'=>'yes', '0'=>'no'))
        ));
    $r .= $SD->block_c();
    return $r;
}

And within function display_field, surrounding both instances where it prints out the ngen-file-existing and ngen-file-choose-existing div’s:

if ($this->site_settings['ngen_file_show_existing'])
{
    $file_field .= ......
}

Now in the backend FieldFrame settings you can choose whether or not “choose existing file” displays. This is useful to me for 2 reasons:

1) In a front-facing SAEF, you may not want to show all visitors the contents of your file upload location. 2) On occasions where there are lots of files in that location, I’ve run in into PHP memory errors, so it’s useful for me to turn that feature off entirely.

Keep up the good work!

Great plugin… thanks!

Could someone please verify that the nGen file field shows errors if an uploaded image exceeds the file size set in the upload preferences? I’m not receiving any errors on my SAEF but the image doesn’t upload if it exceeds what I have set. So it appears there may be a bug related to error display.

anthonys: I can verify this. I’m having the same issue. I’ve set both, file size and image width and nGen doesn’t seem to throw an error. The file still gets uploaded though and shows in the resulting entry. (Fred, I’m using your Preview version.)

.angie : thank you for verification. I thought I was the only one. My image doesn’t get uploaded though like yours does, I checked the server for the file, not there and not in the CP edit entry. I have sent Fred a PM earlier about these issues. Hopefully it will be fixed shortly and released as an updated version. 😊

I forgot to mention that although my images get uploaded, sometimes it causes a PHP memory error. haven’t nailed down exactly when this happens, but I know it’s the image sizes causing the issue because as soon as I delete the images via FTP the error doesn’t occur.

Eager to see this fixed as well. 😊