How can I create a section of my site which is password protected?
Regards
Chris
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
The easiest way of all is to use your hosting provider’s control panel to create a “secure folder” or whatever they call it in the local language. This is often as simple as creating a folder (using an FTP application) in your Web root, selecting that folder in the control panel, and setting up users who can access it. See if there’s something like that available to you. If your hosting provider doesn’t have this feature, file a support ticket with their help desk and ask them to add an ‘.htaccess/.htpasswd’ secured realm.
This will get you one or more user/password combos that can access this folder. In Freeway, just add a folder in the Site panel, and start creating (or moving) your pages into that folder. When you upload, these secure pages will pop into the secure folder on your server. Anyone who tries to enter that folder will see a browser popup requesting a Username and Password.
Walter
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Looking at this one with interest Walt, and sorry to hijack it, but I
think I’m missing something here.
So you have your folder on the server called, for example, “secure
folder”. In Freeway would you name the folder you make the same name
and the enclosed pages automatically go into the correct place when
uploaded?
Basically, how would Freeway know that the folder you create within
the programme was the password protected one?
Trev
On 5 Mar 2009, at 17:54, waltd wrote:
The easiest way of all is to use your hosting provider’s control
panel to create a “secure folder” or whatever they call it in the
local language. This is often as simple as creating a folder (using
an FTP application) in your Web root, selecting that folder in the
control panel, and setting up users who can access it. See if
there’s something like that available to you. If your hosting
provider doesn’t have this feature, file a support ticket with their
help desk and ask them to add an ‘.htaccess/.htpasswd’ secured realm.This will get you one or more user/password combos that can access
this folder. In Freeway, just add a folder in the Site panel, and
start creating (or moving) your pages into that folder. When you
upload, these secure pages will pop into the secure folder on your
server. Anyone who tries to enter that folder will see a browser
popup requesting a Username and Password.Walter
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Let’s say you have a single Freeway document that you use to manage your entire Web site. You have set it to publish into the folder your hosting provider has defined as your Site Root, so that your home page (index.html) is the automatic choice when people simply enter your domain without any folder or filename trailing that.
In Freeway, the list of files and folders you see in the Site pane mirrors the contents of your site root. (It’s not a perfect copy – Freeway is not ‘reading’ the contents of that folder – it’s just listing the things it knows about in that folder, and ignoring the rest.)
If you create a folder in Freeway named ‘private’, put some pages in it, and upload to your server, that folder will be created if it didn’t already exist. If that folder already existed on the server, Freeway would skip creating it and would simply publish the files into the folder.
So if you have created your private folder first using your hosting provider’s control panel or an FTP application, then Freeway will publish its files into that folder. If that folder also contains an .htaccess/.htpasswd file combo, then the server will (if it’s properly configured) limit access to the contents of that folder.
There’s one thing you have to look out for, and that’s shared resources. Freeway is always looking to optimize the content of the site folder. If an image is used in exactly the same size on more than one page, only one copy of that image will be created and referenced throughout the site. You don’t have control over where this will be stored, and I can imagine a case where you have a public page containing images referenced from the Resources folder within the private folder. If that happens, the user will either see a request for authentication, or the image won’t appear – not sure which will happen.
One way around this problem is to select Single Resources Folder in the Document Setup. Another is to have a separate Freeway document that you use only to publish your private file, and you set that to have it’s server root within the private folder. That way it doesn’t know about anything above that level – like your public pages – and doesn’t mix up the secure and public content.
Walter
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Thanks Walter, that makes perfect sense now.
Trev
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options