Long-standing bug in nextPrev generation, etc.

[Rick Hansen]

Please try:

http://www.inligo.com/frontier/tips/studio/nextPrev.html

Works beautifully.

Heath Tanner is god!

Rick

On 8/1/01 2:17 AM, "Michael 'Mickey' Sattler" <michael at GeekTimes.com> wrote:

> BUG #1:A long-standing bug which I just fell across yet again is that
> the nextPrev generation inserts entries for index.html files even if
> the hierarchy one is processing doesn't have them. This silly thing
> is worthy of a fix. If I've chosen other names for the items, I
> really don't want nextPrev assuming that I haven't finished yet and
> will add an index.html. Just process what's there, thank you very
> much.
> 
> Why am I noticing this today? Because old nextPrev entries won't work
> with guest databases. Sigh. It breaks and doesn't generate any errors.
> 
> BUG #2: when a nextPrev entry is processed and there is no match it
> would be nice to (at least optionally) be told that there is no
> matching data in the list.
> 
> Specifically, entries which used to look like this:
> 
>  GeekTimes.michael.["CU-SeeMe"].reflectors.index
> 
> Must now be regenerated to look like this:
> 
> 
> ["rosenkrantz:Users:mickey:Documents:web:GeekTimes.root"].GeekTimes.michael.["
> CU-SeeMe"].reflectors.index

--