searchArgs when table rendering

[Samuel Reynolds]

>On 4/23/02 12:01 PM, "Samuel Reynolds" <sam at spinwardstars.com> wrote:
>
>> You can parse the searchargs yourself, you know.
>> They *are* in the page table. (Crib the code from
>> the ONFH tutorial; it's a few lines in [one or more
>> of] the scripts.) Could be the simplest change to
>> make to make it work as you'd like.
>
>Sure. webserver.parseArgs().
>
>Where are the searchArgs located in a nascent page table? I saved my page
>table to workspace from the tablerRenderer, but could not locate the
>"?topic=blah" which I had appended to my URL.

Is there a subtable called "request"?
If not, the original request should be there *somewhere*.

>Both pathArgs and searchArgs were empty strings. This is what I meant about
>Frontier not propagating the search args.
>
>Maybe this approach doesn't work when the specially named web objects
>'default' or 'index' are being used.
>
>Sorry to belabor the fine detail, but what the hell, this list is in the
>doldrums.
>
>mpm

Oh, well.

Just do an ONFH at (site).#objectNotFoundHandler.
The 'remainingPath' parameter will be (for your
valid pages) in one of these forms:
1. category1
2. category1/default
3. category1/topic1
4. category1/topic1/default

(1) and (2) are identical.
if defined( categories^.['category1'] )
   render and return
else
   fall back to search page or return 404 result.

(3) and (4) are identical.
if defined( categories^.['category1'].['topic1'] )
   render and return
else
   fall back to search page or return 404 result.

HTH.

- Sam
- - - - - - - - - - - - - - - - - - - - - - - - - -
I'm currently looking for a new position/contract.
Resume at http://spinwardstars.com/vitae/
- - - - - - - - - - - - - - - - - - - - - - - - - -
_____________________________________________
Samuel Reynolds         sam at spinwardstars.com
Spinward Stars: http://www.spinwardstars.com/