Tip: upgrading to WebCatalog 3.x, fields to watch for

This WebDNA talk-list message is from

1999


It keeps the original formatting.
numero = 23016
interpreted = N
texte = Hi, we have noticed that a few people have had trouble with some of their WebDNA templates when upgrading to WebCatalog 3.x. The symptom is that the page shows up either blank or halfway filled-out, stopping for no apparent reason. The problem stems from the new [Text] context, because some people already have a field named text in their databases. This conflicts with the context of the same name. Similar things arose when we added the [URL] context in 2.xSolution: rename any database fields that are named text, url, etc. (basically you shouldn't use any fieldnames that WebCatalog already uses for context names).Problem:[search db=xx.db] [founditems] [text] <-- this used to work, but now WebCatalog thinks it's meant <-- to be [text]SomeVariable=Some Words[/text], so it prints <-- an error message saying it can't find the ending [/text] [/founditems] [/search]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:

    
  1. Re: Tip: upgrading to WebCatalog 3.x, fields to watch for (PCS Technical Support 1999)
  2. Re: Tip: upgrading to WebCatalog 3.x, fields to watch for (Kenneth Grome 1999)
  3. Re: Tip: upgrading to WebCatalog 3.x, fields to watch for (Paul Uttermohlen 1999)
  4. Tip: upgrading to WebCatalog 3.x, fields to watch for (PCS Technical Support 1999)
Hi, we have noticed that a few people have had trouble with some of their WebDNA templates when upgrading to WebCatalog 3.x. The symptom is that the page shows up either blank or halfway filled-out, stopping for no apparent reason. The problem stems from the new [text] context, because some people already have a field named text in their databases. This conflicts with the context of the same name. Similar things arose when we added the [url] context in 2.xSolution: rename any database fields that are named text, url, etc. (basically you shouldn't use any fieldnames that WebCatalog already uses for context names).Problem:[search db=xx.db] [founditems] [text] <-- this used to work, but now WebCatalog thinks it's meant <-- to be [text]SomeVariable=Some Words[/text], so it prints <-- an error message saying it can't find the ending [/text] [/founditems] [/search]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

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:

Re:add line item context and showitems (1998) webcat page crashes MSIE 5 on mac (2000) [WebDNA] WebDNA 6.2 ErrorLog.txt (2014) auto enter dates (1998) Listfiles on network with NT (2000) OT: javascript help (2003) 2.0 Info (1997) Displaying photo attached to first record (1997) Google MAP URLs (2006) [WebDNA] Intranet site request (2010) is there a [purchase]? (1998) Caching [include] files ... (1997) New Site Announcement (1998) same product in cart (1997) PROBLEM (1997) Wierd Password Tension (1999) WebDNA 5 & iTools 7 (2003) Signal Raised (1997) Fun with dates (1997) WCS Newbie question (1997)