searchArgs when table rendering
Mike Myers
myersm at optonline.net
Mon Apr 22 14:23:24 PDT 2002
Site structure:
mysite.category1.default
mysite.cateogry2.default
The "default" pages are addresses pointing to another odb table. There is a
table rendering script in #tools. All that works just fine.
I wanted to add additional functionality, where a link from a page in
another site could supply a search argument and my table renderer could look
for it in the page table and act accordingly.
The url would look something like:
oh.me.com/mysite/category1/default?topic=blah
When I set this up, I get an error "Can¹t evaluate the expression because
the name ³tools² hasn¹t been defined."
I suspect this might be due to a limitation of Frontier's table rendering
scheme, because debugging code indicates that my table renderer is not even
being called. In fact, even a URL like this will fail:
oh.me.com/mysite/category1/default
I'm seeking confirmation and suggestions on how to else to do this. One
option is to create a single handler page which extracts the url params,
then POST the values to the appropriate page with tcp.httpClient(). (those
pages handle form data via loopback).
More information about the Frontier-Users
mailing list