Because the force download php does not give you the possibility to go down to my host via internet. You can only select a “filename” without the path from whatever computer you have !! So basically only files on your own computer.
On 5 Jan 2013, 10:22 pm, DeltaDave wrote:
DeltaDave you are from Clydebank ?
No - Bearsden
I dont see why you shouldn’t be able to use Force Download in a protected directory but because of iMac issues I cannot test it.
I would link to a page in a protected folder and on that page have a link to the file using Force Download.
Just to add to this and possibly clear up any confusion.
If you have created a protected directory on your server called ‘protected’ if you then create a sub folder in your FW doc with the same name (making sure that the name is exactly the same - case sensitive) then any pages you create in that FW sub folder will be uploaded to the corresponding ‘protected’ folder on the server as will any files (like your PDFs)
If you upload a project from FW, the resources directory, CSS directory and HTML files are uploaded to the ROOT directory of the host server not any other directories at least not in my version of Freeway, which is the most recent one (version 5.6.5 (6418)).
sorry but it does not work like this. If you create an exactly the same protected directory (with the same content) in your FW project on your HD of your computer as on the host server than the forced download will not ask for the password of the protected directory anymore !!! I agreee it is strange but that is the how it works.
If you create an exactly the same protected directory (with the same content) in your FW project on your HD of your computer as on the host server than the forced download will not ask for the password of the protected directory anymore
You also have to remember that if you revisit a protected folder in the same browsing session then you will not be asked for the user/pass again.
If you quit the browser and then revisit the folder you will then be asked for the user/pass again (or use a different browser)
The Force Download action puts the the file to be downloaded alongside the html page it is applied to so if that page is within the protected folder the file will also be protected.
Yes I have done this all but the protection is gone, even after deleting all saved passwords, emptying the cache memory and closing the browser and restart it. The protection is GONE !!!
Yes I saw at works at your site. Ok I will fiddle a bit more. I am probably doing something wrong. I see at my host that the directory is protected. I than copy the file into it and than I download the protected directory into my FW project. Than I open the FW project and make the link with the file in the protected directory. As last step I upload the whole FW project to the server. Note that the protected directory in my FW project located in the resources directory does not upload to the server. I have to to this manually with FTP. This way when I click on the link the file is downloaded and opened. Unfortunately no password is asked !!!
As I said before once the folder has been created on the server and the protection set then you create a sub folder within your FW document with the same name.
When you upload (using FW) because there is a folder on the server already then only the contents of that folder are uploaded.
This would be no different if you used FTP to transfer the contents of the folder.
It does work with Force Download action, as I do it on a clients site (with PDFs). I did notice however it played up when I was setting it up and THINK I resolved it by having no spaces in the PDF file names.
It does work with Force Download action, as I do it on a clients site (with PDFs). I did notice however it played up when I was setting it up and THINK I resolved it by having no spaces in the PDF file names.
That is something that I bang on about frequently -
Correct File/Folder naming
No spaces or otherwise dodgy characters in file/folder names. Stick to Alphanumerics (A-Z, a-z, 0-9) _underscores and -hyphens and you won’t go wrong. Other punctuation should be avoided.