I've updated this plugin, and it works a bit differently than the 2.x version.
The later versions of 2.x and 3.0 have installed much of the functionality (and thus the purpose) of the original detail_page.cgi
But, in doing so, and trying to do other things, there are some places where the same concept of functionality is needed.
What this plugin does:
1) it runs as a plugin to page.cgi
2) it hooks into the handle_page and generate_detailed hooks/routines
3) it allows you to use the option in the Admin to build pages with FullCategoryName/Title_ID format DYNAMIC, not just static.
4) it allows you to call page.cgi with page.cgi?ID=nnn or page.cgi?p=detailed&ID=nnn to display a detail page from *anywhere* such as the Top, Cool, or Search pages, where <%detailed_URL%> doesn't work.
5) Gets rid of my frustration and broken sites every time the Page.pm was updated and this functionality still hasn't been built into the Page.pm module as distributed.
That's pretty much *all* it does.
At some point, I might add in a routine to check for the link existing in only one category (eg: count from the CatLinks table where Link_ID=<%ID%>). That would allow it to generate a detailed page for that category, as well. Right now, the detail page is just the basic detail page, under the category "Detailed"
Helps if I actually attach the plugin.....
There are no options, nothing to edit, and you can install/unistall without affecting anything, or should. If you want to disable the ID= feature (the handle_page hook on the edit option in the main window), you'll probably increase performance a tad, if you only want to use the extended/enhanced detail pages (and still link via jump.cgi to the Top, Cool, etc pages). It won't have to check on each call if you are asking for a detail page or not. (This is one reason why adding this feature into the Page.pm module was my first choice, and why GT should really add this in.)
PUGDOG� Enterprises, Inc.
The best way to contact me is to NOT use Email.
Please leave a PM here.
The later versions of 2.x and 3.0 have installed much of the functionality (and thus the purpose) of the original detail_page.cgi
But, in doing so, and trying to do other things, there are some places where the same concept of functionality is needed.
What this plugin does:
1) it runs as a plugin to page.cgi
2) it hooks into the handle_page and generate_detailed hooks/routines
3) it allows you to use the option in the Admin to build pages with FullCategoryName/Title_ID format DYNAMIC, not just static.
4) it allows you to call page.cgi with page.cgi?ID=nnn or page.cgi?p=detailed&ID=nnn to display a detail page from *anywhere* such as the Top, Cool, or Search pages, where <%detailed_URL%> doesn't work.
5) Gets rid of my frustration and broken sites every time the Page.pm was updated and this functionality still hasn't been built into the Page.pm module as distributed.
That's pretty much *all* it does.
At some point, I might add in a routine to check for the link existing in only one category (eg: count from the CatLinks table where Link_ID=<%ID%>). That would allow it to generate a detailed page for that category, as well. Right now, the detail page is just the basic detail page, under the category "Detailed"
Helps if I actually attach the plugin.....
There are no options, nothing to edit, and you can install/unistall without affecting anything, or should. If you want to disable the ID= feature (the handle_page hook on the edit option in the main window), you'll probably increase performance a tad, if you only want to use the extended/enhanced detail pages (and still link via jump.cgi to the Top, Cool, etc pages). It won't have to check on each call if you are asking for a detail page or not. (This is one reason why adding this feature into the Page.pm module was my first choice, and why GT should really add this in.)
PUGDOG� Enterprises, Inc.
The best way to contact me is to NOT use Email.
Please leave a PM here.