Here are things I've found as I've wandered through the program, that are more 'buggish' than incomplete coding.
1) you need to create the defs and backup directories
-- otherwise the admin program is _really_ cool... setup was 2 screens?
2) On the editor/tools/validate area, the following error was returned:
Error: Invalid template 'tools_validate.htm' requested (File does not exist)
That prompted me to look at the admin_templates directory.
The files there are all .htm files.
That creates an inconsistency for the user. While it might aid in development (.htm and .html files can coexist on most 32 bit+ systems) it will inevitably cause errors for the users that are easily avoided by sticking with one extension for the 'templates'.
Because of historical reasons, .txt is a file that is a template, but is not 'html' processed, I've taken to using .inc for my 'include' files. That is anything that designed to be included by the system into another file. Thus, header.txt is processed into header.inc, footer.txt into footer.inc, category_sidebar.html into category_sidebar.inc, etc.
So, that the .html and .txt files are 'templates'.
The .inc are 'included' and can be written out by the program with no ill effects for speed or to be used by .shtml extension files.
For instance, Top5.inc would be generated by the program on the first pass through the nph-build.cgi and then could be included in _any_ template from that point on, including server parsed ones -- such as SSI calls. No need to recompile it. Other uses are for directory sidebars that link to main categories, or anything else that may possibly change between any given build, but is static during any given build.
Anyway, I digress greatly. Point being stick with .html and.txt, and get rid of the .htm as it starts to confuse the issue, and _some_ servers may still only parse .htm and not .html files (yes, they do exist for 'security' reasons <sigh>), so using different extensions just muddies the pond.
http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/
1) you need to create the defs and backup directories
-- otherwise the admin program is _really_ cool... setup was 2 screens?
2) On the editor/tools/validate area, the following error was returned:
Error: Invalid template 'tools_validate.htm' requested (File does not exist)
That prompted me to look at the admin_templates directory.
The files there are all .htm files.
That creates an inconsistency for the user. While it might aid in development (.htm and .html files can coexist on most 32 bit+ systems) it will inevitably cause errors for the users that are easily avoided by sticking with one extension for the 'templates'.
Because of historical reasons, .txt is a file that is a template, but is not 'html' processed, I've taken to using .inc for my 'include' files. That is anything that designed to be included by the system into another file. Thus, header.txt is processed into header.inc, footer.txt into footer.inc, category_sidebar.html into category_sidebar.inc, etc.
So, that the .html and .txt files are 'templates'.
The .inc are 'included' and can be written out by the program with no ill effects for speed or to be used by .shtml extension files.
For instance, Top5.inc would be generated by the program on the first pass through the nph-build.cgi and then could be included in _any_ template from that point on, including server parsed ones -- such as SSI calls. No need to recompile it. Other uses are for directory sidebars that link to main categories, or anything else that may possibly change between any given build, but is static during any given build.
Anyway, I digress greatly. Point being stick with .html and.txt, and get rid of the .htm as it starts to confuse the issue, and _some_ servers may still only parse .htm and not .html files (yes, they do exist for 'security' reasons <sigh>), so using different extensions just muddies the pond.
http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/
Alpha 3 bugs/quirks