I'm having a issue with the latest v1.1 of the Amazon S3 plugin, first problem is that it is unable to list files within buckets, I just rolled back to v.1.0 and the files list fine? Second problem I'm having with both v1.1 and v.1.0 is that when trying to create a new file in UMP I am getting the following error "An error occured creating the media item: An S3 Bucket must be specified for S3 PUT object" I am using the root access key, etc...?
Further to this original post, I have rolled back UMP to 1.3 and the S3 provider to 1.0 and everything works fine. Using UMP 1.4 and S3 provider 1.1 brings back both issues. Using UMP 1.4 and S3 provider 1.0, UMP can list the files but still cannot upload!
I have been trying to find issues similar to what you are described, as they have been reported by two other users, but I can't seem to get or provoke the same errors locally. Its been a couple of weeks since I looked at it last, but maybe you can try this build, which is the same build I have sent to other users, but still awaiting replies.
I'm afraid this build does make any difference, I can see the buckets, but no files are shown within them. Also I get "An error occured creating the media item: An S3 Bucket must be specified for S3 PUT object." when uploading through UMP. This is using UMP 1.4 and S3 1.1.1
But if I go back to UMP 1.3 and S3 1.0, all works perfectly.
I can confirm that I am having the exact same problem with Umbraco 4.7, UMP 1.4 and UMP S3 Provider 1.1.1. Is there anywhere that we could download the source code for the provider or at least 1.3 until this problem is fixed?
@Justin I'm working on a fix now so please check back for a fix within the next couple of days.
@Jeavon With UMP 1.4 and S3 1.1.1 installed can I get you to verify that the AWS.dll is version 1.3.1.0 ? I can't reproduce the PUT-error. I did find out why your uploaded movies are not showing up in your two buckets - In my attempt to list folders and files under folders, any files in the root of the bucket won't show up. If you create a folder throught the AWS Console and move your files you should see that the folder and files show up.
I am currently working on the first level files issue.
Guys, I just managed to reproduce the error with the PUT-request if no Contianer is selected in the first dropdown. I realize that having to select a Container, which is actually the Bucket is not very obvious. Do you have any suggestions as to how I can make it better? As I see it I could do a couple of things:
1. Rename Container to Bucket and make some kind of validation telling the user that a Bucket must be selected.
2. Create a standard Bucket option in the configuration of the data type (prevalue editor).
3. A combination where the developer can check which buckets to show in the editor (content section) and validation for selections.
I just found that I can list the bucket contents as long as the items are in a folder. I can't see any items that are at the root of the bucket. Is there anything wrong with listing items that are directly in the root of the bucket?
I was able to upload a file to the folder if I picked the Container, Root Folder and New Folder. I have the structure Bucket > Images > (5 .jpg files). The drop down for "Parent Folder" always just says Root. It does not show Root and Images as expected. However if I pick Root and choose the new folder as Images, then the upload works and the listing displays the file on the existing content tab.
I would suggest option 3 so developers could restrict buckets. You may have a 'backups' bucket for you databases and you don't want people to be able to pick items from that folder.
no there is nothing wrong with having files in the root of a bucket. Its just me that wasn't thorough enough when implementing folder support. I'm fixing this right now,
I'm also leaning towards option 3, as I can see a lot of scenarios where you only want to list a single or couple of Buckets.
For everyone checking back to this thread the issue has been resolved with version 1.2 of the AWS S3 Picker and very importantly version 1.5 of the Universal Media Picker (base) package.
The AWS S3 provider has been updated to support folders (showing and creating) and the ability to limit the buckets that are shown to editors. From one of my previous posts I have implemented option 3.
Great! I just downloaded and installed it. How do I set the buckets that are allowed. I see the list of buckets on my Amazon Data Type but I don't see how to limit them. Is there a config file I need to edit?
Thanks for the quick turn around and awesome plugin.
In the configuration where you enter your API key and secret - once saved you need to reload the datatype with the newly saved properties to get a list of buckets in the same configuration. Its the best way I could do it as the keys are need to get the list of buckets.
oh, and its a listbox with multi-selection, so just ctrl click to select the buckets you want enabled.
Amazon S3 Issue with v1.1
Hi,
I'm having a issue with the latest v1.1 of the Amazon S3 plugin, first problem is that it is unable to list files within buckets, I just rolled back to v.1.0 and the files list fine? Second problem I'm having with both v1.1 and v.1.0 is that when trying to create a new file in UMP I am getting the following error "An error occured creating the media item: An S3 Bucket must be specified for S3 PUT object" I am using the root access key, etc...?
Anyone, any ideas?
Thanks,
Jeavon
Further to this original post, I have rolled back UMP to 1.3 and the S3 provider to 1.0 and everything works fine. Using UMP 1.4 and S3 provider 1.1 brings back both issues. Using UMP 1.4 and S3 provider 1.0, UMP can list the files but still cannot upload!
Hi Jeavon,
I have been trying to find issues similar to what you are described, as they have been reported by two other users, but I can't seem to get or provoke the same errors locally. Its been a couple of weeks since I looked at it last, but maybe you can try this build, which is the same build I have sent to other users, but still awaiting replies.
http://cdn.sitereactor.dk/Files/[UMP]_Sitereactor_Amazon_S3_Provider_1.1.1.zip
This is for UMP 1.4.
Let me know if this makes any difference.
Thanks,
Morten
Hi Morten,
I'm afraid this build does make any difference, I can see the buckets, but no files are shown within them. Also I get "An error occured creating the media item: An S3 Bucket must be specified for S3 PUT object." when uploading through UMP. This is using UMP 1.4 and S3 1.1.1
But if I go back to UMP 1.3 and S3 1.0, all works perfectly.
What can I do to help diagnosing this issue?
Regards,
Jeavon
I can confirm that I am having the exact same problem with Umbraco 4.7, UMP 1.4 and UMP S3 Provider 1.1.1. Is there anywhere that we could download the source code for the provider or at least 1.3 until this problem is fixed?
Thanks,
Justin
@Justin I'm working on a fix now so please check back for a fix within the next couple of days.
@Jeavon With UMP 1.4 and S3 1.1.1 installed can I get you to verify that the AWS.dll is version 1.3.1.0 ? I can't reproduce the PUT-error.
I did find out why your uploaded movies are not showing up in your two buckets - In my attempt to list folders and files under folders, any files in the root of the bucket won't show up. If you create a folder throught the AWS Console and move your files you should see that the folder and files show up.
I am currently working on the first level files issue.
- Morten
Guys, I just managed to reproduce the error with the PUT-request if no Contianer is selected in the first dropdown. I realize that having to select a Container, which is actually the Bucket is not very obvious. Do you have any suggestions as to how I can make it better? As I see it I could do a couple of things:
1. Rename Container to Bucket and make some kind of validation telling the user that a Bucket must be selected.
2. Create a standard Bucket option in the configuration of the data type (prevalue editor).
3. A combination where the developer can check which buckets to show in the editor (content section) and validation for selections.
- Morten
Hi Justin,
no there is nothing wrong with having files in the root of a bucket. Its just me that wasn't thorough enough when implementing folder support. I'm fixing this right now,
I'm also leaning towards option 3, as I can see a lot of scenarios where you only want to list a single or couple of Buckets.
Thank you for the input!
Morten
For everyone checking back to this thread the issue has been resolved with version 1.2 of the AWS S3 Picker and very importantly version 1.5 of the Universal Media Picker (base) package.
The AWS S3 provider has been updated to support folders (showing and creating) and the ability to limit the buckets that are shown to editors. From one of my previous posts I have implemented option 3.
Enjoy!
Morten
Great! I just downloaded and installed it. How do I set the buckets that are allowed. I see the list of buckets on my Amazon Data Type but I don't see how to limit them. Is there a config file I need to edit?
Thanks for the quick turn around and awesome plugin.
In the configuration where you enter your API key and secret - once saved you need to reload the datatype with the newly saved properties to get a list of buckets in the same configuration. Its the best way I could do it as the keys are need to get the list of buckets.
oh, and its a listbox with multi-selection, so just ctrl click to select the buckets you want enabled.
Morten
I saw that right before your post. Thanks again!
I can confirm that it is working. I just uploaded a .jpg and a 40MB video using it.
is working on a reply...