Re: bypassing typo's

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 18710
interpreted = N
texte = I did something related in order to prevent users from posting profanity to a discussion done in WebCatalog.I made a file called foul.db which contains four-letter words and multiple word phrases (Web Cat will find 'see' or 'spot' but also 'see spot run '). The only field is called item.Next, I do a search followed by a found items loop, containing a check against each field entered by the user: Suppose that the user has entered their (1) name, (2) email, and (3) message on a previous page, using an entry form.I would add this to the destination page:[math]profanity=0[/math] [search db=foul.db&geitemdata=0] [founditems][showif [name]^[item]] [math show=F]profanity=profanity+1[/math] [/showif][showif [email]^[item]] [math show=F]profanity=profanity+1[/math] [/showif][showif [message]^[item]] [math show=F]profanity=profanity+1[/math] [/showif][showif [math show=F]profanity[/math]>1] [append...] [/showif][hideif [math show=F]profanity[/math]>1] Some accusatory warning message about profanity, along with [ipaddress] [/hideif]Your approach could be similar, but instead of using a single item list, you could build a list of matching pairs:right wrong riverchase riverchace riverchase riverchas riverchase rivrechase wisconsin wisconson wisconsin wicsonsin ...and on and on...You would then either set up code to use the [wrong] version as if it were the [right] version of the word, or, if you had to, replace the [wrong]s with [right]s - which might get a little tricky.Good Luck -Pat-----Original Message----- From: PCS Technical Support To: Date: Monday, July 06, 1998 6:23 PM Subject: Re: bypassing typo's >>Has any one found a way to make it possible for webcat to manipulate typo's >>say you have a field name riverchase and a user types riverchace , is there >>a way you can make webcat look over these kind of mistakes ? > >Sure, turn on the Artificial Intelligence preference and you're all set ;) > >But seriously, WebCatalog is actually very good at things like Begins >With Separate Words and Contains, so something like river chace >would turn up pretty good results, as well as rivercha. Your case is a >little too much to ask, though. > >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: bypassing typo's (Pat McCormick 1998)
  2. Re: bypassing typo's (talk 1998)
  3. bypassing typo's (talk 1998)
  4. Re: bypassing typo's (PCS Technical Support 1998)
I did something related in order to prevent users from posting profanity to a discussion done in WebCatalog.I made a file called foul.db which contains four-letter words and multiple word phrases (Web Cat will find 'see' or 'spot' but also 'see spot run '). The only field is called item.Next, I do a search followed by a found items loop, containing a check against each field entered by the user: Suppose that the user has entered their (1) name, (2) email, and (3) message on a previous page, using an entry form.I would add this to the destination page:[math]profanity=0[/math] [search db=foul.db&geitemdata=0] [founditems][showif [name]^[item]] [math show=F]profanity=profanity+1[/math] [/showif][showif [email]^[item]] [math show=F]profanity=profanity+1[/math] [/showif][showif [message]^[item]] [math show=F]profanity=profanity+1[/math] [/showif][showif [math show=F]profanity[/math]>1] [append...] [/showif][hideif [math show=F]profanity[/math]>1] Some accusatory warning message about profanity, along with [ipaddress] [/hideif]Your approach could be similar, but instead of using a single item list, you could build a list of matching pairs:right wrong riverchase riverchace riverchase riverchas riverchase rivrechase wisconsin wisconson wisconsin wicsonsin ...and on and on...You would then either set up code to use the [wrong] version as if it were the [right] version of the word, or, if you had to, replace the [wrong]s with [right]s - which might get a little tricky.Good Luck -Pat-----Original Message----- From: PCS Technical Support To: Date: Monday, July 06, 1998 6:23 PM Subject: Re: bypassing typo's >>Has any one found a way to make it possible for webcat to manipulate typo's >>say you have a field name riverchase and a user types riverchace , is there >>a way you can make webcat look over these kind of mistakes ? > >Sure, turn on the Artificial Intelligence preference and you're all set ;) > >But seriously, WebCatalog is actually very good at things like Begins >With Separate Words and Contains, so something like river chace >would turn up pretty good results, as well as rivercha. Your case is a >little too much to ask, though. > >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/ > > Pat McCormick

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:

Nav4 not specifying cart (1997) [item] appears after 'remove last item' ... (1997) [append] (1997) hidden (phantom) file downloads (2000) searching with groups (1997) Multiple Pulldowns (1997) [HIDEIF] inside [FOUNDITEM] (1997) Credit Card Checksum (1997) Cookies (2003) request for string functions (1998) WebCatalog and Webstar 3.02 (1998) Word search (1997) Virtual hosting and webcatNT (1997) followup to ws3 vs ws2.1 speed (1998) [date] insanity! (2001) Do search engines index .tpl pages? (2006) Can you specify encoding=multiline? (2000) Rotating Banners ... (was LinkExchange) (1997) Search Questions (2000) 2.0Beta Command Ref (can't find this instruction) (1997)