Most of the files in the project are essentially pairs of files named:
inside the xxxx file is a single php statement requiring the same file name but w/ the php extension, e.g.
<?php require('xxxx.php'); ?>
What is the rational / programming practice / style / ... for doing this? It's very consistent so I have to believe it is done for a rational reason.
Best How To :
The point of this scheme is to achieve urls that don't end in
.php. Like this:
Another way of achieving the same net effect would be to create folders for each path instead of files and have each folder contain one file called
index.php (or whatever the default name you've configured is). Yet another way would be to use a rewrite rule configured at the web server level.