Re: Incorrect Value Display

This WebDNA talk-list message is from

2000

It keeps the original formatting. numero = 34596
interpreted = N
texte = >>When adding sizes to a db, I'm required to enter the inch symbol ( >>). The record goes into the db without any problems. The record also>>displays without any problems.>>>>I have set up an admin page for this db. When a record is pulled up>>to be modified, the inch symbol and everything thereafter have>>disappeared from the form field.>>>>Example: >>As always, wrap [url] around fields you want to put into a

value field.>>This is just plain WRONG!If you do what Tech Support suggests here, you won't even see a quote in the form field, you will see %22 where you SHOULD be seeing a double quote. This is the worst advice given by Tech Support in a long time ... :(You should *never* use the url context in a form field! Instead you should be putting the url context around your parameter values when appending or replacing them to the database, and if anything you should be using the [input] context around your form values!Here is the CORRECT step-by-step way to do it is this. It's pretty simple, considering the fact that there are only two steps to remember:1- Wrap an url context around every one of your parameter values, in all your append and replace contexts. Just make a habut if it and do it -- every time, no exceptions.Reason:This insures that quotes and other non-alphanumeric characters that you're trying to store in the db are pre-urled before being appended to the db. Webcat unurls them as they are appended to the db anyways, which is why you should use the url context to pre-url them. Webcat's behind the scenes unurling of these values as they are appended to the db is also why quotes and other non-alphanumeric characters actually appear in the database as the original characters -- instead of as urled characters.2- Use the [input] context around the values in your form fields:Reason:If soft returns exist in the db field, the input context changes them into hard returns so they will display properly in a textarea field. It also allows *all* the text in a db field to be displayed in a regular text field if that data happens to have soft returns, such as if that data were originally entered via cut and paste, or if originally entered via a textarea field. The [input] context only affects the specific characters it has to deal with -- which means it makes sense to use it in all form fields that display text.================================Kenneth Grome, WebDNA Consultant808-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 Web Archive of this list is at: http://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

Re: Incorrect Value Display (John Peacock 2000)
Re: Incorrect Value Display (John Butler 2000)
Re: Incorrect Value Display (John Butler 2000)
Re: Incorrect Value Display (Kenneth Grome 2000)
Re: Incorrect Value Display (WebDNA Support 2000)
Re: Incorrect Value Display (John Peacock 2000)
Incorrect Value Display (Clint Davis 2000)

>>When adding sizes to a db, I'm required to enter the inch symbol ( >>). The record goes into the db without any problems. The record also>>displays without any problems.>>>>I have set up an admin page for this db. When a record is pulled up>>to be modified, the inch symbol and everything thereafter have>>disappeared from the form field.>>>>Example: >>As always, wrap [url] around fields you want to put into a value field.>>[url][size][/url]>This is just plain WRONG!If you do what Tech Support suggests here, you won't even see a quote in the form field, you will see %22 where you SHOULD be seeing a double quote. This is the worst advice given by Tech Support in a long time ... :(You should *never* use the url context in a form field! Instead you should be putting the url context around your parameter values when appending or replacing them to the database, and if anything you should be using the [input] context around your form values!Here is the CORRECT step-by-step way to do it is this. It's pretty simple, considering the fact that there are only two steps to remember:1- Wrap an url context around every one of your parameter values, in all your append and replace contexts. Just make a habut if it and do it -- every time, no exceptions.Reason:This insures that quotes and other non-alphanumeric characters that you're trying to store in the db are pre-urled before being appended to the db. Webcat unurls them as they are appended to the db anyways, which is why you should use the url context to pre-url them. Webcat's behind the scenes unurling of these values as they are appended to the db is also why quotes and other non-alphanumeric characters actually appear in the database as the original characters -- instead of as urled characters.2- Use the [input] context around the values in your form fields:[input][size][/input]>Reason:If soft returns exist in the db field, the input context changes them into hard returns so they will display properly in a textarea field. It also allows *all* the text in a db field to be displayed in a regular text field if that data happens to have soft returns, such as if that data were originally entered via cut and paste, or if originally entered via a textarea field. The [input] context only affects the specific characters it has to deal with -- which means it makes sense to use it in all form fields that display text.================================Kenneth Grome, WebDNA Consultant808-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 Web Archive of this list is at: http://search.smithmicro.com/ Kenneth Grome

DOWNLOAD WEBDNA NOW!

Re: Incorrect Value Display

2000

Top Articles:

Related Readings: