A note on settings.php and .htaccess
The Elgg installer will try to create two files for you:
elgg-config/settings.php, which contains local environment configuration for your installation
.htaccess, which allows Elgg to generate dynamic URLs
If these files can’t be automatically generated, for example because the web server doesn’t have write permissions in the directories, Elgg will tell you how to create them. You could also temporarily change the permissions on the root directory and the engine directory. Set the permissions on those two directories so that the web server can write those two files, complete the install process, and them change the permissions back to their original settings. If, for some reason, this won’t work, you will need to:
In elgg-config/, copy settings.example.php to settings.php, open it up in a text editor and fill in your database details
On Apache server, copy install/config/htaccess.dist to .htaccess
On Nginx server copy install/config/nginx.dist to /etc/nginx/sites-enabled and adjust it’s contents
Other Configurations
Cloud9
Homestead
EasyPHP
IIS
MAMP
MariaDB
Nginx
Ubuntu
Virtual hosts
XAMPP
Troubleshooting
Help! I’m having trouble installing Elgg
First:
Recheck that your server meets the technical requirements for Elgg.
Follow the environment-specific instructions if need be
Have you verified that mod_rewrite is being loaded?
Is the mysql apache being loaded?
Keep notes on steps that you take to fix the install. Sometimes changing some setting or file to try to fix a problem may cause some other problem later on. If you need to start over, just delete all the files, drop your database, and begin again.
I can’t save my settings on installation (I get a 404 error when saving settings)
Elgg relies on the mod_rewrite Apache extension in order to simulate certain URLs. For example, whenever you perform an action in Elgg, or when you visit a user’s profile, the URL is translated by the server into something Elgg understands internally. This is done using rules defined in an .htaccess file, which is Apache’s standard way of defining extra configuration for a site.
This error suggests that the mod_rewrite rules aren’t being picked up correctly. This may be for several reasons. If you’re not comfortable implementing the solutions provided below, we strongly recommend that you contact your system administrator or technical support and forward this page to them.
The .htaccess, if not generated automatically (that happens when you have problem with mod_rewrite), you can create it by renaming install/config/htaccess.dist file you find with elgg package to .htaccess. Also if you find a .htaccess file inside the installation path, but you are still getting 404 error, make sure the contents of .htaccess are same as that of install/config/htaccess.dist.
``mod_rewrite`` isn’t installed.
The Elgg installer will try to create two files for you:
elgg-config/settings.php, which contains local environment configuration for your installation
.htaccess, which allows Elgg to generate dynamic URLs
If these files can’t be automatically generated, for example because the web server doesn’t have write permissions in the directories, Elgg will tell you how to create them. You could also temporarily change the permissions on the root directory and the engine directory. Set the permissions on those two directories so that the web server can write those two files, complete the install process, and them change the permissions back to their original settings. If, for some reason, this won’t work, you will need to:
In elgg-config/, copy settings.example.php to settings.php, open it up in a text editor and fill in your database details
On Apache server, copy install/config/htaccess.dist to .htaccess
On Nginx server copy install/config/nginx.dist to /etc/nginx/sites-enabled and adjust it’s contents
Other Configurations
Cloud9
Homestead
EasyPHP
IIS
MAMP
MariaDB
Nginx
Ubuntu
Virtual hosts
XAMPP
Troubleshooting
Help! I’m having trouble installing Elgg
First:
Recheck that your server meets the technical requirements for Elgg.
Follow the environment-specific instructions if need be
Have you verified that mod_rewrite is being loaded?
Is the mysql apache being loaded?
Keep notes on steps that you take to fix the install. Sometimes changing some setting or file to try to fix a problem may cause some other problem later on. If you need to start over, just delete all the files, drop your database, and begin again.
I can’t save my settings on installation (I get a 404 error when saving settings)
Elgg relies on the mod_rewrite Apache extension in order to simulate certain URLs. For example, whenever you perform an action in Elgg, or when you visit a user’s profile, the URL is translated by the server into something Elgg understands internally. This is done using rules defined in an .htaccess file, which is Apache’s standard way of defining extra configuration for a site.
This error suggests that the mod_rewrite rules aren’t being picked up correctly. This may be for several reasons. If you’re not comfortable implementing the solutions provided below, we strongly recommend that you contact your system administrator or technical support and forward this page to them.
The .htaccess, if not generated automatically (that happens when you have problem with mod_rewrite), you can create it by renaming install/config/htaccess.dist file you find with elgg package to .htaccess. Also if you find a .htaccess file inside the installation path, but you are still getting 404 error, make sure the contents of .htaccess are same as that of install/config/htaccess.dist.
``mod_rewrite`` isn’t installed.
https://pylong.com/post/XerKifol