Re: [WebDNA] search command problem
This WebDNA talk-list message is from 2009
It keeps the original formatting.
numero = 102019
interpreted = N
texte = Grant Hulbert wrote: >> Error: WebCatalog does not understand the 'search db=/data/stories.db' >> command > > Taken literally, this error message is saying that you have sent a > variable named "command" with the value "search db=/data/stories.db". > > The command needs to be *only* the word "*search*". There should be > another separate variable named "db", with value "/data/stories.db" > > So I'm guessing you'll need to look very closely at your hyperlink (try > typing it in by hand in the browser) to make sure you've got all the > delimiters in the right places. > > I know your example link that you posted shows the & delimiters in the > right places, but that doesn't seem to be the actual link that's being > presented to WebDNA. > > Also try adding a little code to the top of the readtextstory.html page > that shows the values of all incoming variables, like [command] and [db] > and [max] to see what the parser believes those values are. > > Also, if the browser thinks that "&db" is some kind of escaped entity > string, similar to "&", then the browser itself is what's getting in > your way. Grant stated my hunch much better than I! (Communication with humans is not always my strong point) ;-) I just wanted to add to what he said in the very last paragraph regarding the URL being escaped. Along these lines, you may also want to check to make sure the href value is not being [url][/url]'ed via the sending page as well. But I think we both Grant and I agree that the error message says that the URL that WebDNA sees is not right, and not being parsed as two separate two separate name/value pairs. I guess, to test this theory, I would change the URL to:
(noting only 'command' was changed to 'carman') Then, on the resulting/landing page just under the element, add this code (copy/paste between 'snip' and '/snip' lines): -snip------------------------------ [formvariables] [index].)[name]=[value]
[/formvariables] -/snip----------------------------- This will list all the form variables being received on the landing page and will index them accordingly. Then "view source" of that landing page and find "" and highlight/copy the test text below that line, and Post the results of that test to us. You want to do this via source view and not browse view because we need to check if characters are being encoded. You should be able to determine for yourself if the variable named 'carman' and the variable named 'db' are separate name/value pairs via if they have different indexes. If they are separate indexes, this doesn't necessarily mean WebDNA is receiving them correctly, but it will give us some more clues as to what is going on. Donovan -- Donovan D. Brooke PH: 1 (608) 770-3822 ------------------------------------------------ WebDNA Software Corporation 16192 Coastal Highway Lewes, DE 19958
Associated Messages, from the most recent to the oldest:
Grant Hulbert wrote: >> Error: WebCatalog does not understand the 'search db=/data/stories.db' >> command > > Taken literally, this error message is saying that you have sent a > variable named "command" with the value "search db=/data/stories.db". > > The command needs to be *only* the word "*search*". There should be > another separate variable named "db", with value "/data/stories.db" > > So I'm guessing you'll need to look very closely at your hyperlink (try > typing it in by hand in the browser) to make sure you've got all the > delimiters in the right places. > > I know your example link that you posted shows the & delimiters in the > right places, but that doesn't seem to be the actual link that's being > presented to WebDNA. > > Also try adding a little code to the top of the readtextstory.html page > that shows the values of all incoming variables, like [command] and [db] > and [max] to see what the parser believes those values are. > > Also, if the browser thinks that "&db" is some kind of escaped entity > string, similar to "&", then the browser itself is what's getting in > your way. Grant stated my hunch much better than I! (Communication with humans is not always my strong point) ;-) I just wanted to add to what he said in the very last paragraph regarding the URL being escaped. Along these lines, you may also want to check to make sure the href value is not being
[url][/url]'ed via the sending page as well. But I think we both Grant and I agree that the error message says that the URL that WebDNA sees is not right, and not being parsed as two separate two separate name/value pairs. I guess, to test this theory, I would change the URL to:
(noting only 'command' was changed to 'carman') Then, on the resulting/landing page just under the element, add this code (copy/paste between 'snip' and '/snip' lines): -snip------------------------------ [formvariables] [index].)[name]=[value]
[/formvariables] -/snip----------------------------- This will list all the form variables being received on the landing page and will index them accordingly. Then "view source" of that landing page and find "" and highlight/copy the test text below that line, and Post the results of that test to us. You want to do this via source view and not browse view because we need to check if characters are being encoded. You should be able to determine for yourself if the variable named 'carman' and the variable named 'db' are separate name/value pairs via if they have different indexes. If they are separate indexes, this doesn't necessarily mean WebDNA is receiving them correctly, but it will give us some more clues as to what is going on. Donovan -- Donovan D. Brooke PH: 1 (608) 770-3822 ------------------------------------------------ WebDNA Software Corporation 16192 Coastal Highway Lewes, DE 19958
Donovan Brooke
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:
Sorta OT: Printing From Browser Window (2001)
Forbidden CGI Error (1997)
RE: Signal Raised (1997)
Running _every_ page through WebCat-error.html (1997)
Testing band width (2002)
Setting Cart value (2000)
OK, here's a new one (2002)
WebCatalog2 Feature Feedback (1996)
Email Formatting (1998)
M$loth messes with our sites (again) 2004/02/03 (2004)
Sorting Numbers (1997)
Weird bug, or is there something amiss? (1997)
Date stamp and purging (1998)
shipping calcs (1998)
two domains and one cart and database (2000)
PCS Frames (1997)
5.0 feature request: (2001)
WCS Newbie question (1997)
a search based on ^(contains) (1998)
Which GUI HTML editors work with WC ? (1997)