- Posts: 8
- Thank you received: 0
Support for SermonSpeaker 4.x is canceled as it is for Joomla 2.5. I will gladly assist you with minor issues but I will not fix any bugs anymore in this releases.
The fix is to upgrade to SermonSpeaker 5.x and Joomla 3.x, which is better anyway.
The fix is to upgrade to SermonSpeaker 5.x and Joomla 3.x, which is better anyway.
S3 integration stopped working properly
- David White
-
Topic Author
- Offline
- New Member
-
Less
More
18 Nov 2012 19:12 #2746
by David White
S3 integration stopped working properly was created by David White
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.
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.
Please Log in or Create an account to join the conversation.
- Thomas Hunziker
-
- Offline
- Administrator
-
18 Nov 2012 20:57 #2747
by Thomas Hunziker
Replied by Thomas Hunziker on topic S3 integration stopped working properly
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 think I should be able to fix this, but I need to see how each bucket type works.
Please Log in or Create an account to join the conversation.
- Thomas Hunziker
-
- Offline
- Administrator
-
18 Nov 2012 21:26 #2748
by Thomas Hunziker
Replied by Thomas Hunziker on topic S3 integration stopped working properly
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
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.
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.
The following user(s) said Thank You: David White
Please Log in or Create an account to join the conversation.
- David White
-
Topic Author
- Offline
- New Member
-
Less
More
- Posts: 8
- Thank you received: 0
19 Nov 2012 09:43 #2749
by David White
Replied by David White on topic S3 integration stopped working properly
Wow, that was quick! Thank you for looking at this so promptly.
Please Log in or Create an account to join the conversation.
- Thomas Hunziker
-
- Offline
- Administrator
-
19 Nov 2012 10:25 #2750
by Thomas Hunziker
Replied by Thomas Hunziker on topic S3 integration stopped working properly
You're welcome
![:-) :-)](/media/kunena/emoticons/9.png)
Please Log in or Create an account to join the conversation.
12 Jan 2013 18:27 #2881
by Richard
Replied by Richard on topic S3 integration stopped working properly
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
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
Please Log in or Create an account to join the conversation.
Time to create page: 0.324 seconds