Re: & not allowed in db by definition?

This WebDNA talk-list message is from

1999

It keeps the original formatting. numero = 25575
interpreted = N
texte = >Using the store template from storebuilder, the only fields that I can>find that the ampersand is making a difference is the product title>field, because that is passed to the emailer program, and that is where>it is crashing. However, it is probably a good idea to just avoid it on>principle just in case you have a part of your webDNA that will treat it>is an html variable command connector. This kept my site crashing for 2>months before I finally tracked it down as the culprit. If WebCat techs>had suggested this very simple solution to me, they could have saved me>a lot of time and headaches. I would recommend not using ampersands &>too, from my own personal experience. I almost gave up on WebCatalog due>to the fact that the tech support people just wouldn't do anything but>suggest that I write the mail list here, and nobody on the mail list>seemed to be able to help me. It was simply amazing to discover that the>bug in my code was something so simple as & ampersand in my>database. It also explained why the crashing seemed totally random. It>was only crashing when it hit specific items with the ampersand and was>doing fine the rest of the times.... it was just a matter of figuring>out that the ampersand was the common denominator.Hi Conrad,I can understand your frustration. However, your suggestions only avoid the problem, they do nothing to solve it. The proper solution to this problem is to write your webdna code correctly in the first place -- and that means wrapping every value in your search, append, replace and delete contexts inside an [url] context.How many times on this list have some of us suggest, time and time again, to wrap ALL your parameter values in [url] contexts when those values appear in search, append, replace and delete contexts? If you use the [url] context where you SHOULD be using it, then ampersands will *never* bother you. That's all there is to it.================================Kenneth Grome, WebDNA Consultant808-737-6499, http://webdna.net================================-------------------------------------------------------------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:

>Using the store template from storebuilder, the only fields that I can>find that the ampersand is making a difference is the product title>field, because that is passed to the emailer program, and that is where>it is crashing. However, it is probably a good idea to just avoid it on>principle just in case you have a part of your webDNA that will treat it>is an html variable command connector. This kept my site crashing for 2>months before I finally tracked it down as the culprit. If WebCat techs>had suggested this very simple solution to me, they could have saved me>a lot of time and headaches. I would recommend not using ampersands &>too, from my own personal experience. I almost gave up on WebCatalog due>to the fact that the tech support people just wouldn't do anything but>suggest that I write the mail list here, and nobody on the mail list>seemed to be able to help me. It was simply amazing to discover that the>bug in my code was something so simple as & ampersand in my>database. It also explained why the crashing seemed totally random. It>was only crashing when it hit specific items with the ampersand and was>doing fine the rest of the times.... it was just a matter of figuring>out that the ampersand was the common denominator.Hi Conrad,I can understand your frustration. However, your suggestions only avoid the problem, they do nothing to solve it. The proper solution to this problem is to write your webdna code correctly in the first place -- and that means wrapping every value in your search, append, replace and delete contexts inside an [url] context.How many times on this list have some of us suggest, time and time again, to wrap ALL your parameter values in [url] contexts when those values appear in search, append, replace and delete contexts? If you use the [url] context where you SHOULD be using it, then ampersands will *never* bother you. That's all there is to it.================================Kenneth Grome, WebDNA Consultant808-737-6499, http://webdna.net================================-------------------------------------------------------------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 Kenneth Grome

DOWNLOAD WEBDNA NOW!

Re: & not allowed in db by definition?

1999

Top Articles:

Related Readings: