Hi all htaccess file problem

By Tom

I have a problem with the server 1and1 you see I can not install Elgg
and I suspect it was my htaccess, but I do not know how to set it on other servers installed with no problem and this is not going to thank you in advance for any help

Sorry for my english
That is my htaccess
------------------------

# Elgg htaccess directives
# Copyright Curverider Ltd 2008-2009
# License http://www.gnu.org/licenses/old-licenses/gpl-2.0.html GNU Public License version 2
# Link http://elgg.org/

<Files "htaccess">
order allow,deny
deny from all
</Files>

# Don't listing directory
Options -Indexes

# Follow symbolic links
Options +FollowSymLinks

# Default handler
DirectoryIndex index.php

# Turn on expiry
<IfModule mod_expires.c>
ExpiresActive On
ExpiresDefault "access plus 10 years"
</IfModule>

# php 5, apache 1 and 2
<IfModule mod_php5.c>
# default memory limit to 64Mb
php_value memory_limit 64M
# to make sure register global is off
php_value register_globals 0
# max post size to 8Mb
php_value post_max_size 8388608
# upload size limit to 5Mb
php_value upload_max_filesize 5242880
# hide errors, enable only if debug enabled
php_value display_errors 0
</IfModule>

# Turn on mod_gzip if available
<IfModule mod_gzip.c>
mod_gzip_on yes
mod_gzip_dechunk yes
mod_gzip_keep_workfiles No
mod_gzip_minimum_file_size 1000
mod_gzip_maximum_file_size 1000000
mod_gzip_maximum_inmem_size 1000000
mod_gzip_item_include mime ^text/.*
mod_gzip_item_include mime ^application/javascript$
mod_gzip_item_include mime ^application/x-javascript$
# Exclude old browsers and images since IE has trouble with this
mod_gzip_item_exclude reqheader "User-Agent: .*Mozilla/4\..*\["
mod_gzip_item_exclude mime ^image/.*
</IfModule>

## Apache2 deflate support if available
##
## Important note: mod_headers is required for correct functioning across proxies.
##
<IfModule mod_deflate.c>
AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/x-javascript
BrowserMatch ^Mozilla/4 gzip-only-text/html
BrowserMatch ^Mozilla/4\.[0678] no-gzip
BrowserMatch \bMSIE !no-gzip

<IfModule mod_headers.c>
Header append Vary User-Agent env=!dont-vary
</IfModule>

