S3 upload creating new untitled folder in bucket

Hi Thomas,
After implementing the S3 storage with SermonSpeaker, everything seems to work fine, except that when I upload from the backend, the file path to the files includes an additional slash after the bucket name:

s3.amazonaws.com/calvary-troy-sermons//1...ose-of-the-gifts.mp3

This autocreates an untitled folder inside the bucket, which is accessible from the S3 console; however, I use Transmit for FTP and S3 management, and I can't seem to get this untitled folder to load in Transmit. I would just deal with it as everything functions on the website and from the S3 console, but I would really like to be able to manage these sermons from Transmit as well. Is there anyway to get the mp3's to be posted straight to the bucket rather than an untitled directory?

Here is a view of the untitled bucket folder created in the s3 console -->


These are the views from the backend settings and upload dialogue screens -->



My backend does have my access and secret keys, I just removed them for these photos.

Thanks you so much for your help!

It shouldn't do that double slash for sure. Looks like a bug to me. I'll try to figure out where it comes from

Can you try with the attached version? Just install over the existing one.

Hi Thomas,

Looks like it worked! Thank you kindly!

Joe