I had the same problem with Google Drive, so switched over to Amazon S3 as suggested. Much better way to go. Had initial luck uploading art to assets as follows:
>> Add/edit cover (attachment)
>>Upload a file (using Amazon S3 storage connection) (attachment)
But now the same problem is happening...clicking Upload a file doesn't open a dialogue box).
Tried / Checked the following:
>Updating Flash (didn't think it had anything to do with it, but still tried)
>Tried in all Browsers for mac osx: Firefox, Chrome, Safari
>Checked my Amazon S3 account, seems to be OK. (attachment)
I'm having this same issue at the moment. Attempt to upload items using my Amazon S3 account and no dialog to upload shows. Before I move forward with making a new S3 connection I need to know what happens to the items added through the previous connection. Are the downloads still accessible? Or will I need to re-upload everything through the new connection? Might be a novice question here, but, well, yeah... help! xoxo
I've always put my downloads for the assets on my own server, so i can't confirm 100%... but if logic works out this time around, it seems that your previous Amazon S3 stuff should be OK post-new connection.
Tom Filepp on 20 Mar, 2017 04:43 PM
You can actually add a new connection and use it and this won't affect anything on the old connection, so long as you don't delete it. We recently did some upgrades to the Amazon S3 integrations which may be what's causing these initial problems you're having. It seems like your old connections may have gotten stuck while upgrading. We're looking into it and will let you know ASAP.
In the meantime, no reason to not just make a new connection if it's slowing you down.
Tom Filepp on 21 Mar, 2017 09:35 PM
So it looks like the ticket here is really just to create a new S3 connection if your previous one was created before March 1st. The old assets and downloads will continue to work.
Amazon is being a little finicky with some of the upgrades to old connections, so this appears to be the best solution moving forward. Putting this here for posterity. Thanks for pointing out the issues you were running against and let us know if you have any questions!
Tom Filepp closed this discussion
on 21 Mar, 2017 09:35 PM.
Tom Filepp re-opened this discussion
on 21 Mar, 2017 11:09 PM
Tom Filepp on 21 Mar, 2017 11:09 PM
I actually want to make an addendum to this that we just confirmed, for all of y'all that want to just keep using the old bucket:
If you log in to your AWS console (https://aws.amazon.com), go to S3 and go to the bucket you're having an issue uploading to. If you hit the Permissions tab, then the CORS configuration tab, delete the existing text in the editor and replace it with the following XML. Hit save and then you should be able to upload again on that bucket!