Tried this on one hosting environment and worked great. Trying it on another and I’m seeing a blank white page after uploading with nGen file field and hitting submit. It sees the right directory because I can select and image already on the server. Even if I don’t select an image when saving it will give a white page after submission. I confirmed memory, file paths, etc. Any thoughts on what to check next? The upload directory has worked fine in the past for uploading images with the file manager module (I’ve removed that module to eliminate any possible conflicts).
I recently developed a site using nGen File Field to upload photos to a weblog. When I made the site live the path changed to the directory. After correcting all of the paths in the control panel and setting the proper file permissions, I got my images to work - all except on the home page. For some reason it is still rendering the old path rather than the new one, just on this template. When I copy the code and use the exact same code in another template it renders the path correctly. I can’t figure it out. Caching is disabled for the template, and I’ve cleared all of my caches in the admin area several times. Any thoughts?
using this for the first time and I’m finding that when I hit “use existing file” it does nothing. Any ideas?
just to cover the easy solution, “use existing” means it would use an image that was uploaded only through the extension. need to upload something using it first and then in the future that image should be available to you then. it’s basically for re-using images.
Looking back on some previous entries, it looks like the only recommendation is to increase memory allocation. I’ve already got 64MB allocated and it’s still not working. Since some people have said returning to 0.9.8 works, it seems to be a bug.
Does anyone know where I can find a download of 0.9.8? My live site is kind of broken at this point because of this problem. Thank you.
Fred,
I am receiving this error on all my rendered pages:
Notice: Use of undefined constant PHP_URL_PATH - assumed 'PHP_URL_PATH' in /srv/www/htdocs/cswww/c2/MYADMINFOLDER/extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php on line 689
Warning: parse_url() expects exactly 1 parameter, 2 given in /srv/www/htdocs/cswww/c2/MYADMINFOLDER/extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php on line 689
Can you please lend some advice? Thanks!
Unable to delete when selecting the “trash can” icon. No error messages received.
Using: Field Frame 1.3.3 ExpressionEngine 1.6.8 - Build: 20090723 PHP Version - 5.2.8 MySql Version - 5.0.81
*nGen File Field 0.9.10
After having created an entry that includes one FF Matrix Field (no other custom fields included) and attempting to edit, nothing occurs after selecting the “trash-can” icon intended to delete the uploaded asset. I don’t receive the delete prompt.
Yes, the jquery for the CP extension has been enabled.
I can delete rows. I can also re-order rows.
Not sure what to look for. Any guidance would be much appreciated.
Thanks
RESOLVED: seems the nGen folder I FTP’d to my server was missing the “scripts” directory. I downloaded the newest version which did include the scripts folder. Probably my fault but should anyone else experience this make sure all the nGen assets are present.
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: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.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.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
That solved the problem for me too. Client is on Engine hosting and has 64M php memory… how much is needed then for this to run without errors?
Unable to delete when selecting the “trash can” icon. No error messages received. Using: Field Frame 1.3.3 ExpressionEngine 1.6.8 - Build: 20090723 PHP Version - 5.2.8 MySql Version - 5.0.81 *nGen File Field 0.9.10 After having created an entry that includes one FF Matrix Field (no other custom fields included) and attempting to edit, nothing occurs after selecting the “trash-can” icon intended to delete the uploaded asset. I don’t receive the delete prompt. Yes, the jquery for the CP extension has been enabled. I can delete rows. I can also re-order rows. Not sure what to look for. Any guidance would be much appreciated. Thanks
Anyone have a clue what might be going on here. I have no extensions enabled other than Fieldframe and CP jQuery for the CP. The settings in CP jQuery I’ve left to it’s default.
The inability to delete an uploaded file occurs when setting a field to both nGen File Field and to nGen File Fieldwithin a FF Matrix.
Any help would be much appreciated.
RESOLVED: explanation in my original post.
I have gotten this error when trying to edit a weblog item, that uses the ngen fieldtype in BK’s FieldFrame.
I have received this error before, being the memory allowance, I had it set to 96 MB, now I set it to 156 MB within the .htaccess file, which allows me to edit the entry without displaying a blank page.
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
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?
Hi All, looks like an awesome plugin. I am testing some techniques for a new website locally, this seems like the Extension I was looking for. But I get the following error after clicking submit:
We were unable to upload your file. Make sure your upload directory has the correct permissions set.
The permissions are correct. And the ee upload system works fine. Can anybody help me out?
Thanks!
Edit: Just installed the extension to another EE installation. It shows the exact same error, without the php error line. I must be overlooking something?
using this for the first time and I’m finding that when I hit “use existing file” it does nothing. Any ideas?just to cover the easy solution, “use existing” means it would use an image that was uploaded only through the extension. need to upload something using it first and then in the future that image should be available to you then. it’s basically for re-using images.
yeah I guessed that but it doesn’t work. Uploading of images is fine, however just tried to upload a 10Mb .flv file and I got a blank screen after some activity in Firefox.
I tried disabling nGen and using Mark Huot’s File extension and had the same issue so thinking it’s possibly a server thing?
PHP Upload is set to 32Mb and I had my host temporarily set memory from 32Mb to 128 for testing purposes - anything else you guys can think of?
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.