search
HomeBackend DevelopmentPHP TutorialBe careful about php require_once usage and relative directories_PHP Tutorial

Be careful about php require_once usage and relative directories_PHP Tutorial

Jul 13, 2016 am 10:56 AM
oncephprequireandexistdeveloparticleusageTable of contentsrelativelywant

The article introduces the usage of require_once that everyone often encounters in PHP development. Friends in need can refer to it.

wwwroot //Website root directory. The absolute path is: F:/wwwroot

-- folder_a // Folder A

file_a_a.php

file_a_b.php

file_a_c.php

-- folder_b // Folder B

file_b_a.php

file_b_b.php

file_b_c.php

-- index.php

**************************************************** ******************

This directory hierarchy is already very clear:

wwwroot is the root directory, below which there is the index.php file and two folders folder_a and folder_b

These two folders each have 3 php files

Let’s first look at the contents of the index.php file:

The code is as follows Copy code
 代码如下 复制代码

     require_once("folder_a/file_a_a.php");

     echo "文件folder_a_a.php被包含成功";

?>

require_once("folder_a/file_a_a.php");
 代码如下 复制代码

     require_once("../folder_b/file_b_a.php");

     $x = new X();

     $x.printInfo();

?>

echo "The file folder_a_a.php was included successfully";

 代码如下 复制代码

     class X{

          function printInfo(){

               echo 'success;

          }

     }

?>

?>
Look at the contents of the folder_a/folder_a_a.php file:
The code is as follows Copy code
require_once("../folder_b/file_b_a.php"); $x = new X(); $x.printInfo(); ?>
Finally, let’s take a look at the contents of the folder_b/folder_b_a.php file:
The code is as follows Copy code
class X{ function printInfo(){ echo 'success; } } ?>

ok if I run floder_a/file_a_a.php directly now

Then it will output: success

If I run index.php under wwwroot

Then an error will be reported because the included file cannot be found: file_b_a.php

But if I add dirname(__FILE__).'/'

to all require_once()

Then no matter you run file_a_a.php or index.php, the output will be normal

**************************************************** **********

Question:

The first time I used a relative path, so an error occurred when I included it repeatedly

The second time I used the absolute path, so there was no error. But I am still a little confused:

I first analyzed the following reasons why using relative paths will cause errors:

I run index.php, it can find the folder_a directory and file_a_a.php in that directory, so it copies the contents of folder_a/file_a_a.php to the first line of index.php (including the statement line), and then continue to run (that is, run the included content), so this is equivalent to running require_once('../folder_b/file_b_a.php'); in file_a_a.php in index.php. Find this path file (file_b_a.php) based on the current location of index.php, but of course it can’t be found, so it’s an error.

But isn’t it the same when I use absolute paths? But why doesn’t it go wrong? Maybe everyone is a little confused about this sentence, let me explain it in detail (according to the running order of the program).

The program first runs index.php (note that I added dirname(__FILE__) at this time, so the current path is absolute),

index.php first runs the first line of code: require_once(dirname(__FILE__).'/'.'folder_a/file_a_a.php');

dirname(__FILE__) is f:/wwwroot/, so the path contained in this code is:

f:/wwwroot/folder_a/file_a_a.php

This path is correct, so it’s no problem, right

ok the first step is completed correctly

Then it copies the code in file_a_a.php to this location in index.php:

Then it still continues to run: This is to run all the code in file_a_a.php in index.php, so let’s see what code it runs?

The code is as follows Copy code
 代码如下 复制代码

     require_once(dirname(__FILE__).'/'."../folder_b/file_b_a.php");

     $x = new X();

     $x.printInfo();

?>

require_once(dirname(__FILE__).'/'."../folder_b/file_b_a.php");
 代码如下 复制代码

     require_once(dirname(__FILE__).'/'."../folder_b/file_b_a.php");

     $x = new X();

     $x.printInfo();

     echo "文件folder_a_a.php被包含成功";

?>

$x = new X();

$x.printInfo();

?>
 代码如下 复制代码

c.php

require_once("a.php");
require_once("demo/b.php");
B::demo();a.php
class A
{
}

Yes, that’s it. It should be noted that these codes have been copied to index.php, that is to say, the content of index.php now actually becomes:
The code is as follows Copy code
require_once(dirname(__FILE__).'/'."../folder_b/file_b_a.php"); $x = new X(); $x.printInfo(); echo "The file folder_a_a.php was included successfully"; ?>
Let’s take a look at some things to note Suppose there are the following three files, c.php a.php b.php and the corresponding storage directory is: localhost/ localhost/ localhost/demo
The code is as follows Copy code
c.php require_once("a.php"); require_once("demo/b.php"); B::demo();a.php class A { }

The content of b.php is more interesting, because it inherits CLASS A, so I also introduced a.php into it

The code is as follows
 代码如下 复制代码

require_once("../a.php");
class B extends A
{
    public static function demo()
    {
    echo "xx";
    }
}

Copy code



require_once("../a.php");
class B extends A {
 代码如下 复制代码

require_once("a.php");
require_once("../a.php");
class B extends A
{
    public static function demo()
    {
    echo "xx";
    }
}
B::demo();

Public static function demo()

{
echo "xx";

}

}

The system reports an error when executing localhost/c.php. The error message is as follows Warning: require_once(../a.php) [function.require-once]: failed to open stream: No such file or directory in F:wwwdemob.php on line 2

Fatal error: require_once() [function.require]: Failed opening required '../a.php' (include_path='.;C:php5pear') in F:wwwdemob.php on line 2 However, I was surprised to find that if Remove the require_once statement in b.php and the execution is normal. So there must be too many require_once statements defined? The reason is that Class A was redefined twice? But no. If I only add require_once(‘a.php’); to c.php, it will be correct even if I write it twice. So what’s going on?

The reason is that the directory level defined by b.php is inconsistent with the directory level of the c.php execution file, resulting in two require_once statements in c.php. Make it equivalent to
Statement
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn
The Continued Use of PHP: Reasons for Its EnduranceThe Continued Use of PHP: Reasons for Its EnduranceApr 19, 2025 am 12:23 AM

What’s still popular is the ease of use, flexibility and a strong ecosystem. 1) Ease of use and simple syntax make it the first choice for beginners. 2) Closely integrated with web development, excellent interaction with HTTP requests and database. 3) The huge ecosystem provides a wealth of tools and libraries. 4) Active community and open source nature adapts them to new needs and technology trends.

