Forum Replies Created
-
Posts
-
I get this right away as soon as I click the link.
I have actually purchased the Dropbox addon but trying to get my site working first with the simple case – but if Dropbox can handle this more efficiently I will give that a go… Thanks!
Yes, an id or even better a style_class=”link_style” – that way I could use some form of common class across all the link downloads on my site…
For the most part I’m using the shortcode [sdm_hidden_download…]
Thanks!
Respectfully I’m not talking about how PHP streaming works I’m talking about an inconsistent UI issue… either you CAN include %20 characters or you cannot… Your code “converts” spaces to %20 (no problem) but you should therefore also accept them if I type them manually (and convert on the back-end if necessary) OR you should strip and replace them in the UI (so it get’s converted every time).
What you have now however is an inconsistent case of YOU can do it but I cannot and furthermore what you return from the back-end and populate into the text box is not valid and hence breaks my downloads.
Sorry to dredge up an old issue however I’m experiencing this exact problem…
I humbly somewhat disagree with your response/position however.
I DO agree that spaces are invalid in a URL. In fact your own code replaces spaces in a filename with the correct %20 sequence (so “my file.zip” becomes “my%20file.zip”) – no problem so far.
My issue is that if I enter “my%20file.zip” manually, then the plugin seems to strip it out completely! The result becomes “myfile.zip” – yikes!
This is even more problematic because as I mentioned before when I enter “my file.zip” the plugin is smart enough to change it to “my%20file.zip” automagically when I click Update.
However, if I re-edit the download (e.g. change a typo in the description field) then click Update again then the %20 is once again stripped and I end up with “myfile.zip”.
THIS is unexpected behaviour and has been a source of unexpected (and difficult to find) problems.
A simple solution here would be to accept the %20 sequence as part of the filename since it is indeed valid in a URL.
Thanks!
