Turn template into a php file Turn template into a php file
 

News:

CPG Release 1.6.26
Correct PHP8.2 issues with user and language managers.
Additional fixes for PHP 8.2
Correct PHP8 error with SMF 2.0 bridge.
Correct IPTC supplimental category parsing.
Download and info HERE

Main Menu

Turn template into a php file

Started by blowfishdl, January 29, 2008, 05:41:03 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

blowfishdl

Anyway to use template.php instead of template.html?

Joachim Müller

No. Read the docs? Searched the board? Obviously not.

zoinks

I understand that this question has been asked a million times, and the answer is always an emphatic "no!" But here's a followup question... Why not? If so many people (myself included) would benefit from the template.html file being template.php, why has this not been implemented in any of the updates over the years? To just say "that's the way it is in the core" -- as I've seen many times on this board -- doesn't really answer the question. Obviously the core can be revised, it happens all the time!

And having a template.php isn't just a one-off benefit -- Having to "hack" the include/themes.inc.php file to include additional php makes security updates/upgrades all the more difficult.

If one of the developers can address this I'd really appreciate it.  ???

Joachim Müller

Quote from: zoinks on April 19, 2008, 10:49:34 PMI understand that this question has been asked a million times, and the answer is always an emphatic "no!"
There will be no beaftures from cpg1.4.x to cpg1.4.y.

Quote from: zoinks on April 19, 2008, 10:49:34 PMwhy has this not been implemented in any of the updates over the years? To just say "that's the way it is in the core" -- as I've seen many times on this board -- doesn't really answer the question.
The question "why has coppermine been coded in the way it is" simply doesn't apply.

Quote from: zoinks on April 19, 2008, 10:49:34 PMObviously the core can be revised, it happens all the time!
Only happnes for bugfixes, but not for additional features. PHP-driven templates would be an additional feature. Doesn't make sense anyway, since you can accomplish anything without PHP being parsed in template.html.

Quote from: zoinks on April 19, 2008, 10:49:34 PMHaving to "hack" the include/themes.inc.php file to include additional php makes security updates/upgrades all the more difficult.
You're not supposed to edit that file - under no circumstances. Instead, you should edit themes/yourtheme/theme.php instead. This will help you when updadting as well. You have done something wrong (editing themes.inc.php instead of theme.php), so your question is invalid in the first place. RTFM!