Re: [protect admin]
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 12335
interpreted = N
texte = >Currently using the 2.of3 acgi from the cgi-bin. >The cgi-bin folder contains the webcat .pref file & users.db file. > >It was my understanding that placing [protect admin] would call a usr/pass >box for entry. > >This was to provide username password protection to .tmpl file. > >WRONG!!!! I can log into my site and access a .tmpl file that has [protect >admin] directly. And yes I restarted netscape prior to logon. > >WebCat is doing NO protection of any kind for me. What's Up????You moved the users.db file out of the WebCatalog folder, so WebCatalog cannot find it, so it cannot 'protect' your pages.If you plan to use the [protect] tag, you have to leave things where they were when you downloaded the WbeCatalog package. The path to the users.db file is hard-coded into the software, so you cannot move the users.db and expect to use [protect].Of course, if you want to write your own WebDNA to do the same kind of thing [protect] does, then you can move the users.db file wherever you please - you just won't be able to use the [protect] tag, instead you'll have to use your own custom-coded replacement [include] tags and related files.I've 'been there, done that' ... and I've learned that life's a lot easier when you don't move some things around unless it's absolutely necessary ... :)Sincerely, Ken Grome WebDNA Solutions
Associated Messages, from the most recent to the oldest:
>Currently using the 2.of3 acgi from the cgi-bin. >The cgi-bin folder contains the webcat .pref file & users.db file. > >It was my understanding that placing [protect admin] would call a usr/pass >box for entry. > >This was to provide username password protection to .tmpl file. > >WRONG!!!! I can log into my site and access a .tmpl file that has [protect >admin] directly. And yes I restarted netscape prior to logon. > >WebCat is doing NO protection of any kind for me. What's Up????You moved the users.db file out of the WebCatalog folder, so WebCatalog cannot find it, so it cannot 'protect' your pages.If you plan to use the
[protect] tag, you have to leave things where they were when you downloaded the WbeCatalog package. The path to the users.db file is hard-coded into the software, so you cannot move the users.db and expect to use
[protect].Of course, if you want to write your own WebDNA to do the same kind of thing
[protect] does, then you can move the users.db file wherever you please - you just won't be able to use the
[protect] tag, instead you'll have to use your own custom-coded replacement
[include] tags and related files.I've 'been there, done that' ... and I've learned that life's a lot easier when you don't move some things around unless it's absolutely necessary ... :)Sincerely, Ken Grome WebDNA Solutions
Kenneth Grome
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
PCS Customer submissions ? (1997)
Bug Report, maybe (1997)
WebMerchant 1.6 and SHTML (1997)
Version 2.1.3 changes ... (1998)
Secure Server (1997)
Frames and WebCat (1997)
[ShowNext] (1997)
New Site Announcement (1998)
Cookies (1999)
Running WebCat from a CD-ROM (1997)
[Sum] function? (1997)
Cookie woes with Mac IE4 (1998)
Frames and WebCat (1997)
Web Logs (1998)
Sku numbers (1997)
SMSI FTP - calander system (2002)
Running 2 two WebCatalog.acgi's (1996)
Some Advise needed (1997)
RE: SSL and WebCatalog (1997)
Re:upgrade problem with users.db (1998)