On Jun 14, 2010, at 9:52 AM, Dirk wrote:
Thanks, LLE and Walter for the quick replies.
Walter, did I understand you correctly that I would simply create
another “web site” using the same layout in Freeway for the “secure
portion” so that any moving between the (effectively two) sites is
seamless? I would then just protect the secure portion via FatCow
and jump back and forth depending on what I click on the menu? If
so, I have two questions:
You would create two different Freeway documents (visually the same,
if the secure area is to look identical to the public area) that
publish into the same Web server. The secure document would publish
into a subfolder where you had used the control panel to require user/
password. The other document would publish into the parent folder
(probably the Web root) and would provide the public part of the site.
(1) I would require a menu spanning both sections of the overall
website: the public and the secure portion. Am I to expect problems
here? Anything to watch out for? I assume that the link to the
secure portion would just be an external link from the public
portion and vice versa, right?
All you would need to do in order to link into the private area is to
use the External Link portion of the Hyperlink dialog. If you wanted
to link to the home page of the private area, for example, you would
private_folder_name/index.html in the URL field. To link
out to the public site from a private page, you would enter:
../ index.html to move up a directory level and select the index page. If
you want a direct link to a different page, then you would simply note
that page’s filename and make your link as
(2) How would I create a Freeway page with form asking for user ID
and password that follows my design rather than uses what FatCow
provides - or did I misunderstand something?
You can’t design the form the user will see when you use Basic
Authentication or Digest Authentication (the two kinds of security you
can apply to folders using a control panel on the server). The
individual browsers create that dialog as a popup dialog or slide-down
sheet, and it will look different depending on the browser and the
If you want to have a designed login experience, you will need to use
an authentication system programmed in a scripting language like PHP
or Ruby or Perl. These usually look up users against a MySQL database.
Further on up the food chain from that is an authentication and
authorization system, which maps individual users into classes of
actions those users may perform, allowing some users to administer
other users, some users to only log in and see private content, other
users to create but not publish private content, etc.
This is a whole other kettle of fish, and can get extremely complex
very quickly, so you really need to start from the basics – what do
you need to hide, and from whom? Answer that question, and your
problem is half-solved.
freewaytalk mailing list
Update your subscriptions at: