WPMU-2.9.2 to WP-3.1

  • Hello,

    We sucessfully(all except the issue mentioned here as far as we see now) updated WPMU-2.9.2 to WP-3.1 MultiSite.

    We are using Multi-DB(https://premium.wpmudev.org/project/multi-db) plugin version 3.0.6.

    There are 200+ users and all of them together have almost 2000+ sites while upgrading and all seem to work fine too.
    All plugins work fine too now, had to update couple of them too before they did.

    But, while logged in as ‘admin’, it says “Thank you for Updating! Please visit the Update Network page to update all your sites.” << We do that and get following messages on different browsers we tried.
    Get the same result when we try to access ‘Network Admin’ on top right of admin login.

    Safari:
    Too many redirects occurred trying to open “https://{our-site}.com/wp-admin/network/”. This might occur if you open a page that is redirected to open another page which then is redirected to open the original page.
    Chrome:
    This webpage has a redirect loop
    The webpage at https://{our-site}/wp-admin/network/ has resulted in too many redirects. Clearing your cookies for this site or allowing third-party cookies may fix the problem. If not, it is possibly a server configuration issue and not a problem with your computer.
    IE:
    It keeps on working and has not shown any messages yet, can see ‘Waiting for https://{our-site}/wp-admin/network/upgrade.php’ on the status bar.
    FF:
    Not tried yet.

    Kindly advice, could it be an upgrade issue or the multi-db plugin related issue or anything else?

    Thanks & Regards

Viewing 13 replies - 16 through 28 (of 28 total)

  • Got a backup?

    Go back to the original version. Manually upgrade to 3.0.

    https://wpmututorials.com/how-to/upgrading-to-3-0/

    then upgrade to 3.1.

    Thread Starter mikee17

    (@mikee17)

    Ok, but now it looks like we have everything working fine except that it logs the error (i.e …internal redirects due to probable configuration. Use ‘LimitInternalRecursion’ to increase the limit if necessary. Use ‘LogLevel debug’ to get a backtrace) when we go to the Network Admin area(which was NOT working either earlier) at backend of our WP installation.

    Thread Starter mikee17

    (@mikee17)

    Hi,

    Here is an update we did to our .htaccess (‘—s—‘ & ‘—e—‘ is used only here to improve readability)…

    The below code:

    ---s---
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule . - [L]
---e---

    is REPLACED with:

    ---s---
RewriteCond %{ENV:REDIRECT_STATUS} 200
RewriteRule .* - [L]
---e---

    The above updates seems to have solved our issue reported here, shall get back again with updates if any…

    Thanks & Regards

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    That doesn’t look like Apache…. What kind of server are you on?

    Thread Starter mikee17

    (@mikee17)

    Its Apache on a Linux box.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    *After rereading my books…* Oh. So it is.

    You shouldn’t need %{ENV:REDIRECT_STATUS} but if you do, it’s a server config wacky.

    Thread Starter mikee17

    (@mikee17)

    @ipstenu
    We removed %{ENV:REDIRECT_STATUS and put back the orginal .htaccess file.

    Thread Starter mikee17

    (@mikee17)

    We are researching the cause of the follwoing error:
    “Request exceeded the limit of 10 internal redirects due to probable configuration error. Use ‘LimitInternalRecursion’ to increase the limit if necessary. Use ‘LogLevel debug’ to get a backtrace.”

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    No, what I mean is that you shouldn’t need to use that INSTEAD of

    RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule . - [L]

    That YOUR server is requiring you to use this is what’s weird.

    RewriteCond %{ENV:REDIRECT_STATUS} 200
RewriteRule .* - [L]

    Thread Starter mikee17

    (@mikee17)

    RewriteCond %{ENV:REDIRECT_STATUS} 200
RewriteRule .* - [L]

    We REMOVED the above code and is now using the orginal that is below:

    RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule . - [L]

    I.e. we switched back our changes to .htaccess as that did not solve the issue completely.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Right and now it’s failing again, correct? So for your setup, it only worked with the ENV:REDIRECT_STATUS line?

    Which is weird, and that’s all I was getting at. THAT was weird.

    Thread Starter mikee17

    (@mikee17)

    Yes, we get the bellow error when we go to the Network Admin area:

    Request exceeded the limit of 10 internal redirects due to probable configuration error. Use ‘LimitInternalRecursion’ to increase the limit if necessary. Use ‘LogLevel debug’ to get a backtrace.

    Could be a nested folders issue like Andrea_r said.

    Thread Starter mikee17

    (@mikee17)

    We get the above messages mainly when we go to the ‘Network Admin’ area … looks like an .htaccess file with following code at /wp-admin/network/ solves the issue.

    RewriteEngine On

RewriteRule index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule (.*)$ /wp-admin/$1 [L]

    Do you see any issue?

Viewing 13 replies - 16 through 28 (of 28 total)
  • The topic ‘WPMU-2.9.2 to WP-3.1’ is closed to new replies.