Re: PROTECT Q

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 35971
interpreted = N
texte = The old syntax does work. So your templates will not have to be changed when upgrading to 4.0.x.James Howarth ********************************** Smith Micro, Internet Solutions Div | eCommerce (WebCatalog) 16855 West Bernardo Drive | Software & Site Development Suite 100 | San Diego, CA 92127 | 858.675.1106 | http://www.smithmicro.com/isd 858.675.0372 (fax) -----Original Message----- From: WebCatalog Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of Gary Krockover Sent: Wednesday, August 09, 2000 7:09 AM To: WebCatalog Talk Subject: PROTECT Q Just reading Blo's question rose another one that is related. I've always used the syntax [protect group#] where # is a group from 1 to whatever. I just looked up what the ver 4.0 syntax is for [PROTECT] and see that it's gone from [PROTECT group1,group2] to [PROTECT groups=group1,group2]. My webhost is getting ready to upgrade to 4.0, and I know that the new syntax is to comply with XML tags, but how mission critical would you all think it would be to change that code on all my templates that use it? I know I pretty much answered my own question, it's going to need to be changed, what other similar syntax has anyone discovered that may be of issue. I've followed previous msg's about the [FormVariables] so I'm current on that.Thanks, and sorry for such a long winded question. G.> Hi! > > I'm having a problem with PROTECT; > > in page1.tmpl, I have this: > [PROTECT groups=mygroup] > and a form which posts data to page2.tmpl; > > > in page2.tmpl, I have this: > [PROTECT groups=mygroup] > > When I load page1.tmpl, the authorisation dialog pops up, and I fill it > with the right username and pass; > > when i push the submit button in page1, the [PROTECT groups=mygroup] of > page 2 asks me again username and password; > AND, whatever I type, it returns me Not Authorized!; > > then, if a do a reload in my browser, I get the authorisation dialog, > fill it, and receive access to page 2 (which is not very useful, as the > forms variable of page1 are lost...) > > what could cause the authorisation dialog to come twice? > and why does it sometimes accept my user+pass and sometimes not? > > (9650, MacOS 8.6, Wcat 3.0.1, Web* 3.0.2, IE 5.0) > > thanx in advance :->------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: PROTECT Q (James Howarth 2000)
  2. PROTECT Q (Gary Krockover 2000)
The old syntax does work. So your templates will not have to be changed when upgrading to 4.0.x.James Howarth ********************************** Smith Micro, Internet Solutions Div | eCommerce (WebCatalog) 16855 West Bernardo Drive | Software & Site Development Suite 100 | San Diego, CA 92127 | 858.675.1106 | http://www.smithmicro.com/isd 858.675.0372 (fax) -----Original Message----- From: WebCatalog Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of Gary Krockover Sent: Wednesday, August 09, 2000 7:09 AM To: WebCatalog Talk Subject: PROTECT Q Just reading Blo's question rose another one that is related. I've always used the syntax [protect group#] where # is a group from 1 to whatever. I just looked up what the ver 4.0 syntax is for [protect] and see that it's gone from [PROTECT group1,group2] to [PROTECT groups=group1,group2]. My webhost is getting ready to upgrade to 4.0, and I know that the new syntax is to comply with XML tags, but how mission critical would you all think it would be to change that code on all my templates that use it? I know I pretty much answered my own question, it's going to need to be changed, what other similar syntax has anyone discovered that may be of issue. I've followed previous msg's about the [formvariables] so I'm current on that.Thanks, and sorry for such a long winded question. G.> Hi! > > I'm having a problem with PROTECT; > > in page1.tmpl, I have this: > [PROTECT groups=mygroup] > and a form which posts data to page2.tmpl; > > > in page2.tmpl, I have this: > [PROTECT groups=mygroup] > > When I load page1.tmpl, the authorisation dialog pops up, and I fill it > with the right username and pass; > > when i push the submit button in page1, the [PROTECT groups=mygroup] of > page 2 asks me again username and password; > AND, whatever I type, it returns me Not Authorized!; > > then, if a do a reload in my browser, I get the authorisation dialog, > fill it, and receive access to page 2 (which is not very useful, as the > forms variable of page1 are lost...) > > what could cause the authorisation dialog to come twice? > and why does it sometimes accept my user+pass and sometimes not? > > (9650, MacOS 8.6, Wcat 3.0.1, Web* 3.0.2, IE 5.0) > > thanx in advance :->------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ James Howarth

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:

Weird problems with [SHOWIF]s (1997) Bulk capture for Authorize.net (2004) Country & Ship-to address & other fields ? (1997) Add - optional parameters textA=.... (1997) Big Databases (1997) Close-to Comparison Code (1998) Can a database get stomped by simultaneous access? (1997) Saving Text Areas with Orders (1997) Include a big block of text (1997) Request: Stop any looping context ... (2002) Erotic Sites (1997) [dos] command and [math] (1998) Product Name in AdminResults.inc (2001) Closing Databases (1998) Date Time Oddness (1999) Help with Grep exchange (2005) WebCat2 several catalogs? (1997) Troubles with Selection Drop Down List Search (1998) WC2.0 Memory Requirements (1997) WebCat2 - [format thousands] (1997)