PHP and Python: Exploring Their Similarities and DifferencesPHP and Python: Exploring Their Similarities and DifferencesApr 19, 2025 am 12:21 AM

PHP and Python are both high-level programming languages ​​that are widely used in web development, data processing and automation tasks. 1.PHP is often used to build dynamic websites and content management systems, while Python is often used to build web frameworks and data science. 2.PHP uses echo to output content, Python uses print. 3. Both support object-oriented programming, but the syntax and keywords are different. 4. PHP supports weak type conversion, while Python is more stringent. 5. PHP performance optimization includes using OPcache and asynchronous programming, while Python uses cProfile and asynchronous programming.

PHP and Python: Different Paradigms ExplainedPHP and Python: Different Paradigms ExplainedApr 18, 2025 am 12:26 AM

PHP is mainly procedural programming, but also supports object-oriented programming (OOP); Python supports a variety of paradigms, including OOP, functional and procedural programming. PHP is suitable for web development, and Python is suitable for a variety of applications such as data analysis and machine learning.

PHP and Python: A Deep Dive into Their HistoryPHP and Python: A Deep Dive into Their HistoryApr 18, 2025 am 12:25 AM

PHP originated in 1994 and was developed by RasmusLerdorf. It was originally used to track website visitors and gradually evolved into a server-side scripting language and was widely used in web development. Python was developed by Guidovan Rossum in the late 1980s and was first released in 1991. It emphasizes code readability and simplicity, and is suitable for scientific computing, data analysis and other fields.

Choosing Between PHP and Python: A GuideChoosing Between PHP and Python: A GuideApr 18, 2025 am 12:24 AM

PHP is suitable for web development and rapid prototyping, and Python is suitable for data science and machine learning. 1.PHP is used for dynamic web development, with simple syntax and suitable for rapid development. 2. Python has concise syntax, is suitable for multiple fields, and has a strong library ecosystem.

PHP and Frameworks: Modernizing the LanguagePHP and Frameworks: Modernizing the LanguageApr 18, 2025 am 12:14 AM

PHP remains important in the modernization process because it supports a large number of websites and applications and adapts to development needs through frameworks. 1.PHP7 improves performance and introduces new features. 2. Modern frameworks such as Laravel, Symfony and CodeIgniter simplify development and improve code quality. 3. Performance optimization and best practices further improve application efficiency.

PHP's Impact: Web Development and BeyondPHP's Impact: Web Development and BeyondApr 18, 2025 am 12:10 AM

PHPhassignificantlyimpactedwebdevelopmentandextendsbeyondit.1)ItpowersmajorplatformslikeWordPressandexcelsindatabaseinteractions.2)PHP'sadaptabilityallowsittoscaleforlargeapplicationsusingframeworkslikeLaravel.3)Beyondweb,PHPisusedincommand-linescrip

How does PHP type hinting work, including scalar types, return types, union types, and nullable types?How does PHP type hinting work, including scalar types, return types, union types, and nullable types?Apr 17, 2025 am 12:25 AM

PHP type prompts to improve code quality and readability. 1) Scalar type tips: Since PHP7.0, basic data types are allowed to be specified in function parameters, such as int, float, etc. 2) Return type prompt: Ensure the consistency of the function return value type. 3) Union type prompt: Since PHP8.0, multiple types are allowed to be specified in function parameters or return values. 4) Nullable type prompt: Allows to include null values ​​and handle functions that may return null values.

See all articles

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

Video Face Swap

Video Face Swap

Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Tools

Atom editor mac version download

Atom editor mac version download

The most popular open source editor

SublimeText3 Linux new version

SublimeText3 Linux new version

SublimeText3 Linux latest version

mPDF

mPDF

mPDF is a PHP library that can generate PDF files from UTF-8 encoded HTML. The original author, Ian Back, wrote mPDF to output PDF files "on the fly" from his website and handle different languages. It is slower than original scripts like HTML2FPDF and produces larger files when using Unicode fonts, but supports CSS styles etc. and has a lot of enhancements. Supports almost all languages, including RTL (Arabic and Hebrew) and CJK (Chinese, Japanese and Korean). Supports nested block-level elements (such as P, DIV),

Zend Studio 13.0.1

Zend Studio 13.0.1

Powerful PHP integrated development environment

SecLists

SecLists

SecLists is the ultimate security tester's companion. It is a collection of various types of lists that are frequently used during security assessments, all in one place. SecLists helps make security testing more efficient and productive by conveniently providing all the lists a security tester might need. List types include usernames, passwords, URLs, fuzzing payloads, sensitive data patterns, web shells, and more. The tester can simply pull this repository onto a new test machine and he will have access to every type of list he needs.