New Extension: nGen File Field for FieldFrame

I have left the max post field blank.

PHP will have default values for two directives:

upload_max_filesize post_max_size

You can find their values in phpinfo(). Make sure they’re big enough for your file.

upload_max_filesize: 20M post_max_size: 8M

The biggest file has been 2MB

Got a couple of problems I could use some help with. Seems to be related to use with Brandon’s FieldFrame add-on, as I can upload fine using nGen outside FieldFrame.

Using the latest versions of FieldFrame and nGen, when I view the publish/edit page I get:

Notice: getimagesize() [function.getimagesize]: Read error! etc…

I’ve had this before on other websites, and fixed it using an older version of nGen. Not ideal, I know. Tried on this site and I no longer get the error msg on page load, but when I try to add an image I get an unhelpful error msg in red box saying “Something happened while uploading myimage.jpg. Please try again.”

Anybody had this before? Like I say, seems to be restricted to use of nGen inside a FieldFrame matrix.

Had a quick scan through the thread and couldn’t see any fixes, but apologies if I missed em.

Anyone?

Hi, Can anyone help Mandarax and me with our Fatal error: Out of memory issue please? See posts above. I’m (my client is!) getting pretty desperate for fix. Thanks!

Matthew, I managed to fix the problem. I don’t know if this will work for you but here’s what I did: - The out of memory error was only occurring on one weblog. - The nGen File Field was being used as a custom filed in that weblog - I went to my file upload preferences to find out where on the server that custom field was uploading - I found the problem file, a 300dpi image that my client had tried to upload - Every time the nGen extension tried to create a thumb for that image it would choke causing the problem and error message - I copied all of the images from that folder via ftp onto my computer and then deleted them from the server - Went back to the EE control panel and went to publish an article in that weblog - The weblog is now working no erro messages - Resized the large image in Photoshop to 72dpi - Went back to the EE control panel and edited all posts that had an image upped through the custom field - Luckily this was a very small weblog with only 5 entries so this method worked Hope all of that is clear and that it may help you out of a jam! Cheers, Liam

I have to say I love and hate this add on…. let me explain. We’re having similar problems:

• We cant up the server limit beyond 64 meg
• The client is not that computer savvy so 300dpi image may well be uploaded as she deals with photographers all the time. Example last file that killed the weblog was 38meg.

Excuse my ignorance here but it seems file upload its trying to upload a file then it fails. If there no way of getting the fileupload to check file sizes or dpi before these problems occur?

Or give more error messages and give user the option to deleted / remove problematic files.

I’m just coming at this from my clients point of view. I really want to use this plugin, please let us know any possible alternatives.

Is there any issues with nGen fieldtype being a memory hog? Here is my error msg:

[Mon Oct 05 10:46:27 2009] [error] [client 172.16.20.76] PHP Fatal error:  Allowed memory size of 100663296 bytes exhausted (tried to allocate 23624 bytes) in /web/system/extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php on line 842, referer: http://www.domain.com/admin/index.php?S=5d2de1f94ae6e1dd80e761f2d448b7121d57ef77&C=edit

I have the exact same issue here. I was able to get around by upping the maximum amount of memory php can use but it’s not a very nice thing to do. Anyone else is having this problem?

I get this problem too, both locally and on the remote server, which is strange because it never used to do that. After trying to upload some images I can’t even get back to the edit page for that particular entry.

I’m using nGen to show one random image pulled from my portfolio. At first glance it looks like this code should work but something is missing. It’s only showing the first image of the set and never changes. There are a dozen or so images in the entry I’m referencing. Any ideas would be appreciated! The “port_img” is the field containing the uploaded image.

{exp:weblog:entries  sort="asc" weblog="portfolio"  disable="pagination|member_data|trackbacks" rdf="off"   url_title="exterior"}
    {gallery_set limit="1" orderby="port_img" sort="random"}
      <a href="/portfolio/{url_title}">{exp:imgsizer:size src="{port_img}" width="295" alt="{port_caption}"}</a>
        {title} sample - <a href="/portfolio/{url_title}">see more</a>
    {/gallery_set}
{/exp:weblog:entries}

David– is {gallery_set} a FieldFrame matrix?

Yes, {gallery_set} is a FF Matrix field.

.

David, try removing the orderby=”port_img” from your {gallery_set} tag pair, it shouldn’t be necessary if you are randomizing, and maybe that’s what’s causing your problem. I would also suggest checking your cache settings and make sure you have the latest FieldFrame.

Have other people had problems with the PUBLISH tab going blank using nGen? I just posted to this forum about it: http://ellislab.com/forums/viewthread/135719/#686861

Any clue how it could be fixed (sorry if this has already came up in this thread, I couldn’t find it using search).

Thanks, Chuck

A blank publish screen is usually a PHP error. Turn on error reporting or ask your host to give you the exact error. My guess is that you just need to raise your PHP memory limit– I keep mine around 128M for most sites.