Hi All

The default index pages are named "index.html" and the the default span pages look like "/more2.html"

Instead of those, I would prefer creating a new field in category.def, entering some value per category, and then having the script use those values as a substitutes for "index" and "more"

Examples

Category: Shoes
"extension_name" = shoes_and_stuff
../shoes_and_stuff.html
../shoes_and_stuff2.html
../shoes_and_stuff3.html

Category: Frogs
"extension_name" = frogs_and_friends
../frogs_and_friends.html
../frogs_and_friends2.html
../frogs_and_friends3.html

Is this possible? This would be a great hack.

Thanks very much



------------------------------------------

Forgot...

Would like to do the same with detail pages, too



------------------------------------------

You need an index page in each category, as that is the first page that is displayed, by internet default. Without an index page, you would have to specify a link to a page in each folder. Normally you have this:

Directory name: Shoes
../index.html

So going to Shoes will automatically present the viewer with index.html. Without that, the directory would be unviewable, unless linked to specifiaclly;

../Shoes/shoes_and_stuff.html


Here's some thoughts, probably not rightm but in the right place to make the changes. From nph-build.cgi, sub_build_category_pages:

$next = $url . "more$page_num$build_extension";

maybe changing it to this would do it...

$next = $url . "$cat$page_num$build_extension";

And this:

$next = $url . "more$next_page$build_extension";

to this...

$next = $url . "$cat$next_page$build_extension";


Leonard
aka PerlFlunkie

Hey Leonard

Yep. That's what I was thinking, too. In fact, I think I could still add a field if I wanted to. Your point about the index.html is well taken. The script is set up to look for index.html in the nav menu and things. It would be too hard to have each and every category index page named otherwise.

I'll also see what I can come up with for the detail pages, too.

Thanks very much

------------------------------------------

If you're using the nonenglish mod, you could probably use that field.


Leonard
aka PerlFlunkie

Yeah. Using nonenglish. I'll give it a go. Thanks, Leonard

------------------------------------------