numero = 24861
interpreted = N
texte = Sunday warriors-I have a form that lets the admin person create products (including fields for the product that may contain all kinds of illegal chars). The inputted values get into the product db. When the admin wishes to tweak something about that product, then she goes back to the same form which does a [search][founditems] to load the db field values into the values of the form variables. And I am not yet able to maintain the quot character (or anything past it in an inputted value).Here's an example-1) She first creates the product, inputting '8"' to designate 8 inches for the dimensions field for that product. That gets into the db as '8"'.2) When she revisits the same HTML form to tweak something, then it loads '8' (the number 8 followed by a single quote mark) into the value of the dimensions text input (that's proper HTML syntax). Upon submitting the from this second time, the value '8' gets into the db.3) When she revisits the same form again, then it loads '8' (the number 8 alone) into the value of the dimensions text input (the quote mark designates the end of the value). Upon submitting the from this third time, the value '8' gets into the db. So we have completely lost the inches. It could be 8 meters for all we know. If I [URL]ize [dimensions] in the [replace append=T] context, then the originally inputted '"' gets into the db as '"' (so far so good), but displays in the HTML form (next time she goes to it) as just a quote mark (). and we are back into the problem loop at step # 2 above.If I also [URL]ize the value for dimensions in the HTML form (like this - then '8"' gets into the db as '8"' like I want, but displays in the HTML form as '8%26quot%3B'. This is no good because upon the next round trip the value would be '8%2526quot%253B'. ad infinitum.With textareas, one doesn't have this problem since the quote is not used to deliminate the textarea value, but how are you all getting quote marks into your regular text inputs?-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:
Sunday warriors-I have a form that lets the admin person create products (including fields for the product that may contain all kinds of illegal chars). The inputted values get into the product db. When the admin wishes to tweak something about that product, then she goes back to the same form which does a [search][founditems] to load the db field values into the values of the form variables. And I am not yet able to maintain the quot character (or anything past it in an inputted value).Here's an example-1) She first creates the product, inputting '8"' to designate 8 inches for the dimensions field for that product. That gets into the db as '8"'.2) When she revisits the same HTML form to tweak something, then it loads '8' (the number 8 followed by a single quote mark) into the value of the dimensions text input (that's proper HTML syntax). Upon submitting the from this second time, the value '8' gets into the db.3) When she revisits the same form again, then it loads '8' (the number 8 alone) into the value of the dimensions text input (the quote mark designates the end of the value). Upon submitting the from this third time, the value '8' gets into the db. So we have completely lost the inches. It could be 8 meters for all we know. If I [url]ize [dimensions] in the [replace append=T] context, then the originally inputted '"' gets into the db as '"' (so far so good), but displays in the HTML form (next time she goes to it) as just a quote mark (). and we are back into the problem loop at step # 2 above.If I also [url]ize the value for dimensions in the HTML form (like this - [url][Title][/URL]> then '8"' gets into the db as '8"' like I want, but displays in the HTML form as '8%26quot%3B'. This is no good because upon the next round trip the value would be '8%2526quot%253B'. ad infinitum.With textareas, one doesn't have this problem since the quote is not used to deliminate the textarea value, but how are you all getting quote marks into your regular text inputs?-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 John Butler
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...