A slightly better no-settings error. It's probably a good idea to eventually allow people to edit settings.php directly if they have the access defined.

git-svn-id: https://code.elgg.org/elgg/trunk@13 36083f99-b078-4883-b0ff-0f9b5a30f544

2 files changed, 9 insertions, 3 deletions

diff --git a/engine/start.php b/engine/start.php
index 54e3fecf5..81edfb905 100644
--- a/engine/start.php
+++ b/engine/start.php
@@ -67,8 +67,12 @@
 					register_error("Could not load {$file}");

 			}

 		

-		}	// End portion for sanitised installs only

+		} else {	// End portion for sanitised installs only

 			

+			register_error("Once you've corrected any configuration issues, press reload to try again.");

+			

+		}

+		

 		// Trigger events

 			trigger_event('init', 'system');

 		

diff --git a/views/default/messages/sanitisation/settings.php b/views/default/messages/sanitisation/settings.php
index e49f07b7a..539598320 100644
--- a/views/default/messages/sanitisation/settings.php
+++ b/views/default/messages/sanitisation/settings.php
@@ -13,6 +13,8 @@
 	 */

 

 ?>

-Elgg couldn't find its settings file.  This is normally located in engine/settings.php.

+Elgg couldn't find its settings file. Most of Elgg's settings will be handled for you, but we need you to supply your database details. To do this:

 

-This probably means you haven't configured Elgg yet!  Some message about installing Elgg to go right about here.
\ No newline at end of file
+1. Rename engine/settings.example.php to settings.php in your Elgg installation.

+

+2. Open it with a text editor and enter your MySQL database details. If you don't know these, ask your system administrator or technical support for help.  
\ No newline at end of file