Re: when is failing to [URL]ize values in a comparison risky?

This WebDNA talk-list message is from

1999


It keeps the original formatting.
numero = 25328
interpreted = N
texte = It is always safe to URL'ize both sides of a equality comparison, as far as I know. I have started always doing that (when I can remember), except where I am typing all data myself. I think that it would be appropriate for PCS to always URL'ize ShowIf and HideIf comparisons. I cannot think of a single instance where it would not be correct. The only enhancement I can think of is some way to force a numeric comparison (stripping any non-numeric characters before testing).HTHJohn Peacock ____________________Reply Separator____________________ Subject: when is failing to [URL]ize values in a comparison risky? Author: (WebCatalog Talk) Date: 12/9/99 11:38 AMLinux RedHat 6 webcat 3.xI have this code on my shoppingcart.tmpl-[showif [Header10]=yes][Header11], you ... [/showif]sometimes there will be no value for [Header11], sometimes it will equal yes. I haven't narrowed it down to be sure, but I think webcat is crashing on reaching this page every time. The above line of code is the only thing I have changed since the page used to work fine... (though it was on a mac server before that line got added and the crashes started... but I assume the crashes would have happened on the mac before if some other code on the page is the culprit.) I remember a couple weeks ago a discussion on blank values in a comparison like [showif] can cause crashes... Can someone define when one side or the other *must* be wrapped in an [URL] context to prevent crashes (if this is even a valid statement) ??like so-[showif [URL][Header10][/URL]=yes][Header11], you ... [/showif]?-John ------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .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: when is failing to [URL]ize values in a comparison risky? (John Butler 1999)
  2. Re: when is failing to [URL]ize values in a comparison risky? (Kenneth Grome 1999)
  3. Re: when is failing to [URL]ize values in a comparison risky? (John Butler 1999)
  4. Re: when is failing to [URL]ize values in a comparison risky? (Kenneth Grome 1999)
  5. Re: when is failing to [URL]ize values in a comparison risky? (John Butler 1999)
  6. Re: when is failing to [URL]ize values in a comparison risky? (jpeacock@univpress.com 1999)
  7. when is failing to [URL]ize values in a comparison risky? (John Butler 1999)
  8. when is failing to [URL]ize values in a comparison risky? (John Butler 1999)
It is always safe to URL'ize both sides of a equality comparison, as far as I know. I have started always doing that (when I can remember), except where I am typing all data myself. I think that it would be appropriate for PCS to always URL'ize ShowIf and HideIf comparisons. I cannot think of a single instance where it would not be correct. The only enhancement I can think of is some way to force a numeric comparison (stripping any non-numeric characters before testing).HTHJohn Peacock ____________________Reply Separator____________________ Subject: when is failing to [url]ize values in a comparison risky? Author: (WebCatalog Talk) Date: 12/9/99 11:38 AMLinux RedHat 6 webcat 3.xI have this code on my shoppingcart.tmpl-[showif [Header10]=yes][Header11], you ... [/showif]sometimes there will be no value for [Header11], sometimes it will equal yes. I haven't narrowed it down to be sure, but I think webcat is crashing on reaching this page every time. The above line of code is the only thing I have changed since the page used to work fine... (though it was on a mac server before that line got added and the crashes started... but I assume the crashes would have happened on the mac before if some other code on the page is the culprit.) I remember a couple weeks ago a discussion on blank values in a comparison like [showif] can cause crashes... Can someone define when one side or the other *must* be wrapped in an [url] context to prevent crashes (if this is even a valid statement) ??like so-[showif [url][Header10][/URL]=yes][Header11], you ... [/showif]?-John ------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .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 jpeacock@univpress.com

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:

Introduction/Tutorial/QuickStart (1997) WebTen and WebCat (1997) can WC render sites out? (1997) Web Catalog vs. ICAT (1997) Fun with Dates - finally resolved but.... (1997) [WebDNA] WebDNA future (2010) Suggestions for Topics to be covered in an Advanced WebDNACourse... (1998) b12 cannot limit records returned and more. (1997) RequiredFields template (1997) [quantity] - spoke too soon (1997) Thanks ! (1997) [cart] how is it generated (2002) RE: type 2 errors with ssl server (1997) WebCat2 Append problem (B14Macacgi) (1997) Only charge card when product shipped ? (1997) Price Not Appearing (2000) Signal Raised (1997) Permissions / Restart WebDNA? (2005) AOL refuses some e-mails (2000) Multi-processor Mac info ... (1997)