New Extension: nGen File Field for FieldFrame

I’m trying to figure out a way to have nGen ask me for which folder to upload within the one specified in the upload settings. Is this a feature request or is there a possible workaround?

Love the plug-in Thanks

Hi,

Using the latest version 0.9.10 I experience problems. There is some kind of .ftpquota file added to the server directory which triggers a whole series of errors.

The warning starts when editing an article within Expressionengine.

Warning: exif_imagetype(/home/username/public_html/down/headerfoto//.ftpquota) [function.exif-imagetype]: failed to open stream: Permission denied in /home/username/public_html/system/extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php on line 797

I am also using wygwam and the above error continues with:

Warning: Cannot modify header information - headers already sent by (output started at /home/username/public_html/system/extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php:797) in /home/username/public_html/system/extensions/fieldtypes/wygwam/ft.wygwam.php on line 348

This error continues for 30 maybe 40 times…

But, deleting the .ftpquota file in the server directory /public_html/down/kopfoto/ resolves the error. However, for some kind of reason the .ftpquota appears again… sigh…

Any idea what to do?

Regards, Steef

.ftpquota I believe is set by Apache or CPanel when you create a FTP account on that particular folder (down/headerfoto). Deleting will just mean the server re-creates it. If you’ve got CPanel, either check the size settings for that specific ftp account, or delete the account (ensure you don’t remove the files as well!!!!) and just use your primary FTP account.

Edit: Further thought - I’d assume it’s trying to process all files as images in that folder and hitting the .ftpquota file and getting the error, so irrelevant to ftp settings - you’ll just have to remove the FTP account for that folder - or move it to the previous folder (/down/).

Thanks Twobelowzero. I deleted the ftp-account and it seems to work. The reason why I added the extra ftp-account is that I can easily upload screenshots from Voila into the directory I intended to use with EE. This, without using and sharing my primary ftp-account.

Has anyone been able to use nGen File Field with NSM Publish Plus?

I have been using nGen to great effect for a few months now and it works great.

I asked Leevi for help with this but he said “Third party plugins must support quicksave and preview functionality to be fully compatible with NSM Publish Plus.”

NSM Publish Plus adds buttons to ‘Save Draft’ or ‘Submit for Approval’ for users who are editors and ‘Save Draft’, ‘Quicksave Revision’ and ‘Save Revision’ if they are publishers. It seems like Save Draft is built off the ‘Preview’ because it shows the new file if you hit ‘Save Draft’ (or Preview) but of course that disappears if you go back to edit without first ‘Submit for Aproval’ or ‘Save Revision’.

Really confused at this point…

So found the nGen file field and love it but when I use FF matrix I run into problems. I can use the EE file upload fine. I can use nGen fine in its own field. When I use nGen file field with FF matrix I get this SQL error when I try to publish or edit an 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 =

I notice I do not get an option to choose the “file upload location” when I use FF matrix. Thanks for any help Mike

update:

With a little MYSQL hacking from this article fixed my problem, just had to go back and re do the nGen fields.

http://ellislab.com/forums/viewthread/132347/

Thanks StudioKong

Has anyone been able to use nGen File Field with NSM Publish Plus? I have been using nGen to great effect for a few months now and it works great. I asked Leevi for help with this but he said “Third party plugins must support quicksave and preview functionality to be fully compatible with NSM Publish Plus.”

I’ll second this question. I’ve really been wanting to implement Publish Plus, but I need File Field to work as well.

Will nGen file field eventually have the ability to resize the photos automatically when uploading to a specific (maximum) dimensions, just like the file extension of mark huot?

Does anyone know how to use the show=”filename” parameter with File Field? I’m completely stumped. Thanks!

Seconded.

It’s very simple if you’re using it with FF Matrix you just use it within the quotes of your ngen FF field and not the quotes of the FF Matrix fields pairs.

{application_images}
{image show="filename"}
{/application_images}

In the above code the matrix field is application_images and the ngen FF field is image. I hope this helped you

Perfect! Thanks.

Feeling kinda dumb now.

Ran into a new bug that seems to have popped up after installing MSM and creating a new site:

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

I’ve just experienced this on a site that was working previously.

Files are still uploading but the error is bugging me.

Did you get a fix?

I don’t use MSM but ran into this as well. Just posted a fix in this thread.

In our case it was due to file upload errors storing nothing in the field - even though the file gets uploaded. Field frame wouldn’t show the blank FF field and it doesn’t cause any display errors - easy to miss. The fix mentioned above will also prevent the error in case of super tiny files (blank.txt for instance).

Maybe a bug fix to be added to ngGen FF for FF? Not sure, it might hide other problems so maybe not (upload errors).

@Dylan Smith/ContextDesign - someone told me they’ve used Publish Plus with nGen but I’ve yet to make it work. Have you heard anything from Leevi? If he gets the request from multiple people maybe he’ll look into it?

I don’t use MSM but ran into this as well. Just posted a fix in this thread. In our case it was due to file upload errors storing nothing in the field - even though the file gets uploaded. Field frame wouldn’t show the blank FF field and it doesn’t cause any display errors - easy to miss. The fix mentioned above will also prevent the error in case of super tiny files (blank.txt for instance). Maybe a bug fix to be added to ngGen FF for FF? Not sure, it might hide other problems so maybe not (upload errors).

was that in response to me?

I forgot to mention I don’t use MSM either.