Thread

Oy…what a mess.

I have EE site for news text and photo service. The photo service end (set up as standard weblog, not gallery) has gone through many, many different setups/plugins/strategies with variably bad results. The full-res images are already being uploaded to the server through the FoxEE plugin for use as downloadables in FoxyCart (if I can ever get this issue resolved long enough to set up the cart, that is).

The original concept was to use imgsizer plugin or phpthumb to generate thumbnails of those images on the fly, but some of the files are quite large and time out, so we’d get blank pages from imgsizer or broken links from phpthumb.

Since that wasn’t working, I was going to use same local full-res file w/Mark Huot’s File to generate thumbs and call those up instead, but no dice, because we end up returned to empty page after submitting entry w/large file. Firefox reports this error:

Error: uncaught exception: [Exception… "Not enough arguments"  nsresult: "0x80570001 (NS_ERROR_XPC_NOT_ENOUGH_ARGS)"  location: "JS frame :: <a href="http://www.religionnews.com/rnsys/index.php?S=1e794d6a60ee95dcdf82310d113fd652d9358029&C=edit&M=edit_entry&weblog_id=6&entry_id=71524">http://www.religionnews.com/rnsys/index.php?S=1e794d6a60ee95dcdf82310d113fd652d9358029&C=edit&M=edit_entry&weblog_id=6&entry_id=71524</a> :: uploadFiles :: line 2415"  data: no]

Is this memory issue as well? I’m thinking it must be because smaller files seem to work. The large files that don’t work end up in the specified file directory, but at full size w/no thumbnail.

I’m limited to GD2 (host won’t allow ImageMagick), and php memory is alloted at 64MB (and can’t change that). I see file upload limit is listed as 5MB when I look in php info under Admin, and I haven’t asked if that’s changeable, but given the answers to the other questions, I’m thinking that’s a no, too.

Anybody out there doing anything similar that’s working? Sample file that didn’t work via File method this morning is 3.1MB 4368 x 2912 jpeg.

I realize the endgame is to have client create two versions of the file: one full res uploaded for purchase/download, and one low res for thumbs/display on the site, but solution needs to be as low-tech as possible (to avoid having low-res sent to cart by mistake) and client is already overwhelmed with the complexity of the entry process w/o this extra step.

Instead of Huot’s File, have you looked at using an LG Image Manager field that ties into Moxiecode’s ImageManager? Your client should be able to create a new thumbnail right there in the Image manager - which would at least save them from having to have image software to create a second image. At some point in every process, automation just isn’t feasible - I think in some way that two images will need to be made for this situation.

Actually, I’m running into a very similar issue and after debugging, it’s definitely a memory issue. The “easiest” way to deal with it seems at this point to upgrade the hosting server to a VPS… My problem right now is to figure how much memory you need to process 5MB files… If anyone knows where to find this info, a pointer in the right direction would be most appreciated! 😊