So Symphony is throwing up this error:

User Warning: GenericErrorHandler 512: S3::putObject(): [AccessDenied]
Access Denied on line 358 of file /Users/jdsimcoe/Sites/fire/extensions/s3upload_field/lib/S3.php

I have a user policy on my S3 bucket that allows uploading/deleting and have tested this in Transmit successfully.

Here is my policy:

{
   "Statement":[
      {
         "Effect":"Allow",
         "Action":[
            "s3:ListAllMyBuckets"
         ],
         "Resource":"arn:aws:s3:::*"
      },
      {
         "Effect":"Allow",
         "Action":[
            "s3:ListBucket",
            "s3:GetBucketLocation"
         ],
         "Resource":"arn:aws:s3:::bucket-name"
      },
      {
         "Effect":"Allow",
         "Action":[
            "s3:PutObject",
            "s3:GetObject",
            "s3:DeleteObject"
         ],
         "Resource":"arn:aws:s3:::bucket-name/*"
      }
   ]
}

Any ideas?

if(empty($data) || $data['error'] == UPLOAD_ERR_NO_FILE) {

PHP 5.4

I am using Symphony 2.3.6 on a very large site. After upgrading from version 0.7 to 0.9, every time I would upload something, it would mark it as private. It seemed to be ignoring the public-read (default setting)...

https://github.com/symphonists/s3upload_field/blob/master/fields/field.s3upload.php#L378

Anyway, I tried re-installing it and same issue. I moved back to version 0.8.1 and that corrected the issue. But that version of the extension was before the new S3 library was added to this extension.

It looks as if version 0.9 of the extension isn't recognizing the public-read ACL (or is just plain ignoring it, and setting it as private (Owner access only).

Would be great if anyone could add this extension to symphonyextensions.com
Thanks a lot!

Hi Brian,

I'm having a great deal of difficulty getting this working. I've created a new bucket, and set my access keys correctly (I can see the bucket list in the Section editor). Every time I try to upload, nothing happens — no file is uploaded to S3 and nothing is logged. An empty database row is added to the database the first time, and then not updated after that. Any ideas?

I get this error when saving entries (2.3.3)

Symphony Warning: Illegal string offset 'error'

An error occurred in /Applications/MAMP/htdocs/XXXX/extensions/s3upload_field/fields/field.s3upload.php around line 323



318         catch (Exception $e) {
319             $message = __('The bucket %s doesn\'t exist! Please update this section.', array($this->get('bucket')));
320             return self::__INVALID_FIELDS__;    
321         }
322
323         if(empty($data) || $data['error'] == UPLOAD_ERR_NO_FILE) {
324
325
326             if($this->get('required') == 'yes'){
327                 $message = __("'%s' is a required field.", array($this->get('label')));

Looks like Amazon are changing the way you access the S3 infrastructure.

They seem to want you to setup IAM users and assign policies to each user.

We encountered an issue where connections to the service weren't being allowed, but no message or indication that the creds weren't connecting. Has there been any updates that present us with notification of successful or unsuccessful connection to the S3 landscape from the preferences page at all?

If a file does not exist, datasource output will look similar to this:

<bild url="https://mybucket.s3.amazonaws.com/">
    <filename/>
    <size/>
    <mimetype/>
</bild>

I see two problems here:

1. A URL is still added, although there is no file.
2. Empty elements are output (while Symphony normally omits empty elements).

Well, that's no big deal, but it's not very consistent with Symphony's style either.

When the field is required, an attempt to save an entry from the frontend without any file will result in something like the following:

<events>
    <my-section result="error">
        <filter name="permission" status="passed" />
        <message>Entry encountered errors when saving.</message>
        <image label="Image" type="invalid" message="'Image' is a required field." />
        <post-values>
            <title>My Title</title>
            <date>2014-09-21 17:10</date>
            <image>
                <error>4</error>
            </image>
        </post-values>
    </my-section>
</events>

I tried to find out why I get type="invalid" while the error message is correct—to no avail. Maybe @brendo has an idea? Or somebody else?

I'm just wondering if anyone has used this extension to allow the fields to upload files into a nested folder structure on the bucket? As I understand, this field currently uploads all files into the root of the bucket.

My client requires that images go into an /images folder on the same bucket as files (which would live in /files folder). It seems to be a simple file naming convention which allows the files to be displayed a traditional folder structure via the AWS console, the file just needs to be uploaded with the 'folder' prefixed to the filename.

I'm thinking of enabling this just by having an additional setting on the field which prepends the value to the file upon upload, eg. '/images' would be added to beach.jpg to allow it to live in http://s3.amazonaws.com/{bucket}/images/beach.jpg

Has anyone does this before (happy to merge rather than develop from scratch) :)

It would be great to have a basic progress indicator with this extension. Since many people use S3 to hold larger documents, or audio, or video. It would be nice to have a progress indicator to show the progress of the upload.

I noticed that the S3 library used in this extension doesn't seem to be maintained well anymore. It has some open issues and rather few commits. In addition it doesn't work with AWS Signature Version 4, which is needed for any new regions after January 30, 2014. (For example, the new "Frankfurt" region.)

So I think about switching to the official AWS SDK for PHP. Of course, this is a big library… But probably this one will be maintained better. (And I verified that it's working with Signature Version 4.)

Any thoughts on this?

Should I rather build a separate/new extension?

Is there anybody who has time and interest to help with this (starting not now, but in the next few weeks)?

I am currently generating Amazon S3 images like this on 2.5.2:

http://atheycreek.com/image/2/1920/1080/5/1/atheycreek.s3.amazonaws.com/leviticus-1920_new-54ee6e53ee3bb.jpg

In 2.6.0-rc1 I am getting this error in my Apache log:

127.0.0.1 - - [02/Mar/2015:10:07:40 -0800] "GET /image/2/300/300/5/1/atheycreek.s3.amazonaws.com/podcast-audio-54ac7c6834517.jpg HTTP/1.1" 500 -

Any ideas?

While deploying a client site this week, we twice got bitten by Chrome prefilling the access key value on the Preferences page.

It would prefill this data with our Symphony password, and then as we'd save the preferences, the key would be overridden and access to S3 was lost.

This happened twice because we enabled and then disabled maintenance mode!