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 changedwhen upgrading to 4.0.x.James Howarth **********************************Smith Micro, Internet Solutions Div | eCommerce (WebCatalog)16855 West Bernardo Drive | Software & Site DevelopmentSuite 100 |San Diego, CA 92127 |858.675.1106 | http://www.smithmicro.com/isd858.675.0372 (fax)-----Original Message-----From: WebCatalog Talk [mailto:WebDNA-Talk@talk.smithmicro.com]OnBehalf Of Gary KrockoverSent: Wednesday, August 09, 2000 7:09 AMTo: WebCatalog TalkSubject: PROTECT QJust reading Blo's question rose another one that is related. I've alwaysused the syntax [protect group#] where # is a group from 1 to whatever. Ijust looked up what the ver 4.0 syntax is for [PROTECT] and see that it'sgone from [PROTECT group1,group2] to [PROTECT groups=group1,group2]. Mywebhost is getting ready to upgrade to 4.0, and I know that the new syntaxis to comply with XML tags, but how mission critical would you all think itwould be to change that code on all my templates that use it? I know Ipretty much answered my own question, it's going to need to be changed, whatother similar syntax has anyone discovered that may be of issue. I'vefollowed 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 toWeb 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:

Re: PROTECT Q (James Howarth 2000)
PROTECT Q (Gary Krockover 2000)

The old syntax does work. So your templates will not have to be changedwhen upgrading to 4.0.x.James Howarth **********************************Smith Micro, Internet Solutions Div | eCommerce (WebCatalog)16855 West Bernardo Drive | Software & Site DevelopmentSuite 100 |San Diego, CA 92127 |858.675.1106 | http://www.smithmicro.com/isd858.675.0372 (fax)-----Original Message-----From: WebCatalog Talk [mailto:WebDNA-Talk@talk.smithmicro.com]OnBehalf Of Gary KrockoverSent: Wednesday, August 09, 2000 7:09 AMTo: WebCatalog TalkSubject: PROTECT QJust reading Blo's question rose another one that is related. I've alwaysused the syntax [protect group#] where # is a group from 1 to whatever. Ijust looked up what the ver 4.0 syntax is for [protect] and see that it'sgone from [PROTECT group1,group2] to [PROTECT groups=group1,group2]. Mywebhost is getting ready to upgrade to 4.0, and I know that the new syntaxis to comply with XML tags, but how mission critical would you all think itwould be to change that code on all my templates that use it? I know Ipretty much answered my own question, it's going to need to be changed, whatother similar syntax has anyone discovered that may be of issue. I'vefollowed 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 toWeb 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!

Re: PROTECT Q

2000

Top Articles:

Related Readings: