numero = 19421
interpreted = N
texte = >(This is where they enter the new message): >[search db=msg.db&eqsubjectdatarq=[subject]&max=1] <<---here?Yes, if the [subject] could ever contain an & or =>[founditems] > <<---here?Yes, if the [subject] could ever contain a quote character like >[append db=msg.db]subject=[subject]&otherstuff[/append] <<---here?Yes, if the subject could ever contain & or =>[subject]Yes, if the [subject] could ever contain &, space, or =.The idea behind the [URL] context is that certain letters are illegal in some places. An HREF, for instance, must never contain a space, because it freaks out the browser and web server. Somewhat more subtle, but just as important, is text that happens to contain delimiter characters like & and =. Humans can see that the ampersand inside Casady&Greene means something very different from var1=Casady&var2=Greene, yet the computer is not so smart. So the [URL] context also converts & and = into special sequences that will automatically get converted back when necessary.So companyName=Casady&Greene won't do what you hope it will, but if you look at what companyName=[URL]Casady&Greene[/URL] displays, you'll see it becomes companyName=Casady%26Greene. If you append some text that looks like that to a database using WebDNA, you'll see that the actual text put into the database is Casady&Greene, because WebCatalog always decodes the URL-encoded text before storing it in the field.Technical Support | ==== eCommerce and Beyond ==== Pacific Coast Software | WebCatalog, WebMerchant, 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, San Diego, CA 92128 | Typhoon 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Re: Fuzzy on [url] context (PCS Technical Support 1998)
>(This is where they enter the new message): >[search db=msg.db&eqsubjectdatarq=[subject]&max=1] <<---here?Yes, if the [subject] could ever contain an & or =>[founditems] > <<---here?Yes, if the [subject] could ever contain a quote character like >[append db=msg.db]subject=[subject]&otherstuff[/append] <<---here?Yes, if the subject could ever contain & or =>[subject]Yes, if the [subject] could ever contain &, space, or =.The idea behind the [url] context is that certain letters are illegal in some places. An HREF, for instance, must never contain a space, because it freaks out the browser and web server. Somewhat more subtle, but just as important, is text that happens to contain delimiter characters like & and =. Humans can see that the ampersand inside Casady&Greene means something very different from var1=Casady&var2=Greene, yet the computer is not so smart. So the [url] context also converts & and = into special sequences that will automatically get converted back when necessary.So companyName=Casady&Greene won't do what you hope it will, but if you look at what companyName=[url]Casady&Greene[/URL] displays, you'll see it becomes companyName=Casady%26Greene. If you append some text that looks like that to a database using WebDNA, you'll see that the actual text put into the database is Casady&Greene, because WebCatalog always decodes the URL-encoded text before storing it in the field.Technical Support | ==== eCommerce and Beyond ==== Pacific Coast Software | WebCatalog, WebMerchant, 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, San Diego, CA 92128 | Typhoon 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/
PCS Technical Support
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...