numero = 61895
interpreted = N
texte = Hi Ken, Correct, my mistake - it's not the landing page on forms but when recalling a pre-populated form, such as in the case where the visitor missed a required field and I've redirected them back to the form while checking for existing values in a custom "required fields" situation. Example, visitor fills in form, that appends to a db but they missed a field. I redirect them back to the form and repopulate the form from what they did fill in. One of the fields: That just seems to be too much. But yes, I've tried the [url][field][/url]=] route, and it wont catch it if the field equals [field]. Example: [showif [didsubmit]=T] [text show=f]thefield=[raw][thefield][/raw][/text] [showif [url][thefield][/url]=]It equals nothing[/showif] [showif [thefield]=[raw][thefield][/raw]]It equals the field name[/showif] [showif =[thefield]] .... this is shown when [fieldname] is blank ... [/showif] [/showif] Now, this is probably an error with my coding on the original form. I could (should?) on the append, check to see if a field was populated and if not then zero it out fully, but I'm still checking to see if it equals [raw][field][/raw], either there or when repopulating the form. But ugh, it's too late on a Sunday night to worry with this now. :) GJK At 08:40 PM 5/1/2005, you wrote: >I wonder why you're not avoiding the use of raw contexts by using this >technique instead: > >[showif [url][field][/url]=] >... this is shown when [fieldname] is blank ... >[/showif] > >Of course you should be [url]ing your [field] value as in this example -- >to prevent any comparison operators from screwing up your showif >comparisons. By the way, when I know that the visitor cannot enter an >ending webdna bracket (which would become part of the [field] value) I >sometimes use this technique because it's even more efficient: > >[showif =[field]] >... this is shown when [fieldname] is blank ... >[/showif] > >This works when the the [field] value does NOT have an ending bracket in >it, such as in fields that are not editable by the visitor -- hidden, >radio, checkbox and select -- assuming you do not put the ending bracket >in one of these field values yourself! > >The bottom line is that I haven't used raw contexts for this purpose in >years ... not that it doesn't work but it seems there are more efficient >coding techniques to use in this case. > >But I actually think you've confused the place where you're using [raw] >contexts anyways. Aren't you actually using them in your edit forms, and >not on the pages that follow your form submissions? The reason I ask is >because the [field] values in the page after the form submission are >always going to have values, even if they are [blank] values. > >In other words, putting a [fieldname] tag on this page is never going to >result in the raw [field] tag being displayed because that form field will >always have a value that's set in the form, even if that value is blank -- >unless it's a checkbox field that was not checked of course, because >that's the only HTML form that does NOT get passed as a name-value pair in >a form submission. > >Sincerely, >Kenneth Grome >www.kengrome.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://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Hi Ken, Correct, my mistake - it's not the landing page on forms but when recalling a pre-populated form, such as in the case where the visitor missed a required field and I've redirected them back to the form while checking for existing values in a custom "required fields" situation. Example, visitor fills in form, that appends to a db but they missed a field. I redirect them back to the form and repopulate the form from what they did fill in. One of the fields: [input][showif [CVV2]!][showif [CVV2]![raw][CVV2][/raw]][CVV2][/showif][/showif][/input]" size="5" maxlength="3"> That just seems to be too much. But yes, I've tried the [url][field][/url]=] route, and it wont catch it if the field equals [field]. Example: [showif [didsubmit]=T] [text show=f]thefield=[raw][thefield][/raw][/text] [showif [url][thefield][/url]=]It equals nothing[/showif] [showif [thefield]=[raw][thefield][/raw]]It equals the field name[/showif] [showif =[thefield]] .... this is shown when [fieldname] is blank ... [/showif] [/showif] Now, this is probably an error with my coding on the original form. I could (should?) on the append, check to see if a field was populated and if not then zero it out fully, but I'm still checking to see if it equals [raw][field][/raw], either there or when repopulating the form. But ugh, it's too late on a Sunday night to worry with this now. :) GJK At 08:40 PM 5/1/2005, you wrote: >I wonder why you're not avoiding the use of raw contexts by using this >technique instead: > >[showif [url][field][/url]=] >... this is shown when [fieldname] is blank ... >[/showif] > >Of course you should be [url]ing your [field] value as in this example -- >to prevent any comparison operators from screwing up your showif >comparisons. By the way, when I know that the visitor cannot enter an >ending webdna bracket (which would become part of the [field] value) I >sometimes use this technique because it's even more efficient: > >[showif =[field]] >... this is shown when [fieldname] is blank ... >[/showif] > >This works when the the [field] value does NOT have an ending bracket in >it, such as in fields that are not editable by the visitor -- hidden, >radio, checkbox and select -- assuming you do not put the ending bracket >in one of these field values yourself! > >The bottom line is that I haven't used raw contexts for this purpose in >years ... not that it doesn't work but it seems there are more efficient >coding techniques to use in this case. > >But I actually think you've confused the place where you're using [raw] >contexts anyways. Aren't you actually using them in your edit forms, and >not on the pages that follow your form submissions? The reason I ask is >because the [field] values in the page after the form submission are >always going to have values, even if they are [blank] values. > >In other words, putting a [fieldname] tag on this page is never going to >result in the raw [field] tag being displayed because that form field will >always have a value that's set in the form, even if that value is blank -- >unless it's a checkbox field that was not checked of course, because >that's the only HTML form that does NOT get passed as a name-value pair in >a form submission. > >Sincerely, >Kenneth Grome >www.kengrome.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://webdna.smithmicro.com/
Gary Krockover
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...