We’re Still Here to Help (Even Over the Holidays!) - find out more here.
Forum Discussion
Solved
Force render issues (raw=1) and shared links won't work for hosting.
images were perfect on all browsers until yesterday afternoon - what is the fix or is this a dropbox issue?
We are rolling out a fix for issues with raw=1 and dl=1 links that started recently. Please try again and let us know if it's still not working.
We use https://plyr.io/ to play audio files hosted on a paid dropbox account through our webflow site. It has worked wonderfully for years. We change the end of the file to the raw=1 suffix.
3 days ago all links stopped working apart from old public links that outdated the new rlkey naming structure - it should be noted that the files with the rlkey naming structure have also been working since the beginning of the year. These links are read only links so no authenitcation required to access or view. They also load fine in a browser either as the file in dropbox or as a streamer.
Is there an option to generate a dropbox link without the rlkey or another work around anyone can think of? PLYR is an open source js library on github.
Would appreciate any help! Thanks.
phantompower wrote:...
Is there an option to generate a dropbox link without the rlkey ...
Hi phantompower,
No, all new links follow that scheme already and no way back. It's not your issue actually. Something else changed recently. Let's hope it's not something intentional and will be fixed. We'll see...
phantompower wrote:...or another work around anyone can think of? ...
The only thing I can think of is to put somewhere in your code a statement like:
l = /^https:\/\/www.dropbox.com/.test(l) ? l.replace('www.dropbox.com','dl.dropboxusercontent.com') : l
Here 'l' is a variable carrying the link. 😉
Hope this helps (to some extent at least).
Thanks - there seems to be a general consensus on other threads that this is an intentional move to restrict people using it as a streaming host. They may even monetise that facility down the line. Who knows. I've found another host removed that works really well for this purpose. It means completely rebuilding the MP3 library I've spent years creating but I can do that over time as and when I need the songs to be visible. (we only show around 40 MP3s at one time for a 3 month period and then we switch to new songs - they are learning resources for a choir)
I think this is a pretty poor business move on Dropbox's part by not even acknowledging what is going on. They obviously are aware of the issue, but can't be bothered to address their customer base?
This has sorted the problem for me.
