Site Reference Forums

Just to stick my oar in!!

There's somethings you'll need to consider when using includes:

1. most servers won't allow you to include a remote file from another server. Similarly, most servers won't allow a file to be remotely included (make sense?)

2. You can include any kind of file (pretty much) but it's best to stick with php, txt or html files. including Javascript isn't as quick as the standard way (and bloats the outputted html code) and why anyone would bother including an image, i don't know!!

3. It's possible to include within a .html file using the same code by making alterations to your .htaccess file.  you would tell your server to treat all HTML files (files with a .html extension) as php files. Personally I wouldn't though. You can get a similar effect (ie, .html extension in your URLs) by using a proper php file and using .htaccess mod rewrite to change the extension on the fly.
Search keyword: mod rewrite

4. There are 4 kinds of includes. They're all used the same, but have slightly different effects. eg:

this code in test.php:

<?php include("file.php");  ?>

include() includes the file. If the included file is missing, there'll be an error in place of the include, but the file (test.php) will continue to execute after the include line.

<?php require("file.php");  ?>

require() includes the file. If the included file is missing there'll be an error in place of the include, AND the file (test.php) will STOP executing at the include line.

<?php include_once("file.php");  ?>

include_once() includes the file. During execution of test.php, include_once would check to see if file.php has already been included. if it has, it'll ignore the new request and carry on executing test.php. however, there will be an error where the include_once statement is.

<?php require_once("file.php");  ?>

require_once() includes the file. During execution of test.php, require_once would check to see if file.php has already been included. if it has, it'll ignore the new request and STOP executing test.php where the require_once statement is.


So, 4 ways, how do you know what to do?

easy peasy really. if you're including a static html file, test using include(). Once the page is ready for the public, change to include_once()
If you're including a PHP file, especially if it's connected to your database or has other security issues, use require() to test (helps with debugging) and switch to require_once() once live.

Always go public with _once() or you might find a hacker can add a string to the URL and reinclude just about anything!

If your included file contains functions, classes or any other kind of PHP working out, it's best to include it BEFORE any html output (ie, before the HTML tag).
You can include a file that creates a variable, then echo out that varibal in different ways too:

eg:

<?PHP echo $variable; ?>

<? echo $variable; ?>

<?PHP echo "$variable"; ?>

<?= $variable; ?>

The last one is my personal fav.

Anyhoo, hope this gets the creative juices flowing alittle in the New Year!!
Well done for making the leap to PHP, you'll never look back!

Thanks Fellas.

Getting just a bit complex for this country lad.

Got me worried about the security issues.

Regards,
Laurie.