Copy public link is not working on dropbox.com

Here is trick how to create public link till DB fix it.

Click on file in public folder, you want to share in public

Click on Share option Rt upper corner

Select create link in popup window - then select copy link.

Now paste this link, It will be something like this

https://www.dropbox.com/s/********/FileName?dl=0

Now delete " ?dl=0 " from end of link name you have copied and replace " https://www.dropbox.com " with " https://dl.dropboxusercontent.com "

So after this your link will be look like this

https://dl.dropboxusercontent.com/s/********/FileName

Now this is your public link and you can share it to users without having DB account.

KH - very many thanks! This works, and while it is inconvenient it will do until DB get their act together.

Come on DB - can't be that difficult...

I finished copying my files to a new host, good bye Drop Box, I'm dropping you and your box.

I turned in a support ticket on 9/22 for this after a few days of it not working. We are over a week into this issue. I find it to be ridiculous its not fixed and most of all, the response I got from Dropbox. Here it is:

Thanks for reaching out about this! I've passed your report along to our engineering team who will endeavor to fix it.

As there is now a report with our engineering team, due to how our ticketing system works, we will need to close this support ticket. We will reach back out with any further information or questions.

We appreciate your patience in regards to this matter. In the meantime, please let us know if you any other questions or feedback.

This tells me nothing and not only am I frustrated....too many users are as well and DROPBOX...YOU NEED TO ADDRESS YOUR USERS BETTER ABOUT THIS!!!!

Same problem.  I need this feature back NOW.  I've tried this from Chrome, Firefox, IE.  From at work and at home, and on mobile.  The feature is 100% broken.  Starting to migrate my stuff over to OneDrive right now.  This needs to be fixed within the week.

Dropbox's web interface has always been glitchy as he11, but this gets into the unprofessional range.  Especially as a paid user of their service.

HK.  Unfortunately this does not allow for embedded images.  Only previewing on Dropbox's site.

Now this is your public link and you can share it to users without having DB account.

That's not a Public Link, but a Share Link, and they act slightly different. If you see your user number in the link such as /u/1234567 (as opposed to a randomly generated number) then it's a Public Link. If you see a random number in the link such as /s/0skuwdlhg6q4fol then it's a Share Link.

Share links open by default on the preview page but you have more control of them by changing the ?dl=0 at the end. A 0 will preview, a 1 will download, and ?raw=1 will present the file in its raw format (good for embedding images). See here and here for more info.

Share Links can also be created for any file or folder in your account, where Public Links can ONLY be created for files in the Public folder.

Unfortunately this does not allow for embedded images.  Only previewing on Dropbox's site.

Create a share link and change ?dl=0 to ?raw=1.

@ clay s.

That's a copy paste formula, you obviously did it wrong.

When opening a ticket ask to NOT give you a copy paste formulae answer and explain why they can't be botehred to fix the issue after a week, you'll get the same answer as i did and get pissed off and move your files to a new host.

Which I strongly recommend.

How hard is it to fix this? You guys are a multi-million dollar business. I'm using mediafire instead until the fix is applied as it shouldn't be impossible to share a public link with my co-workers.

Another workaround we found was to just move the files out of the public folder and share them from another folder.

It only happens for us from the public folder, for both copying the public link and using the "Share" option.

To the Dropbox team, here's the error we're getting pasted below. Looks like a method got removed that was still relied on. I know you're getting beat up over this, but surely you have unit tests to catch this sort of thing before pushing a new version, yes?

TypeError: this._append_ellipsis is not a function

at Function.showCopyPublicUrlModal (browse_actions-vflqAxCFc.coffee:46)
at file_actions-vflb1Vq2X.coffee:232
at Object.execCb (require-vflLeRP3M.js:1678)
at Object.require.s.contexts._.execCb (require_config-vfltnDUQG.coffee:149)
at Object.check (require-vflLeRP3M.js:873)
at Object.enable (require-vflLeRP3M.js:1165)
at Object.init (require-vflLeRP3M.js:783)
at require-vflLeRP3M.js:1441