Re: [WebDNA] inputed text getting scrambled up in DB

This WebDNA talk-list message is from

2012


It keeps the original formatting.
numero = 108398
interpreted = N
texte = DefaultMaxClassProcessCount 1 Did not help any HOWEVER I did try the double [url] wrap into the database and [unurl] coming = out, as Ken suggested, and this WORKED This really is not ideal, but at least its a solution. Perhaps it is a = better idea after all to double [url] wrap text because of all the = carriage returns, tabs, and whatever else could be in there from user = input. So, for my final observations... Originally when I was troubleshooting, I put the single [url]'ed string = (wrapped in {replace}) to see what was being put into the database and = verified that it was correct to what was inputed. So to me, this means = that the text became scrambled somewhere between the [replace] command = being called and actually writing the var to file. =20 Also, I ran a test by adding several sentences with no carriage returns. = No problem. Add some carriages, enter the problems. However, I have an AJAX based db application that first takes a request = (a link) and grabs a db record with Ajax (kind of like a model), then = puts a view/modify record form into a
via the Jquery html() = method. Upon form submission, Jquery serializes the form into an array = and sends it back to itself (again via Ajax) where a function is called = cotaining: [replace db=3D[selectedDb]&eqiddatarq=3D[recordID]][listfields = db=3D[selectedDb]][fieldname]=3D[url][interpret][[fieldname]][/interpret][= /url]...... sort of logic Of course it would take way too much time for me right now to create an = isolated instance containing the entire Ajax+WebDNA function logic. But = it WORKS! However, when I did try to make a much more simplified = (single ajax call) version of this it didn't work. Way to many = 'variables' there to really know what the magic key is, but I can tell = you that in the example where this works (same db on the same server), = javascript is acting as a controller - it takes a request for a certain = db and displays a DB Record Append/Replace screen and and then Submits = them all 100% with AJAX. =20 The underlying processes behind a basic html form post or the ajax = XMLHTTPRequest, are beyond me. The fact that there is a variance = between the execution of these as well as with the OS may mean something = to a technical wizard. If anyone has clues, it would be cool to know. = Otherwise, I'll just conclude that double [url][url] wrapping user = content is a smart thing ;-) Thanks, Aaron= Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] inputed text getting scrambled up in DB (aaronmichaelmusic@gmail.com 2012)
  2. Re: [WebDNA] inputed text getting scrambled up in DB (Govinda 2012)
  3. Re: [WebDNA] inputed text getting scrambled up in DB (aaronmichaelmusic@gmail.com 2012)
  4. Re: [WebDNA] inputed text getting scrambled up in DB (christophe.billiottet@webdna.us 2012)
  5. Re: [WebDNA] inputed text getting scrambled up in DB (aaronmichaelmusic@gmail.com 2012)
  6. Re: [WebDNA] inputed text getting scrambled up in DB (christophe.billiottet@webdna.us 2012)
  7. Re: [WebDNA] inputed text getting scrambled up in DB (aaronmichaelmusic@gmail.com 2012)
  8. Re: [WebDNA] inputed text getting scrambled up in DB (Donovan Brooke 2012)
  9. Re: [WebDNA] inputed text getting scrambled up in DB (aaronmichaelmusic@gmail.com 2012)
  10. Re: [WebDNA] inputed text getting scrambled up in DB (Donovan Brooke 2012)
  11. Re: [WebDNA] inputed text getting scrambled up in DB (Kenneth Grome 2012)
  12. Re: [WebDNA] inputed text getting scrambled up in DB (Kenneth Grome 2012)
  13. Re: [WebDNA] inputed text getting scrambled up in DB (aaronmichaelmusic@gmail.com 2012)
  14. Re: [WebDNA] inputed text getting scrambled up in DB (aaronmichaelmusic@gmail.com 2012)
  15. Re: [WebDNA] inputed text getting scrambled up in DB (aaronmichaelmusic@gmail.com 2012)
  16. Re: [WebDNA] inputed text getting scrambled up in DB (Donovan Brooke 2012)
  17. Re: [WebDNA] inputed text getting scrambled up in DB (Govinda 2012)
  18. Re: [WebDNA] inputed text getting scrambled up in DB (aaronmichaelmusic@gmail.com 2012)
  19. Re: [WebDNA] inputed text getting scrambled up in DB (Donovan Brooke 2012)
  20. [WebDNA] inputed text getting scrambled up in DB (aaronmichaelmusic@gmail.com 2012)
DefaultMaxClassProcessCount 1 Did not help any HOWEVER I did try the double [url] wrap into the database and [unurl] coming = out, as Ken suggested, and this WORKED This really is not ideal, but at least its a solution. Perhaps it is a = better idea after all to double [url] wrap text because of all the = carriage returns, tabs, and whatever else could be in there from user = input. So, for my final observations... Originally when I was troubleshooting, I put the single [url]'ed string = (wrapped in {replace}) to see what was being put into the database and = verified that it was correct to what was inputed. So to me, this means = that the text became scrambled somewhere between the [replace] command = being called and actually writing the var to file. =20 Also, I ran a test by adding several sentences with no carriage returns. = No problem. Add some carriages, enter the problems. However, I have an AJAX based db application that first takes a request = (a link) and grabs a db record with Ajax (kind of like a model), then = puts a view/modify record form into a
via the Jquery html() = method. Upon form submission, Jquery serializes the form into an array = and sends it back to itself (again via Ajax) where a function is called = cotaining: [replace db=3D[selectedDb]&eqiddatarq=3D[recordID]][listfields = db=3D[selectedDb]][fieldname]=3D[url][interpret][[fieldname]][/interpret][= /url]...... sort of logic Of course it would take way too much time for me right now to create an = isolated instance containing the entire Ajax+WebDNA function logic. But = it WORKS! However, when I did try to make a much more simplified = (single ajax call) version of this it didn't work. Way to many = 'variables' there to really know what the magic key is, but I can tell = you that in the example where this works (same db on the same server), = javascript is acting as a controller - it takes a request for a certain = db and displays a DB Record Append/Replace screen and and then Submits = them all 100% with AJAX. =20 The underlying processes behind a basic html form post or the ajax = XMLHTTPRequest, are beyond me. The fact that there is a variance = between the execution of these as well as with the OS may mean something = to a technical wizard. If anyone has clues, it would be cool to know. = Otherwise, I'll just conclude that double [url][url] wrapping user = content is a smart thing ;-) Thanks, Aaron= aaronmichaelmusic@gmail.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:

Socks Proxy Error (1999) RE: Still Learning (1997) Message Boards (2003) quit command on NT (1997) Problem about [CART] number (1998) Help!!!! (1997) searchable list archive (1997) Nested vs conditional (1997) Append..... doesn't (2000) WebDNA Quick Reference (Reserved Words) (2000) How to append text after the sign & (1997) apostrophe in search item (1997) Emailer Problem (1998) [format 40s]text[/format] doesn't work (1997) 2.1 Stuff (1998) triggering an update of two frames (1998) Associative lookup style? + bit more (1997) emailer (1997) [WriteFile] problems (1997) Server Load (2000)