It appears Alex is correct, not that that's any surprise. :) I did some testing on a small installation and the current template parser does indeed allow for PHP functionality. Did that get changed somewhere along the line? I could've sworn there was talk previously of any PHP in the templates becoming disabled after being parsed for CGI...
So, it looks like the best thing to do for people wanting PHP pages but not wanting to give up the directory structure is to simply set the build extension to .php and add any desired PHP tags to the templates.
I haven't tested any of the cgi-output template pages (add/modify/search), but I'm pretty sure those won't work for PHP... Going back to a previous question, with the new PHP frontend under development, will there be any way to control which templates page.php will function for? Using this example, all I would want it to do is take the place of add.cgi, modify.cgi, and the like, to have a consistent PHP interface. I would not want it to handle things like the home and category pages for the directory reasons mentioned above, so it would need to be smart enough to recognize where to point to for on-site links. For instance, the standard page.php approach might have the home page at /page.php and category #3 at /page.php?cat=3, whereas I would want it to link to pages/category_name/ (significant mostly if a user somehow got to the page.php version of the home page, possibly by manually removing the query string).
If that is beyond the scope of page.php, will it be possible to adapt pieces of it to work as individual templates for the add/modify type pages?
Thanks,
Dan
So, it looks like the best thing to do for people wanting PHP pages but not wanting to give up the directory structure is to simply set the build extension to .php and add any desired PHP tags to the templates.
I haven't tested any of the cgi-output template pages (add/modify/search), but I'm pretty sure those won't work for PHP... Going back to a previous question, with the new PHP frontend under development, will there be any way to control which templates page.php will function for? Using this example, all I would want it to do is take the place of add.cgi, modify.cgi, and the like, to have a consistent PHP interface. I would not want it to handle things like the home and category pages for the directory reasons mentioned above, so it would need to be smart enough to recognize where to point to for on-site links. For instance, the standard page.php approach might have the home page at /page.php and category #3 at /page.php?cat=3, whereas I would want it to link to pages/category_name/ (significant mostly if a user somehow got to the page.php version of the home page, possibly by manually removing the query string).
If that is beyond the scope of page.php, will it be possible to adapt pieces of it to work as individual templates for the add/modify type pages?
Thanks,
Dan