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 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 Web Archive of this list is at: http://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Incorrect Value Display (John Peacock 2000)
  2. Re: Incorrect Value Display (John Butler 2000)
  3. Re: Incorrect Value Display (John Butler 2000)
  4. Re: Incorrect Value Display (Kenneth Grome 2000)
  5. Re: Incorrect Value Display (WebDNA Support 2000)
  6. Re: Incorrect Value Display (John Peacock 2000)
  7. 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 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 Web Archive of this list is at: http://search.smithmicro.com/ 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:

emailer settings and control questions (1997) Ongoing group search problems ... (1997) Troubles with Selection Drop Down List Search (1998) Three new problems ... (1997) More DateMath problems (1997) help with autenticate (1998) PROBLEM (1997) How To question on setting up downloads (1997) relogin same user? (1998) contextual shownext (1998) Recording size of uploaded file? (2001) Upgrading to 4.0 (2000) [subTotal] pricefield in another database !? (1998) Webcatalog error, Plug-in for Webstar (1996) PCS Frames (1997) WebDelivery downloads alias, not original ? (1997) Country & Ship-to address & other fields ? (1997) Emailer help....! (1997) One other big addition... (1997) Re:listfiles-looking for slick solution (1997)