# The following is to disable compression for actions. The reason being is that these
# may offer direct downloads which (since the initial request comes in as text/html and headers
# get changed in the script) get double compressed and become unusable when downloaded by IE.
SetEnvIfNoCase Request_URI action\/* no-gzip dont-vary
SetEnvIfNoCase Request_URI actions\/* no-gzip dont-vary

</IfModule>

# Configure ETags
<FilesMatch "\.(jpg|jpeg|gif|png|mp3|flv|mov|avi|3pg|html|htm|swf)$">
FileETag MTime Size
</FilesMatch>

<IfModule mod_rewrite.c>

RewriteEngine on

# If Elgg is in a subdirectory on your site, you might need to add a RewriteBase line
# containing the path from your site root to elgg's root. e.g. If your site is
# http://example.com/ and Elgg is in http://example.com/sites/elgg/, you might need
#
#RewriteBase /sites/elgg/
#
# here, only without the # in front.
#
# If you're not running Elgg in a subdirectory on your site, but still getting lots
# of 404 errors beyond the front page, you could instead try:
#
#RewriteBase /

RewriteRule ^action\/([A-Za-z0-9\_\-\/]+)$ engine/handlers/action_handler.php?action=$1&%{QUERY_STRING}

RewriteRule ^services\/api\/([A-Za-z0-9\_\-]+)\/(.*)$ engine/handlers/service_handler.php?handler=$1&request=$2&%{QUERY_STRING}

RewriteRule ^export\/([A-Za-z]+)\/([0-9]+)$ services/export/handler.php?view=$1&guid=$2
RewriteRule ^export\/([A-Za-z]+)\/([0-9]+)\/$ services/export/handler.php?view=$1&guid=$2
RewriteRule ^export\/([A-Za-z]+)\/([0-9]+)\/([A-Za-z]+)\/([A-Za-z0-9\_]+)\/$ services/export/handler.php?view=$1&guid=$2&type=$3&idname=$4

RewriteRule ^\_css\/css\.css$ _css/css.php

RewriteRule ^pg\/([A-Za-z0-9\_\-]+)\/(.*)$ engine/handlers/pagehandler.php?handler=$1&page=$2&%{QUERY_STRING}
RewriteRule ^pg\/([A-Za-z0-9\_\-]+)$ engine/handlers/pagehandler.php?handler=$1&%{QUERY_STRING}

RewriteRule xml-rpc.php engine/handlers/xml-rpc_handler.php
RewriteRule mt/mt-xmlrpc.cgi engine/handlers/xml-rpc_handler.php

RewriteRule ^tag/(.+)/?$ engine/handlers/pagehandler.php?handler=search&page=$1

</IfModule>

And this error after the installation is finished

Not Found
The requested URL /kunden/homepages/37/d344360624/htdocs/elg/engine/handlers/action_handler.php was not found on this server.


Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
 --------------

Once again, thank you for any help

  • The URL is probably wrong. I recommend deleting settings.php, dumping your database and starting over. When you get to the settings screen, check your site URL very carefully. If that is not the issue, then it is a rewrite problem.

    Documentation: http://docs.elgg.org/wiki/Install_Troubleshooting

  • Hi still nothing has changed the same error
    This view is

    System settings

    The site URL, followed by a trailing slash:
    http://www.likesports.pl/homepages/37/d344360624/htdocs/elg/
    -------------------------------------------------------
    The full path to your site root on your disk, followed by a trailing slash:
    /homepages/37/d344360624/htdocs/elg/
    -----------------------------------------
    The full path to the directory where uploaded files will be stored, followed by a trailing slash:
    /homepages/37/d344360624/htdocs/dane/

     

    a htaccess file looks identical to the above, and really have no idea what's going on

  • Like I said. That's probably the wrong URL. I'm guessing it should be http://www.likesport.pl/elg/ without the stuff in the middle. This is covered in the troubleshooting guide.

  • I have done so

    The site URL, followed by a trailing slash:
    http://www.likesports.pl/elg/

    The full path to your site root on your disk, followed by a trailing slash:
    /homepages/elg/

    The full path to the directory where uploaded files will be stored, followed by a trailing slash:
    /homepages/dane/

    Such an error

     

    Not Found
    The requested URL /kunden/homepages/37/d344360624/htdocs/elg/engine/handlers/action_handler.php was not found on this server.


    Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

    Now that I have no idea at all what's going on

  • You might have to start the installation again with a new and empty database as the wrong site URL might not be changeable once you have entered it. http://www.likesports.pl/elg/ (or elgg at the end?) seems right. For path to site root and path to data directory the full path might be needed, i.e. /homepages/37/d344360624/htdocs/elg/ and /homepages/37/d344360624/htdocs/dane/. Additionally, it could be necessary to enter the correct subdirectory in .htaccess:

    # If Elgg is in a subdirectory on your site, you might need to add a RewriteBase line
    # containing the path from your site root to elgg's root. e.g. If your site is
    # http://example.com/ and Elgg is in http://example.com/sites/elgg/, you might need
    #
    #RewriteBase /sites/elgg/

    For your site this would be

    RewriteBase /elg/

    or

    RewriteBase /elgg/

    depending on how many "g" you have used for your directory name.

     

  • Unfortunately, none of these options do not match, the database for each installation, I assume a new, unfortunately, I treated the whole day in August when a pity that one installation in 1and1 hosting is so difficult to other servers installed with no problem.
    So everything boils down to the # RewriteBase? or even to something else?
    Or maybe someone will install on my server and check if at all 1and 1 is suitable for Elgg, at least found out what's really going on
    Yours

  • I'm not sure if your assumption that the database is new each time is true. If you don't recreate the database yourself in CPanel (or what you use for server administration) it will still be the same database. Does Elgg still try to load /kunden/homepages/37/d344360624/htdocs/elg/engine/handlers/action_handler.php even though you entered the site URL without this part? Then it would be an indication that the old, wrong values are still in the database.

    You should also edit .htaccess to include the line "RewriteBase /elg/" (or "RewriteBase /elgg/" ?) before you start with the installation. Best would be to drop the database and create a new one. If you give the new database the same name and use the same database user and password you might be able to leave Elgg's settings.php in the engine subdirectory unchanged.

  • I think iionly is on the right track. Your hoster probably has set up an alias for your web directory in apache. If so, you'll need to set the rewrite base to /elg/. Your settings should be

    The site URL, followed by a trailing slash:
    http://www.likesports.pl/elg/

    The full path to your site root on your disk, followed by a trailing slash:
    /homepages/37/d344360624/htdocs/elg/

  • So sorry for you matches he insisted on Elgg and I need to install it on this server
    Every time I delete and put a new base
    I am currently so:

    The site URL, followed by a trailing slash:
    http://www.likesports.pl/homepages/37/d344360624/htdocs/elgg/

    The full path to your site root on your disk, followed by a trailing slash:
    /homepages/37/d344360624/htdocs/elgg/


    The full path to the directory where uploaded files will be stored, followed by a trailing slash:
    /homepages/37/d344360624/htdocs/dane/

     

    RewriteEngine on

    # If Elgg is in a subdirectory on your site, you might need to add a RewriteBase line
    # containing the path from your site root to elgg's root. e.g. If your site is
    # http://example.com/ and Elgg is in http://example.com/sites/elgg/, you might need
    #
    #RewriteBase /sites/elgg/
    #
    # here, only without the # in front.
    #
    # If you're not running Elgg in a subdirectory on your site, but still getting lots
    # of 404 errors beyond the front page, you could instead try:
    #
    #RewriteBase /

    what is wrong and what to improve

  • Try it with:

    The site URL, followed by a trailing slash:
    http://www.likesports.pl/elgg/

    The full path to your site root on your disk, followed by a trailing slash:
    /homepages/37/d344360624/htdocs/elgg/

    The full path to the directory where uploaded files will be stored, followed by a trailing slash:
    /homepages/37/d344360624/htdocs/dane/

    And in .htaccess:

    # If Elgg is in a subdirectory on your site, you might need to add a RewriteBase line
    # containing the path from your site root to elgg's root. e.g. If your site is
    # http://example.com/ and Elgg is in http://example.com/sites/elgg/, you might need
    #

    RewriteBase /elgg/