I get the message
We think your server is running the Apache web server.
The rewrite test failed and the most likely cause is that AllowOverride is not set to All for Elgg's directory. This prevents Apache from processing the .htaccess file which contains the rewrite rules.
A less likely cause is Apache is configured with an alias for your Elgg directory and you need to set the RewriteBase in your .htaccess. There are further instructions in the .htaccess file in your Elgg directory.
I have tested out the url rewriting using the rewrite.php file. This doesnt work until I add the "RewriteBase /" into the .htaccess file. One this is configured it works fine but I still get the install error. Where do I go next to find out why it the install rewrite tests fail? Easyspace assure me allowOverride all is set for all directories, which makes sense as the change I make to the RewriteBase is being picked up. Im just not sure where to go from here.
Thanks.
Colin
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
- Colin Downes@d0wn5ey
Colin Downes - 0 likes
- Javier Zambrana@Aporta
Javier Zambrana - 0 likes
- Colin Downes@d0wn5ey
Colin Downes - 0 likes
- Colin Downes@d0wn5ey
Colin Downes - 0 likes
- Brett@brett.profitt
Brett - 0 likes
- Arsalan Shah@arsalanlee
Arsalan Shah - 0 likes
You must log in to post replies.Should have included version ...v1.8 b2.
Hi Colin:
Give me more details. If you have installed elgg in a folder within the root directory, make sure the file. Htaccess RewriteBase look like this:
RewriteBase / tu: _carperta /
Greetings.
Hi Javier,
Thanks for your response. Elgg is in the root directory so I get to it by http://www.myserver.com. I think that the rewrite rules are working because when I open http://www.myserver.com/rewrite.php I get a success message.
Im currently trying to debug ElggRewriteTester.php to see where it is going wrong....
I think what is happening is that in apache Curl is installed, but it has been turned off in config with '--without-curl' (shown in configure command when running phpinfo).
So when the installer tries the curl test (after checking function_exists('curl_init')) it doesnt pick up the fact that it has been disabled.... at least thats what I think....
@Colin - The installer checks if curl is available, then tries sockets, then finally bails with an error saying it can't tell. I don't think that curl will report as available if it's been disabled. You can force it to report true by altering that function if you want, but it's possible there are other problems with the server config...
@Brett how are you?
@Colin Downes download http://community.elgg.org/pg/plugins/project/713214/developer/arsalanlee/requirements-check