Re: Re[3]: Problem with new formvariables

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 31212
interpreted = N
texte = > The more I think about it, the less I like the idea of a system > option that > turns off the secure mode of operation. With that in place, no one who > currently uses this feature will stop using it, so the same > people will bitch > and moan when WebCat5 comes out! And I dislike having the new tags use a > version specific flag, because it is just asking for trouble for the next > version.Why can't we just use [text &secure=f] seems so simple to me? it's not version specific as it would work for the issues they are talking about. Jesse Proudman - NineWire Productions http://www.ninewire.com <-> jesse@ninewire.com Innovative and Creative Web Design and Hosting############################################################# 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 To switch to the INDEX mode, E-mail to Send administrative queries to Associated Messages, from the most recent to the oldest:

    
  1. Re[3]: Re[3]: Problem with new formvariables (jpeacock@univpress.com 2000)
  2. Re[2]: Re[3]: Problem with new formvariables (jpeacock@univpress.com 2000)
  3. Re[2]: Re[3]: Problem with new formvariables (jpeacock@univpress.com 2000)
  4. Re: Re[2]: Re[3]: Problem with new formvariables (Jesse Proudman 2000)
  5. Re: Re[3]: Problem with new formvariables (Mike Davis 2000)
  6. Re: Re[3]: Problem with new formvariables (Jesse Proudman 2000)
  7. Re: Re[3]: Problem with new formvariables (Nicolas Verhaeghe 2000)
  8. Re: Re[3]: Problem with new formvariables (Jesse Proudman 2000)
  9. Re: Re[3]: Problem with new formvariables (Nicolas Verhaeghe 2000)
  10. Re[3]: Problem with new formvariables (jpeacock@univpress.com 2000)
> The more I think about it, the less I like the idea of a system > option that > turns off the secure mode of operation. With that in place, no one who > currently uses this feature will stop using it, so the same > people will bitch > and moan when WebCat5 comes out! And I dislike having the new tags use a > version specific flag, because it is just asking for trouble for the next > version.Why can't we just use [text &secure=f] seems so simple to me? it's not version specific as it would work for the issues they are talking about. Jesse Proudman - NineWire Productions http://www.ninewire.com <-> jesse@ninewire.com Innovative and Creative Web Design and Hosting############################################################# 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 To switch to the INDEX mode, E-mail to Send administrative queries to Jesse Proudman

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:

Re:PCS Customer submissions ? (1997) Nested tags count question (1997) Limiting user access to .tmpl files (1997) WebCat2b13 Command Reference Doc error (1997) WebCat2b12 CGI Mac -- Problems propagating the cart through (1997) Frames and [cart] (1998) WebCat2 - Getting to the browser's username/password data (1997) Problems getting parameters passed into email. (1997) Wanted: G5 apple xserve (2007) WebCatalog vs WebDNA (2002) [WriteFile] problems (1997) cart info (1998) system crashes, event log (1997) Which beta for w* 4.1 and a problem w/b12 (1999) Date Bug (1998) Erotic Sites (1997) WebCat2b13MacPlugIn - [include] doesn't allow creator (1997) Tax and Shipping Examples (1997) UPS Rate Tables (2002) searching by date (1998)