AardvarkGirl

Yes… windows server.

I even went into IIS and stopped services to this site and restarted it but it didn’t help.

krispy_b
I had the same exact issue. We have control of our server.

See my other posts about everything I have done. I ran the auto update on one of our clients sites and the site went blank (actually got an error in Chrome and FF that it is in a loop). Then I ran the auto update on our WP test site (used to just develop themes). It killed that one too.

So with the test site I tried a manual update – didn’t work. Then I killed all the files and the database and tried a brand new, fresh install of 3.1 and got the same thing (full access to admin area but the front end hung in a loop / blank page).

I finally killed the entire thing and just reinstalled 3.0.5 with a clean database and it works fine.

My clients site that is still in ‘upgrade-loop-limbo’ is still there. I’ve given up, only two people have replied to my two threads. I’m digging into the server back ups of the database from yesterday and I’m going to kill everything and just totally reinstall the ‘limbo’ site again using 3.0.5 and just import the backed up ‘pre update’ database. :-\

Cameback to edit that my limbo site does not have that plug in installed – and actually from the admin area it let me deactivate all my plug ins, but it still won’t function on the front end.

I tried to go in and change the plug in folder name, not just via FTP but via remote desktop, and it would not give me access (seriously?). I even started/stopped the website in IIS.

Want to know something odd? My site that is still ‘in limbo’ from the upgrade, is giving an error that it is in a loop. I log into the server via remote and tried to rename the plug in folder (like some suggestions said today) and it won’t give me access to do so, says the files is in use. Makes sense, it’s stuck in a loop. So I go into IIS and stop services for that entire site and restart it – still nothing.

I’m going to just grab the back up of the database from yesterday, kill the entire site (the limbo 3.1 upgrade) and reinstall a fresh install of 3.0.5 including a brand new database, then import my backup from yesterday.

No one else seems to have an answer, and only two people have replied to my personal threads about my problem.

Yes, when I did a fresh install, and I do mean fresh. I killed everything on the server, I killed the entire database. The only thing that remained the same was my root folder on the server. YES doing a fresh clean install of 3.0.5 worked fine, no issue what so ever.

My big question is, how do we go back to 3.0.5 after a botched upgrade?

On our test site we totally killed everything and did a full fresh install of 3.1 and has the SAME issue with the upgrade. For this site I totally killed everything again and did a fresh install (with database) to 3.0.5.

But my other site is a ‘real’ site in development with real content installed.

At least you get just a blank page. When I go to mine it gives me this:

https://www.kairosemployment.com/test/

Same with me (I have two of my own threads going).

:-\

What browser are you using? If you try to go to the front end of your site in Chrome or FireFox, what error do you get? (For me the site just hangs in IE with no error or anything).

Just another update (guess I’m just talking to myself at this point)

I totally killed site B, all 3.1 files and the database, and did a resintall from 3.05 with a brandnew database. Works like a charm, like it was before this update.

So.

This is OUR server. We are the host.

I finally killed one of the sites entirely and restored an install of 3.0.5 and it is running just fine. Which was fine because this was just a test site used for theme development – but the other site is a site currently in development that had real content on it.

I was able to run the upgrade – and get back into my admin area and access everything.

When I try to go to the front end it hangs and hangs, then I get these errors from Firefox and Chrome:

The page isn’t redirecting properly
Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

* This problem can sometimes be caused by disabling or refusing to accept cookies.

—————————————

This webpage has a redirect loop
The webpage at https://www.kairosemployment.com/test/ 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.
Here are some suggestions:
Reload this web page later.
Learn more about this problem.
Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects.

I got so frustrated I totally killed one of the sites, database and all (it was a test site we use to develop themes). Did a total fresh install from a full 3.1 zip, created a new database and had the same problem. Finally I just killed all that and reinstalled version 3.0.5 and it works just like it did before (fine).

Of course this doesn’t help me for the ‘live’ site that is hanging in limbo with the 3.1 install. :-\

I’ve got full access to my server and nothing has changed.

I did a manual update – I even went as far as totally killing my database and emptying the entire folder and doing a fresh install of 3.1 from a manual upload. Got the admin area working but the front end of mine still hangs.

Ok – site B… I manually downloaded and uploaded all the 3.1 files manually and still no front end of the site.

So then I went in and killed EVERYTHING. The database, all the files, and ran a totally new install on this. Created a new database, ran the install… still nothing on the front end. *sigh*

Tried opening it in Chrome this time and got this error:

his webpage has a redirect loop
The webpage at https://ra-wordpress.com/ 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.
Here are some suggestions:
Reload this web page later.
Learn more about this problem.
Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects.

Steven – I tried to auto update from 3.0.5 to 3.1 – I’ve got at least 8 WP sites on this server and have never had an issue with auto updates.

I ran this update and it killed my site (I have a thead posted but no one is responding).

I tried it on a test install of WP and it killed that one as well (a stock install with a child 2010 theme, no plug ins installed).

Admin is fully functional (I can deactivate plug ins, change the theme, edit pages etc) but when I go to the front end in IE it just hangs and in Firefox I get an error telling me the site is in a loop.

Any tips?

I also tried to manually unzip/upload the 3.1 install – and still no front end.

Ok, just for sh*ts N giggles I ran the auto update on our wordpress test site – same exact server but not running in a sub folder – and the result is the same.

The site is dead. :-\

Site A had minimimal plug ins installed and was running on a TemplateMonster theme.

Site B was had 1 plug in (demo data) and was running on a 2010 child theme.

*sigh*

Site B was just auto upgraded (same server settings etc) from 0.4 to 0.5 not too long ago and everything went fine, so I don’t get how it could be a permissions issue (just talking out loud).

ESMI – tried using FTP and could not change the plug-ins folder name to plugins.hold (or what ever it was the article suggested).

I then went thru phpmyadmin and the setting was already a:0:{} (because as I said I was allowed to deactivate all my plug ins).

Still no site on the front end. ??