Problem with elgg 1.8 - after update from 1.7


My egg not working correct. When i was have egg 1.7 it works good. Now after update i have only problems.

1-st. I haven't got any layout.. - on 1.7 i had two of them

2-nd. I can't install or uninstall any plugins. I have information from server - "Sorry. We could not find the page that you requested."

3-rd. When i click 'Report this' i haven't got any action.

4-rd. When i Click 'administration' i had information

Invalid Admin Section.

Invalid Admin Section.

5-th. when i click 'dashboard' next i click 'flush the caches' i had info "Sorry. We could not find the page that you requested."


Please help me anyone.


If u need more information Ask me.


  • From which version of elgg 1.7 were you upgrading?

    How did you do the upgrade? Did you follow the instructions? Do you have a backup?

    Rodolfo Hernandez

    Arvixe/Elgg Community Liaison

  • - form 1.7.16 to 1.8.11

    - yes i have backup

    - upgrade form instructions. Only with .htacces may be a problem - i think, but i can have not right. Is my below:

    # Elgg htaccess directives
    # Copyright Curverider Ltd 2008-2009
    # License GNU Public License version 2
    # Link

    <Files "htaccess_dist">
        order allow,deny
        deny from all

    # 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"

    # php 5, apache 1 and 2
    <IfModule mod_php5.c>
        # limit the maximum memory consumed by the php script to 64 MB
        php_value memory_limit 64M
        # register_globals is deprecated as of PHP 5.3.0 - disable it for security reasons.
        php_value register_globals 0
        # post_max_size is the maximum size of ALL the data that is POST'ed to php at a time (8 MB)
        php_value post_max_size 8388608
        # upload_max_filesize is the maximum size of a single uploaded file (5 MB)
        php_value upload_max_filesize 5242880
        # on development servers, set to 1 to display errors. Set to 0 on production servers.
        php_value display_errors 1

    # Turn on mod_gzip if available
    <IfModule mod_gzip.c>
        mod_gzip_on yes
        mod_gzip_dechunk yes
        mod_gzip_keep_workfiles yes
        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/.*

    ## 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

        # 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


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

    #  Add Proper MIME-Type for Favicon to allow expires to work
    AddType image/ .ico

    <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
    # and Elgg is in, 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 /

    # In for backwards compatibility
    RewriteRule ^pg\/([A-Za-z0-9\_\-]+)$ engine/handlers/page_handler.php?handler=$1&%{QUERY_STRING}
    RewriteRule ^pg\/([A-Za-z0-9\_\-]+)\/(.*)$ engine/handlers/page_handler.php?handler=$1&page=$2&%{QUERY_STRING}
    RewriteRule ^tag\/(.+)\/?$ engine/handlers/page_handler.php?handler=search&page=$1

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

    RewriteRule ^cache\/(.*)$ engine/handlers/cache_handler.php?request=$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]+)\/?$ engine/handlers/export_handler.php?view=$1&guid=$2
    RewriteRule ^export\/([A-Za-z]+)\/([0-9]+)\/([A-Za-z]+)\/([A-Za-z0-9\_]+)\/$ engine/handlers/export_handler.php?view=$1&guid=$2&type=$3&idname=$4

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

    # rule for rewrite module test during install - can be removed after installation
    #RewriteRule ^rewrite.php$ install.php

    # Everything else that isn't a file gets routed through the page handler
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteRule ^([A-Za-z0-9\_\-]+)$ engine/handlers/page_handler.php?handler=$1 [QSA]

    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteRule ^([A-Za-z0-9\_\-]+)\/(.*)$ engine/handlers/page_handler.php?handler=$1&page=$2 [QSA]




    Please don't post the same question in multiple threads.  I've removed your duplicate post.

  • I know but i waiting so long.. Your link doing for me nothing..

    Any solution for this problem ? i know lots.. and im not a child.. try to help me giving more information.


    Thank you for your time


  • Ok, I strongly recommend you to roll back to the previous version (restore the site with the backup) and try again.

    Keep in mind that you have to disable all third party plugins and themes. Also, remember to change the dist_htaccess to .htaccess after upgrading.

    Rodolfo Hernandez

    Arvixe/Elgg Community Liaison

  • Also, did you do the step that everyone keeps missing when upgrading from 1.7 to 1.8 and deleting the various directories (especially views) before overwriting?

  • I took a look at problem here and I think problem is in rewrite rules interpretation, exactly in funny mod_rewrite implementation from this hosting provider. In theory rewrite rules should go over and over until none applies, I think it happens here, /cache / requests are routed via pagehandler after /cache/ rewrite rule is applied. Solution is to add [L] to rewrite rules. I don't see possible disadvantage here and it helps on some hostings.

    AFAIR we had similar proplem on the same hosting (one of the bigger hosting providers in Poland), and adding [L] flags solved problems. I think it deserves ticket and PR.

  • @JogiDarkHeart: Please let us know if adding [L] solves problem for you.

  • Hello

    Thanks for all helps informations. I solve the problem. I get to do like this.

    1. Delete all files from server.

    2. Upload all files from 1.8.11 to server.

    3. Install one more time all. ( i see one problem in that resolution - when u have step with "showing" script "data" folder. U can't get the full path - or - its the same path. but its not working. Installation get error.)

    hire real functional examples:

    but 1st will work 2 will not ( when u get use both in installation)

    4. Ill install script with Paweł Sroka (vazco) htacces settings

    5. Its work correctly. :-)

    P.S. If u will have some solves for point 3 let me know :-)

  • Matt Beckett



    ill do all poins from instruktions when i update. Only one thing was different.. Data folder directories. It was bigest problem.

Beginning Developers

Beginning Developers

This space is for newcomers, who wish to build a new plugin or to customize an existing one to their liking