mod rewrite test faied on 000webhost

  • i know there are other forms out there but 000webhost claims that it is enabled. 

  • do u just rename htaccess_dist to .htaccess and it lets you go to the next step?

  • Read all they write in their FAQ:

    We use virtual user home directory paths, so you may get errors when trying to set up search engine friendly URL's. All you need to do to fix this issue is add the below line to the very top of your .htaccess file:

    RewriteBase /

    Make sure this line is placed before all the other rules (on the first line of .htaccess file). That's it. Now your rewrite rules will be working fine.

    Note: if you are installing your script to some directory such as www.yourdomain.com/forum/, you have to place RewriteBase /forum/ line to the .htaccess file which also must be located in public_html/forum/ directory.

  • In docs, it says to rename htaccess_dist to .htaccess.

    But, after Ben claims he did it, the Next button isn't showing up.

  • You only need to create .htaccess on your own (using htaccess_dist) if Elgg can't create it itself. The main reason creation of .htaccess fails is due to permission issues.

    But...

    In case of this installation something else seems not alright as there are the errors shown above:

    • the webhoster might claim that mod_rewrite is enabled, but you might want to verify if that's true (http://docs.elgg.org/wiki/Mod_rewrite_test),
    • you also might want to make sure (ask the webhoster support) if "AllowOverride All" is set for the Elgg install directory,
    • open_basedir directive set? Ask your webhoster,
    • "curl" package installed? If not, this might be the reason why the mod_rewrite test of Elgg fails.
    • If you have created .htaccess on your own, have you set RewriteBase in .htaccess to match your installation location (either uncommented "/" to see if this works better or set it to the correct subdirectory if you are installing Elgg into a subdirectory),
    • http://docs.elgg.org/wiki/Install_Troubleshooting.
  • DO NOT SET PERMISSIONS OF THE ELGG ROOT DIRECTORY (PUBLIC_HTML) OR ANY SUBDIRECTORIES OF THIS FOLDER TO PERMISSIONS 777!!!!!!!!!!!!!!!!

    Permissions 777 for public_html or anything inside this folder will allow EVERYONE to modify what's inside this folder via Internet. There're nowhere any instructions to set the Elgg root folder to 777 but only the data folder which needs to be OUTSIDE the document root folder / Elgg root folder (what's exposed to the Internet).

    "We think your server is running the Apache web server"

    This is only a neutral statement and does not mean there's any problem with using Apache (on the contrary Apache is the only webserver officially suggested for Elgg). It only means Elgg thinks that Apache is used and therefore the issues listed in the following are the likely causes why Elgg can't be installed properly. In case Elgg is wrong in the first place in guessing that Apache is used the following possible causes are less likely - but then you need to figure out on your own what might be to do.

    But if you use Apache on your server and Elgg does not properly install I would suggest to try solving the issues listed by Elgg first and not trying to make any other changes that are neither listed nor adviceable.