x10Hosting Member
Can someone give me a list of files to split into? I want to keep the files compact by using includes. I don't know if header.php and footer.php would be good files to split.
header.php - Contains tags between <html> and </head>
footer.php - Contains the copyright and from </body> to </html>
-------
And the navbar:
navbar.php - Contains the navbar HREFs
Last edited by TofuBoy; 04-06-2009 at 10:04 AM.
Ignore the free V.I.P. thing because I don't have a forum yet. :nuts:
x10 Sophmore
x10 Sophmore
@ tofuboy
Having a header and footer include files seems to work fairly well for me, and it was recomended to me by someone else on this forum, so its likely an accepted if not recomeded way to do things
@parsa
works fine for me, post a sample of the code you're using, maybe you have a simple syntax error or the like
x10 Elder
@TofuBoy
i generally use one config file and use it to set variables for my separate parts, like this:
html page
config.phpHTML Code:<?php include('config.php'); ?> <!DOCTYPE blah...> <head> <?php echo $headCode; ?> </head>
PHP Code:<?php
$headCode = '<title>This is where your code goes.</title>';
etc...
?>
Generally Helpful Member
I've read somewhere that it is the best coding practice to keep any function 50 lines or less (excluding comments and long strings). So, it would be best to use many small functions instead of one huge function. This just makes your code easier to understand to you and for anyone who may need to look at it in the future.
It is also good to group functions that are often used together into the same file, so they are all included at once. Headers and Footers are used on every page, every time, so really, you could put them in the same file and save yourself a few keystrokes and probably a few processor cycles here and there. It doesn't make a lot of sense to put
In every file when you could just sayCode:include('header.php'); include('footer.php');
An exception would be if your code does not have a function. If your header is always the exact same thing, you don't need a function. Just put the code in the file then call header.php when you want the header output. Here, it makes more sense to separate them, since there's something in between the header and footer, presumably :PCode:include('whatever.php');
gjr.gr - coming soon: secrets of OCD coding from a self taught tinkerer
Abuse Compliance Officer
For me, I split configuration, frequently used functions, and my mysql connect's into them.
The mysql-connection's a big one though - include("logmein_admin.php") or include("logmein.php"), depending if it needs all permissions, or just select.
The reason it's a big one? Locally, the password and username are different. So x10's got a different logmein and logmein_admin than localhost.
I don't have to change my code to make it work on x10
If anything, I'd store mysql username/passwords in an include, then bury it in a folder with a .htaccess "Deny From All" setting. Seems include and require CAN access folders that have been set to "deny from all," which makes it handy - index.php can include includes/logmein_admin.php, but there's no way to actually access logmein_admin.php directly ^_^
TOS breakers will be suspended regardless of race, creed, national origin, hair color, or favorite food. Thanks for your understanding!
x10 Elder
I always use includes for headers and footers and yes, it is an accepted way of doing things.
I think your have to have an intermediate account for includes to work though which is why you might be having problems.
Posting Permissions
LinkBack URL
About LinkBacks
Reply With Quote
