Hi Phil, EllisLab has asked third party devs to handle support for our add-ons somewhere other than on these public forms. In the future if you have support questions for any of eMarketSouth’s add-ons please contact me via PM through these forums, at .(JavaScript must be enabled to view this email address), or via our contact form.

That said, “czowOiIiOw==” is base64 for “s:0:”“;” which is serialized array for “array()” which means no data got saved except an empty array! Something is clearly not working as it should be so I’ll follow up with you via PM shortly.

Also worth noting: EE2 SAEFs currently don’t support third-party fieldtypes. It can be made to work, but you’ll have to hardcode the necessary fields in the form yourself.  I gave a little code snippet earlier in this thread that should work for a basic SAEF once we get the add-on working for you.

Hey i am trying to make this work on 1.6 with Matrix. It works like a charm without matrix. But when i am creating a new custom field, i select matrix and when i choose Simple S3 Uploader from the drop down when i submit it it asks for S3 key… but there is no way to enter it there…

isn’t there a field for S3 key in the settings within the FF matrix cell?

Not really, here is what it looks like. (attached image)

my guess is that Matrix isn’t installed properly because it doesn’t appear to have its css and javascript working. Did you upload its themes folder into the proper place? Might want to redownload and update to the latest version/build just in case.

I am looking at purchasing this but I had a question that I wanted to ask first. I see that i can create a filename based upon replacing variables when the item is uploaded. Is it possible for it to also create a folder? Ideally I would like to have s3.bucketname/member_name/uploaded_item.xxx where the member name would create a folder within the main bucket and every time a member uploaded an item it would be placed in their folder.

yup, that’ll work just fine.

technically speaking S3 doesn’t really have ‘folders’, they are just files with slashes in the name… but they’re treated as folders by pretty much everybody so yeah, semantics.

Okay that works for me. Thanks for that

We’re getting a strange behavior with this extension when updating an entry.

Creating and entry and uploading a file with the Simple S3 Uploader works the first time the entry is added. But in our case it seems that when the entry is later edited and updated, the image disappears both in the CP and frontside.

Where do I look for a solution?

Thanks for any help.

That is odd.  Please send an email containing EE version, PHP version, and any other relevant error messages or details to our support line (.(JavaScript must be enabled to view this email address)).

We’re using this add-on on one of our sites and are running into some memory issues.

In doing some testing, I’m trying to upload a single 5MB JPG and have it resized down and then thumb-nailed.  I know this is big but I have to account for less-than-knowledgable clients trying to upload full-quality photos off of their DSLRs.

We had the memory_limit set to 32M in php.ini and ran into a memory issue:

Thinking that it could need a little more, I boosted that to 64M and ran into the same(ish) issue:

In thinking about the file size involved (5MB) and what’s going on (resizing), it just seems like the script should not need 64MB of RAM to accomplish the task.

Has anyone else run into this issue and am I wrong in this assumption?

I’ve had to add the following to the top of the ft.simple_s3_uploader.php file:

Of course, this is just a bandaid solution and hopefully it’s a short-term solution.

Thanks for this excellent add-on and I hope you can let me know what’s going on.

I got to looking around the ‘net to see if this is a common issue and, it appears that it probably is.

I added the following debugging info to your _resize_image() method to give me an estimate of how much memory is needed for an operation:

For that 5MB JPG image I’ve been testing with, it needs close to 60MB of memory to do *each* resize operation.  So, pretty much 120MB of memory for that single 5MB image.  I would have thought it would do a better job freeing up memory between operations (it looks like you are destroying the image data between resizes) but it’s not.

I’m probably going to add in some dynamic memory allocation functionality so that I can ensure that I allocate enough memory for each uploaded image.  Of course, will have to take into account the server’s max_memory but I’m sure there’s some code out there for that.

Hope this helps someone else if you stumble onto the same issue.

Great add-on, thank you so much!

Any chance of adding an unsharp mask option such as Torstein Hønsi’s UnsharpMask function?  The imgsizer plugin for EE uses this function and it makes the thumbs really pop (i.e. photoshop/flickr-esque quality thumbs).  I would love to see this in the next version!

Thanks for your time.

I saw you mention something about the max upload size being limited by my servers php.ini settings. So this plugin doesnt get around that php.ini limitation by uploading directly to the Amazon S3 with is 5GB upload limit?

Unfortunately my host does not allow me to adjust the max_upload_size to over 10M, and I am trying to find a goos solution for sending and sharing very large files. I know I could simply use an FTP program, but i am looking for a good web interface.

So, i guess my question is, is the max upload limited by my php.ini?

I’m getting the white screen error when I try to save the bucket name only. I’ve adjusted every SSL setting in the extension I can find and I still get it.

I’m running 1.7.1 on EC2. Does anyone have any ideas on how to get by this??

** EDIT ***

I solved the white screen issue by updating CURL to the latest version on the server and OPENSSL as well, however, it still errors out when I try to upload large files :-(