S3 integration stopped working properly

Somewhere a couple of updates ago S3 stopped working properly. The credentials are all correct and I can select a file I've uploaded to S3 from the sermon editor. However, it doesn't play.

The reason is the URL for the sermon is the S3 control url (s3.amazon.com/<bucket>/<file>), when what is needed is the access link on the correct S3 end point (in my case, s3-eu-west-1.amazonaws.com/ /).

Any chance of this being fixed soon? I'm copying and pasting links from S3 at the moment.

Thanks,
David.

Hmm, that's interesting. I've tested it with an standard US bucket where it works flawless. But it looks like for european buckets, the URL is different.

I think I should be able to fix this, but I need to see how each bucket type works.

I've fixed it in the trunk, so the next release will have the fix included.
If you want to fix it yourself, you can unzip the attached file and upload it to

/administrator/components/com_sermonspeaker/models/fields/customfilelist.php

There are additional issues where it displays the wrong path in the edit forms. These will also be fixed in the next release, but the attached file will not fix those. These bugs are only a display issue, so this shouldn't generate any problems.

Wow, that was quick! Thank you for looking at this so promptly.

You're welcome

Hello Thomas,
It seems there might be another tweak needed for this file and for \controllers\file.json.php

CHANGE:
' s3.amazonaws.com/'.$bucket.'/'.$file
TO:
'http://'.$bucket.'.s3.amazonaws.com/'.$file

So for us instead of:
s3.amazonaws.com/bgspreken/2013-01-06_ramon_bonte.mp3
Amazon want us to use the frontend endpoint:
bgspreken.s3.amazonaws.com/2013-01-06_ramon_bonte.mp3

Can you look into this for a next version?
With kind regards,
Richard van Oosterhout, The Netherlands