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...
5
use Elgg\Application;
6
use Elgg\Config;
7
use Elgg\Database\DbConfig;
8
use Elgg\Project\Paths;
9
use Elgg\Di\ServiceProvider;
10
use Elgg\Http\Request;
11
12
/**
13
* Elgg Installer.
14
* Controller for installing Elgg. Supports both web-based on CLI installation.
15
*
16
* This controller steps the user through the install process. The method for
17
* each step handles both the GET and POST requests. There is no XSS/CSRF protection
18
* on the POST processing since the installer is only run once by the administrator.
19
*
20
* The installation process can be resumed by hitting the first page. The installer
21
* will try to figure out where to pick up again.
22
*
23
* All the logic for the installation process is in this class, but it depends on
24
* the core libraries. To do this, we selectively load a subset of the core libraries
25
* for the first few steps and then load the entire engine once the database and
26
* site settings are configured. In addition, this controller does its own session
27
* handling until the database is setup.
28
*
29
* There is an aborted attempt in the code at creating the data directory for
30
* users as a subdirectory of Elgg's root. The idea was to protect this directory
31
* through a .htaccess file. The problem is that a malicious user can upload a
32
* .htaccess of his own that overrides the protection for his user directory. The
33
* best solution is server level configuration that turns off AllowOverride for the
34
* data directory. See ticket #3453 for discussion on this.
35
*/
36
class ElggInstaller {
37
38
private $steps = [
39
'welcome',
40
'requirements',
41
'database',
42
'settings',
43
'admin',
44
'complete',
45
];
46
47
private $has_completed = [
48
'config' => false,
49
'database' => false,
50
'settings' => false,
51
'admin' => false,
52
];
53
54
private $is_action = false;
55
56
private $autoLogin = true;
57
58
/**
59
* @var Application
60
*/
61
private $app;
62
63
/**
64
* Dispatches a request to one of the step controllers
Elgg /
Elgg
Evan Winslow
Ismayil Khayredinov
Steve Clay
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: