New Extension: nGen File Field for FieldFrame

@verveuster: I’m no expert but that error message seems to indicate that there’s an issue with getimagesize. I would suggest trying to leave out some of the add-ons to narrow down the issue further and determine what exactly it is. For instance, do you get the same error when you use nGen FF alone or with just 1 of the other add-ons?

Hey All,

I’m using nGen File Fields for the FieldFrame framework to upload my images and crop them using img Sizer. Everyting was perfect until I changed servers. now the images dont show up on the site, however field frame is showing the thumbnail in the Control Panel. ANy ideas? Thank you

First thought is that the GD image library is not installed on the new server? It’s required by imgsizer.

My guess is that the thumbnails you see in the CP have already been generated by imgsizer and are cached.

wow James thanks for the super lighting response. IT was actually a folder permission issue.

To all mentioning the lack of errors in SAEF. This is a known issue and I’ll be including this functionality in the next release.

Also the next release, as previously stated, will have a setting to disable the “Use existing file” functionality per custom field or FF Matrix cell.

If you’re having a particularly stubborn issue please PM me as it seems the system is not sending me notices when posts on this thread occur. Be aware that it may still take me several days before getting back to you but I’ll know for sure you have an issue.

Thanks!

Couple of feature requests for the next release:

Mark Huot’s file extension had options to “sanitize” filenames (remove all characters except alphanumeric, underscore, and dash), AND to “rename” files (assign every file uploaded a sequential-ish number instead of keeping the original name.) His extension allowed for those on a per-location basis, but honestly i don’t care about that; one single across-the-board setting would be totally fine for me on those. Sanitization is definitely the more important of the two – i have a LOT of clients who don’t realize you shouldn’t use spaces, asterisks, parentheses, etc. in filenames – but i would love it if i could have both options.

Thanks for listening!

@Adrienne Those features have been in nGen File for some time now, we just didn’t make it a setting. It automatically cleans the file name, and if the file exists it adds a numeric increment to the end. If this isn’t working for you then please PM me and we can look into it.

Fred

I had actually noticed the adding-numbers-to-the-end; somehow i hadn’t noticed it was cleaning filenames. In any case, as far as adding numbers goes, what i’m asking for is something different: not ADDING numbers, but completely rewriting the filename on upload. So that my-uploaded-file.jpg becomes, say, 0000001.jpg . In a perfect world it would be a selectable scheme: either plain numbers, numbers with an admin-chosen prefix, a datestamp of some kind (either epoch timestamp or YYYY-mm-dd_HH-ii-ss, with a suffix if more than one file gets uploaded that second), or GUIDs.

There’s any number of reasons why you might want this feature for various sites, including a little extra security-through-obscurity, general cleanliness of the filesystem, datestamping of the files, etc, etc.

Huot’s file extension didn’t have a selectable scheme, but it did allow rewriting (it just used sequential numbers). Again, his had the setting per-upload-location, but i don’t personally care – if it’s a global setting that’s fine with me. If it’s per-location that’d just be gravy!

Adrienne

hi

fixed! fred gave me a solution

I think I just noticed where the issue is in your code. The error is being thrown by your code here: <?php $size = getimagesize(“{serie1}”); $width = $size[0]; $height = $size[1]; What’s happening is that {serie1} spits out a relative URI for the image, but getimagesize() needs an absolute path to the file. So in your case you would need to actually have the following: $size = getimagesize(“/home/www/web146/html{serie1}”); Try that and it should resolve your issue. - Fred

Hi i am using ff-matrix, ngen-fileField, imagesizer, floatbox and some php with getimagesize to build an image-gallery. i get the following error-message: Warning: getimagesize(/images/uploads/reportagen/_ASC5365.jpg) [function.getimagesize]: failed to open stream: No such file or directory in /home/www/web146/html/admin/core/core.functions.php(637) : eval()’d code on line 196 here the code:

does anybody know what the problem could be? thanks Using: EE v 1.6.7 Field Frame v.1.3.3 nGen File Field 0.9.10

MH File compatability: can now be a drop in replacement for single file uploads.

I love you.

That is all.

Buzzed this to Fred via email but if anyone has any advise would be appreciated

http://getsatisfaction.com/brandonkelly/topics/ff_matrix_and_ngen_file_field_mysql_error_1064

Thanks

just an update, ie8 wasn’t showing the upload location field so i didn’t no that i was supposed to be selecting it!

I’m also having memory issues. I’m using it for a photo gallery and it works absolutely awesome up until about 50 images when I get this error:

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 6356565 bytes) in /www/eh10997/public_html/kwsys/extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php on line 119

I’m on EngineHosting with a 64 meg PHP memory limit.

I’ve seen a few other post here with the same issue, but haven’t seen a definitive response on how to handle this. Is there any way to make the nGen FF extension more efficient? Any other solutions? The only thing I can think of is breaking the gallery up into multiple entries, but obviously that’s not the most client friendly solution.

I’m also having memory issues. I’m using it for a photo gallery and it works absolutely awesome up until about 50 images when I get this error:

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 6356565 bytes) in /www/eh10997/public_html/kwsys/extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php on line 119

I’m on EngineHosting with a 64 meg PHP memory limit. I’ve seen a few other post here with the same issue, but haven’t seen a definitive response on how to handle this. Is there any way to make the nGen FF extension more efficient? Any other solutions? The only thing I can think of is breaking the gallery up into multiple entries, but obviously that’s not the most client friendly solution.

The fix I’ve just applied is to comment out line 729-758 in /yoursystemfolder/extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php relating to DirectoryIterator which, as martymix pointed out previously, removes the ‘choose an existing file’ feature.