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:

Stupid question (2003) Check boxes (1997) Re:Emailer and encryption (1997) calculating tax rates, mail order solutions and version 2 (1997) HTML Editors (1997) Whats wrong with this???? (2001) $flushdatabases question ... (1998) [WebDNA] My SQL will not Connect (2020) Vann's - nice new WebCatalog site (1998) Web Catalog 2 demo (1997) Need some Java Script Code (2003) [shell]? (2000) Append command (1999) Progress !! WAS: Trouble with formula.db (1997) Moving encrypted fields to different boxes/platforms (2000) Wanted: More Math Functions (or, Can You Solve This?) (1997) NewCart+Search with one click ? (1997) [WebDNA] PayPal IPN (2009) Problems getting parameters passed into email. (1997) WebCat editing, SiteGuard & SiteEdit (1997)