Log In
Register
Home
Topic RSS
8:00 pm
20 February, 2011
Offline
Hi I use amazon s3 to host my media files, how can I make sermon browser work with Amazon s3, or has anyone been able to make it work, I tried simply linking the audio to a file in my bucket with public permissions, but I get a file not found error.
8:34 pm
18 June, 2009
Offline
I don't see any reason why it wouldn't work, but I haven't tried it, either. Could you post a link to your site so I could take a look?
3:19 pm
21 February, 2011
Offline
We use it at http://www.kcctriad.com. All you need to do is grab the url of the file on S3 and enter it as a link to an external file instead of uploading the file. Works beautifully.
Just watch your permissions on S3 to make sure the file is accessible by the public.
7:23 pm
20 February, 2011
Offline
Thank for the info, I am still developing the site so it is not even ready, I had just tried to make it work and it wasn't reading the files, but I figured it out. I'll post links once I get it done. Thanks for the help!
4:03 pm
23 February, 2011
Offline
Bencotten, is your url using https?
1:52 am
21 February, 2011
Offline
Sorry for the REALLY late response…
If you're still out there, no we aren't using https.
11:42 pm
3 June, 2011
Offline
When you guys upload sermon files do you upload them directly to Amazon S3 and then paste the URL into Sermon Browser? Or do you use a plugin that syncs your Sermon Browser uploads with S3?
6:13 am
19 November, 2009
Offline
I tried it, and couldnt get it to work. Maybe I'll give it another go. Must have been doing it wrong if you can get it to work…
Dodgeville United Methodist Church -- Dodgeville, WI
11:37 pm
3 June, 2011
Offline
It's not working for me either. Says the file is not found after I past the URL of the file in the attachments section. The permissions are all public and I can browse to the file directly but Sermon Browser can't find it. I'm sure i missed a step somewhere. Any hints?
7:42 pm
19 November, 2009
Offline
Yeah, that's exactly what it was doing to me… If someone could post step-by-step how to make it work, that would be awesome. It's not a permissions thing on Amazon side… Files and folders set to public, and can be accessed directly without issue.
Dodgeville United Methodist Church -- Dodgeville, WI
2:29 am
29 December, 2011
Offline
I believe that I have reproduced the problem you are all experiencing. In the Amazon S3 AWS console ( https://console.aws.amazon.com/s3/ ) you are able to see and follow a URI for accessing a file you have uploaded, such as your sermon. The printed URI uses the https scheme instead of the http scheme.
The current release of sermon-browser does not know that https is a valid URI schema. It assumes that, if your blog is at http ://example.org/blog/ , a URI of https ://s3.amazonaws.com/bucket/sermon.mp3 means that the file should be downloaded from http ://example.org/blog/wp-content/uploads/sermons/https :/s3.amazonaws.com/bucket/sermon.mp3 . I don't know why it assumes a relative URI should be relative to wp-content/uploads/sermons, that seems rather arbitrary to me ;-).
So, the workaround would be to copy the URI from your Amazon S3 AWS console into sermon-browser. But after pasting it, edit the URI to replace "https" with "http". If your file on Amazon S3 is listed as public, it will be accessible through the http scheme even though Amazon appears to be implicitly recommending the use of SSL.
One potential alternative to manually uploading the sermons to Amazon S3 using the console is to use a plugin which does this automatically. I'm not sure if anything else exists, but I have written one myself. Currently it is only available through http://ohnopub.net/w/Sermon_Browser_S3 , but I may register it at http://wordpress.org/extend/plugins/ someday. The workflow that my plugin uses is the following: you upload sermons to your wordpress site as usual; when the cron task starts running, wordpress will start uploading the sermon to Amazon S3; when the upload is complete, the file is optionally automatically deleted from your wordpress server. This allows you to use Sermon Browser's normal methods for uploading sermons and still take advantage of Amazon S3. And, this plugin will use a URI scheme which the sermon-browser plugin doesn't choke on, so you wouldn't encounter this particular error ;-).
(Some URIs in this post were mangled because of the anti-spam system's dislike to them.)
Most Users Ever Online: 40
Currently Online:
17 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
malpan: 2453
jogen: 2440
VanWatterson: 652
GeraldSebring: 364
LucasWoltman: 362
RandellFeenstra: 362
Member Stats:
Guest Posters: 7
Members: 2066
Moderators: 1
Admins: 1
Forum Stats:
Groups: 1
Forums: 2
Topics: 1071
Posts: 4045
Newest Members: Nixon Designs, zolaperry, tanec69, lbakyl, richdorm, Aaron Velasquez
Moderators: Ben Miller (387)
Administrators: Mark Barnes (425)
