return
Two functions to help:
<?php
function add_include_path ($path)
{
foreach (func_get_args() AS $path)
{
if (!file_exists($path) OR (file_exists($path) && filetype($path) !== 'dir'))
{
trigger_error("Include path '{$path}' not exists", E_USER_WARNING);
continue;
}
$paths = explode(PATH_SEPARATOR, get_include_path());
if (array_search($path, $paths) === false)
array_push($paths, $path);
set_include_path(implode(PATH_SEPARATOR, $paths));
}
}
function remove_include_path ($path)
{
foreach (func_get_args() AS $path)
{
$paths = explode(PATH_SEPARATOR, get_include_path());
if (($k = array_search($path, $paths)) !== false)
unset($paths[$k]);
else
continue;
if (!count($paths))
{
trigger_error("Include path '{$path}' can not be removed because it is the only", E_USER_NOTICE);
continue;
}
set_include_path(implode(PATH_SEPARATOR, $paths));
}
}
?>
require()
require()문은 특정 파일을 인클루드하고, 적용시킨다.
require()문은 특정 파일을 인클루드하고, 적용시킨다. 이런 인클루드가 어떻게 동작하는지에 대한 자세한 정보는 include()에 대한 문서에서 설명한다.
require()와 include()는 수행 실패를 다루는 방법을 제외하고 완전히 동일합니다. 둘 모두 Warning을 발생시키지만, require()는 Fatal Error가 나타납니다. 즉, 파일이 없을 때 페이지 처리를 멈추고 싶으면 require()를 사용하면 됩니다. include()는 멈추지 않고 스크립트가 계속 실행됩니다. 또한, 적합한 include_path 설정인지 확인해야 합니다.
Example#1 기본적인 require() 사용예
<?php
require 'prepend.php';
require $somefile;
require ('somefile.txt');
?>
더 많은 예제 코드는 include()문서에서 볼수있다.
Note: PHP 4.0.2 이전 버전에서는 다음 규칙이 적용된다: require()는 어떤줄도 수행되지 않는 목적 파일도 무작정 읽어 들이려 한다. 조건절에서는 require()가 효과적이지 않다. 하지만, require() 되는 어떤 줄도 수행되지 않으면 목적 파일의 어떤 코드도 수행되지 않을것이다. 이와 유사하게, 루프 구조에서도 require()는 효과적이지 않다. 목적파일내에 포함된 코드가 계속 루프를 반복한다면, require()는 오직 한번만 발생한다.
Note: 이것은 함수가 아닌 언어 구조이기 때문에, 변수 함수 방식으로 호출할 수 없습니다.
Warning
PHP 4.3.0 이후의 Windows 버전 PHP에서는 이 함수를 이용하여 원격 파일에 접근할 수 없습니다. allow_url_fopen을 활성화하여도 마찬가지입니다.
참고: include(), require_once(), include_once(), get_included_files(), eval(), file(), readfile(), virtual(), include_path.
add a note
User Contributed Notesrequire
ricardo dot ferro at gmail dot com
14-May-2008 11:15
14-May-2008 11:15
Peter McDonald
15-Oct-2007 09:21
15-Oct-2007 09:21
re the comment by moazzamk at gmail dot com
As the manual states require and require_once as of PHP 4.02 no longer call the file if the line of code it is on should not be executed.
scott
20-Sep-2007 01:27
20-Sep-2007 01:27
If you want to verify that a file can be included or required, the simplest solution I've found is just to check that the file exists.
<?php
if(file_exists($pageContentInc)){
require_once $pageContentInc;
}else{
$pageContentInc = "common/content_404.inc";
require_once $pageContentInc;
}
?>
Does it really need to be any harder than that?
daniel at nohair dot com
06-Sep-2007 07:24
06-Sep-2007 07:24
I love php. But when file can't be included, 'require' or 'require_once' throw fatal error and halt the script, which is almost never desirable on a mission-critical production server. I think it may be better to use something like the following.
<?php
if (@include 'plan_A.php') {
// Plan A;
} elseif (@include 'plan_B.php') {
// Plan B;
} else {
// Hope never happens. If does, then Email the webmaster;
// Call 911, Medic, Fire, Police, the president;
// Change hard drive, server, hosting service;
}
?>
Or handle trouble first is you wish
<?php
if (!@include 'plan_A.php') {
// Someone has kidnapped/corrupted Plan_A.php;
// Email the webmaster;
// Change hard drive, server, hosting service;
} else {
// Plan A;
}
?>
moazzamk at gmail dot com
17-Jul-2007 08:51
17-Jul-2007 08:51
require and include read the included files even if they are not executed in the code. You can use eval() to avoid this.
eval('require filename;');
I don't know if it's faster to have the files included the regular way or the eval way though (in other words, I haven't tested their efficiency). It will be great if someone can test which is better.
some dot user at notarealdomain dot com
11-Jul-2007 07:58
11-Jul-2007 07:58
Discovered a bit of weird behavior yesterday involving require() (using PHP 5.2.3). If you use require() inside a function, the "globals" in the file will be local to the function. An example of this:
test.php:
<?php
function TestFunc()
{
require('test2.php');
echo "<pre>" . print_r($GLOBALS, true) . "</pre>";
}
?>
test2.php:
<?php
$MyTestGlobal = Array();
?>
This happens because require is a statement that _inlines_ the target code - not a function that gets called.
To fix this, use the $GLOBALS superglobal:
test2.php:
<?php
$GLOBALS["MyTestGlobal"] = Array();
?>
chris at chrisstockton dot org
19-Jun-2007 05:06
19-Jun-2007 05:06
Remember, when using require that it is a statement, not a function. It's not necessary to write:
<?php
require('somefile.php');
?>
The following:
<?php
require 'somefile.php';
?>
Is preferred, it will prevent your peers from giving you a hard time and a trivial conversation about what require really is.
31-Jan-2007 03:38
A note that drove me nuts for 2 days!
Be carfull if you have a newline or blank space befor your php tags in the included/required file it will read as html and outputed.
If your running your output through javascript string evaluations which would be sensitive to newlines/white spaces be carfull that the first chars in the file are the php tages eg <?php
bmessenger at 3servicesolution dot com
17-Oct-2006 01:06
17-Oct-2006 01:06
// Looks like I might have a fix for some on the
// relative path issue.
if (!function_exists('bugFixRequirePath'))
{
function bugFixRequirePath($newPath)
{
$stringPath = dirname(__FILE__);
if (strstr($stringPath,":")) $stringExplode = "\\";
else $stringExplode = "/";
$paths = explode($stringExplode,$stringPath);
$newPaths = explode("/",$newPath);
if (count($newPaths) > 0)
{
for($i=0;$i<count($newPaths);$i++)
{
if ($newPaths[$i] == "..") array_pop($paths);
}
for($i=0;$i<count($newPaths);$i++)
{
if ($newPaths[$i] == "..") unset($newPaths[$i]);
}
reset($newPaths);
$stringNewPath = implode($stringExplode,$paths).
$stringExplode.implode($stringExplode,$newPaths);
return $stringNewPath;
}
}
}
require_once(bugFixRequirePath("../config.php"));
gabe at websaviour dot com
13-Jul-2006 05:42
13-Jul-2006 05:42
If you are experiencing a bug related to using relative paths with include or require, it may be related to a grandparent directory that is executable but not readable. It will cause __FILE__ to return a relative path instead of the full path which it is supposed to show. This manifests itself in interesting ways that can be seemingly unrelated. For instance, I discovered it using the Smarty {debug} command which failed to find its template due to this issue. Please see the following for more details:
http://bugs.php.net/bug.php?id=34552
http://shiftmanager.net/~kurt/test/
Inc
31-May-2006 08:35
31-May-2006 08:35
I have found a problem when I try to access a php file via require($class_directory)
// # $class_directory contain a long full path and dot into the last folder.
// # $class_directory = "/var/.../app/system/plugintoto_1.0/class_plugintoto_1.0.php";
// dot ('.') and minus ('-') are not accepted in require !
tjeerd
11-May-2006 06:41
11-May-2006 06:41
When using symbolic links with PHP, specify a dotslash './page.php' path to ensure that PHP is looking in the right directory with nested requires:
E.g. when the required actual page1.php contains other require statements to, say page2.php, PHP will search the path that the symbolic link points to, instead of the path where the symbolic link lives. To let PHP find the other page2.php in the path of the symbolic link, a require('./page2.php'); statement will solve the puzzle.
webmaster at netgeekz dot net
24-Feb-2006 09:34
24-Feb-2006 09:34
I have learnt to manipulate this code into an effecitve and easy to use form. I use it with require_once, but it could be used for require.
require_once($_SERVER['DOCUMENT_ROOT'].'/includes/top.php');
This mainly jumps back to the servers document root and then begins to enter the directories defined until it finds the file. In this case it would go back to the root of the server, or whatever your document root is, and then enter includes. there it would search for the top.php file. Simple to use, yet effective...espcially for people like me who re-use code or move files to different directories. I don't have to fix the includes, because they all work the same way.
steve at walkerfx dot com
24-Feb-2006 03:24
24-Feb-2006 03:24
WARNING: Be absolutely sure that your include paths are relative or directory based and not http!!!
require("http://www.mydomain.com/somefile.php"); //WRONG!!
require("usr/mydomain/somefile.php"); //CORRECT!!
If you are intending to access local files and you accidentally use an http address, the request will probably work. However, this creates a wierd situation that can cause all sorts of bugs in your scripts and slow your code down.
The problem is that the include spawns off another php request, and is essentially requesting the file in the same a way a remote viewer would. So rather than including the intended php code, instead you get the processed output from that single file executed in its own private scope.
It's a simple mistake, but it can be an awful problem to debug.
Walker
dave at davidhbrown dot us
22-Jan-2006 12:08
22-Jan-2006 12:08
re: danielm at unb dot br...
$_SERVER['DOCUMENT_ROOT'] is very useful, but it is not available with all web servers. Apache has it; IIS doesn't.
I use the following to make my PHP applications work in more situations:
<?php
if (!defined("BASE_PATH")) define('BASE_PATH', isset($_SERVER['DOCUMENT_ROOT']) ? $_SERVER['DOCUMENT_ROOT'] : substr($_SERVER['PATH_TRANSLATED'],0, -1*strlen($_SERVER['SCRIPT_NAME'])));
?>
...but even that gets tripped up by symlinks to different mount points, etc. You could substitute realpath($_SERVER['PATH_TRANSLATED']), but that function has been reported not to work on some (Windows) servers. One could use the PATH_TRANSLATED for both servers, but I figure if Apache is going to tell me exactly what I want to know, I should listen.
tuxedobob at mac dot com
06-Jul-2005 11:54
06-Jul-2005 11:54
Something which may not be immediately obvious is that if you use double quotes on the filename, you can use variables to specify the filename, allowing you to do something like this:
<?php
$query = "SELECT filename FROM updates WHERE version>$current ORDER BY version";
$updateresult = mysql_query($query) or exit($query.'<br />'.mysql_error());
while ($updaterow = mysql_fetch_row($updateresult)) {
require "$updaterow[0]";
}
?>
Drop this in a script on a server and you can push updates to your clients. Obviously, make sure you only run scripts you want to.
Marc
06-May-2005 10:42
06-May-2005 10:42
This will sound elementary, but for C++ native programmers, be sure NOT to put a '#' in front of your include statements! The parser will not give you an error, but also will not include the file, making for a tedious debugging process.
In short, USE:
<?php
include "yourfile.php";
?>
and DON'T use:
<?php
#include "yourfile.php";
?>
richardbrenner(-at- )gmx(-)at
07-Apr-2005 01:58
07-Apr-2005 01:58
If you use relativ paths in a php script (file A) that can be required by another php script (file B), be aware that the relativ paths in file A will be relativ to the directory, where file B is stored.
You can use the following syntax in file A, to be sure that the paths are relativ to the directory of file A:
<?
require(dirname(__FILE__)."/path/relative/file_to_include.php");
?>
Greetings,
Richard
10-Feb-2005 10:29
Note when calling any require or include function, that the call will block if the script given as the parameter is excecuting.
Because of this one should be careful when using blocking functions like sleep() in a script which is included by another.
danielm at unb dot br
21-Nov-2004 11:50
21-Nov-2004 11:50
if you want to include files with an absolut path reference, you can use:
require ($_SERVER["DOCUMENT_ROOT"]."/path/to/file.php");
this way you can organize your files in subdirectories trees.