and let’s assume the following content of Bar.php:
// Bar.phpnamespaceOtherDir;useSomeDir\Foo;// This now conflicts the class OtherDir\Foo
If both files OtherDir/Foo.php and SomeDir/Foo.php are loaded in the
same runtime, you will see a PHP error such as the following:
PHP Fatal error: Cannot use SomeDir\Foo as Foo because the name is already in use in OtherDir/Foo.php
However, as OtherDir/Foo.php does not necessarily have to be loaded and the
error is only triggered if it is loaded before OtherDir/Bar.php, this problem
might go unnoticed for a while. In order to prevent this error from surfacing,
you must import the namespace with a different alias:
// Bar.phpnamespaceOtherDir;useSomeDir\FooasSomeDirFoo;// There is no conflict anymore.
Loading history...
4
5
/**
6
* Elgg Installer.
7
* Controller for installing Elgg. Supports both web-based on CLI installation.
8
*
9
* This controller steps the user through the install process. The method for
10
* each step handles both the GET and POST requests. There is no XSS/CSRF protection
11
* on the POST processing since the installer is only run once by the administrator.
12
*
13
* The installation process can be resumed by hitting the first page. The installer
14
* will try to figure out where to pick up again.
15
*
16
* All the logic for the installation process is in this class, but it depends on
17
* the core libraries. To do this, we selectively load a subset of the core libraries
18
* for the first few steps and then load the entire engine once the database and
19
* site settings are configured. In addition, this controller does its own session
20
* handling until the database is setup.
21
*
22
* There is an aborted attempt in the code at creating the data directory for
23
* users as a subdirectory of Elgg's root. The idea was to protect this directory
24
* through a .htaccess file. The problem is that a malicious user can upload a
25
* .htaccess of his own that overrides the protection for his user directory. The
26
* best solution is server level configuration that turns off AllowOverride for the
27
* data directory. See ticket #3453 for discussion on this.
Elgg /
Elgg
Evan Winslow
Ismayil Khayredinov
Let’s assume that you have a directory layout like this:
. |-- OtherDir | |-- Bar.php | `-- Foo.php `-- SomeDir `-- Foo.phpand let’s assume the following content of
Bar.php:If both files
OtherDir/Foo.phpandSomeDir/Foo.phpare loaded in the same runtime, you will see a PHP error such as the following:PHP Fatal error: Cannot use SomeDir\Foo as Foo because the name is already in use in OtherDir/Foo.phpHowever, as
OtherDir/Foo.phpdoes not necessarily have to be loaded and the error is only triggered if it is loaded beforeOtherDir/Bar.php, this problem might go unnoticed for a while. In order to prevent this error from surfacing, you must import the namespace with a different alias: