Re: locking variables?

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 28877
interpreted = N
texte = >> You can use [FormVariables] at the top of the page to examine which >> variables are being overridden by the incoming GET, and put up an >> error message or redirect back to the same page without those >> particular form variables. We realize the current behavior is not >> optimal, and we're revisiting it for 4.0. > >If you guys have this already coded for 3.x, why not post it? >This is just one more example of the poor support for the product you >advertise as premier.Hey, they do NOT have any obligation to write YOUR webdna code for you! That's not what support is about! If you're too lazy to do it yourself, then ask nicely for someone else to give you an example instead of being a jerk about it.What seems to be your problem anyways?They suggested you use the formvariable technique so you could see which variables have fixed values on the page. The reason is simple -- so you would not be tempted to set new text or math variables with the same names on that page.If you want some kind of error-handling code, you have to write it yourself -- that's why they made the webdna language so powerful in the first place, so you can do things yourself!There is nothing wrong with the way webcatalog works. If you don't understand it, then read the manual and the docs, or ask polite questions, instead of accusing SM of poor tech support. Their support has improved noticeably during the past month or so -- but they still have no obligation to do your work for you.================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================------------------------------------------------------------- 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 Associated Messages, from the most recent to the oldest:

    
  1. Re: locking variables? (Kenneth Grome 2000)
  2. Re: locking variables? (Charles Kline 2000)
  3. Re: locking variables? (WebDNA Support 2000)
  4. Re: locking variables? (Glenn Busbin 2000)
  5. Re: locking variables? (Charles Kline 2000)
  6. Re: locking variables? (Jereme Claussen 2000)
  7. Re: locking variables? (Glenn Busbin 2000)
  8. Re: locking variables? (Kenneth Grome 2000)
  9. Re: locking variables? (Kenneth Grome 2000)
  10. Re: locking variables? (WebDNA Support 2000)
  11. Re: locking variables? (Jereme Claussen 2000)
  12. Re: locking variables? (Kenneth Grome 2000)
  13. Re: locking variables? (John Butler 2000)
  14. Re: locking variables? (WebDNA Support 2000)
  15. Re: locking variables? (Kenneth Grome 2000)
  16. locking variables? (Jereme Claussen 2000)
>> You can use [formvariables] at the top of the page to examine which >> variables are being overridden by the incoming GET, and put up an >> error message or redirect back to the same page without those >> particular form variables. We realize the current behavior is not >> optimal, and we're revisiting it for 4.0. > >If you guys have this already coded for 3.x, why not post it? >This is just one more example of the poor support for the product you >advertise as premier.Hey, they do NOT have any obligation to write YOUR webdna code for you! That's not what support is about! If you're too lazy to do it yourself, then ask nicely for someone else to give you an example instead of being a jerk about it.What seems to be your problem anyways?They suggested you use the formvariable technique so you could see which variables have fixed values on the page. The reason is simple -- so you would not be tempted to set new text or math variables with the same names on that page.If you want some kind of error-handling code, you have to write it yourself -- that's why they made the webdna language so powerful in the first place, so you can do things yourself!There is nothing wrong with the way webcatalog works. If you don't understand it, then read the manual and the docs, or ask polite questions, instead of accusing SM of poor tech support. Their support has improved noticeably during the past month or so -- but they still have no obligation to do your work for you.================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================------------------------------------------------------------- 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 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:

[WebDNA] Digest (2008) Emailer (1997) Retrieve deleted files (2001) [WebDNA] New Site (2010) Server Error Question (2004) Undeliverable Mail (1997) 6.0 Upgrade Issue (2005) WebCommerce: Folder organization ? (1997) Modifying order output (1997) Country & Ship-to address & other fields ? (1997) emailer (1997) Sendmail reply-to header? (2001) Problems passing [SKU] with $Replace in 2.0 (1997) [WebDNA] Need to convert unix date? (2009) Not really WebCat (1997) Getting Emailer to send mail (1997) WebCat2b13MacPlugin - nested [xxx] contexts (1997) Hyperlink in email (2002) C is for cookie - that's good enough for me... (2001) Nesting Search Within Tag? (1997)