Elgg Install: Requirements Check Issue - htaccess

When installing Elgg 1.8.0.1, I got the following message:

image

I can't find any information about how to fix this error. Please help. Thanks

  • The installer thinks you have an .htaccess file from a previous version of Elgg in the root directory.

  • I had Elgg 1.7.12 installed but I was having problems with it so I installed 1.8.0.1. I removed all the previous files. I tried deleting the .htaccess file and re-installing it. What do I do?

  • I installed 1.8.0.1 locally about a week ago on my macbook. My .htaccess for 1.8.0.1 looks like this. I  added the following to my apache2/httpd.conf and apache2/users/[usersname].conf (must also configure user otherwise it overrides httpd.conf) and enabled mod_rewrite.

    <Directory "/path/to/http/root/">
        Options Indexes MultiViews FollowSymLinks
        AllowOverride All
        Order allow,deny
        Allow from all
    </Directory>

    I installed elgg to /path/to/http/root/elgg/html/ and data at /path/to/http/root/elgg/data/

    Youll also need to check/set the permissions on elgghtmldir and elggdatadir. I think that's all i did to set it up (other than database). Hope it helps.

  • I really do not know anything about coding. Can you (or anyone) please be more clear on how exactly to fix this issue??

  • Delete .htaccess

    It may be hidden on your server since it begins with a .

  • i tried deleting htaccess_dist but that didnt work so I reuploaded it and renamed it .htaccess and that worked.

    Now I am on step 4. Configure site and it is saying "Your data directory /root/data/ does not exist."

    It exists, the location is correct. How do I fix this?

  • The permissions of the directory might not allow the apache webserver to access this directory. I think /root/data is in the home directory of the root user account (at least in Linux it is), so the read/write permissions might be for the root user only. It might be better to create the data directory not in the /root directory and you also need to set the read/write permissions to 777, i.e. permissions for the owner, the group and others to read/write to this directory, or at least to allow read/write access for the user account the webserver is running as.