Posted 2 years ago #
I have installed a fresh blog and imported data into it. When I attempt to go to view the site, I get the following error from Firefox
Firefox has detected that the server is redirecting the request for this address in a way that will never complete.
Any suggestions?
Posted 2 years ago #
I have the same issue, was there ever a resolution?
I got this when upgrading from the following
2.3.3 to 2.5.0
2.3.3. to 2.5.1
2.3.3. to 2.6.5
What to do?
First stop updating way old posts :)
Second, stick to ONE post with your one question.
Third, do a manual upgrade.
Posted 2 years ago #
Me or the first person? I didn't forward anything.
It's still very relevant to me.
Please provide a solution, I did a manual upgrade using upgrade.php
9000word - You.
The first person posted 1 month ago. You posted 1 hour ago. That is the definition of 'updating way old posts'.
By manual upgrade, confirm that you downloaded the new version of WP, FTPd it to your server, unzipped it, and went to log in.
Posted 2 years ago #
I did do a manual upgrade then, exactly as you indicated.
Thank you :) Assumption is the mother of all wrong support answers. ;)
What plugins are installed, and are you using default permalinks or pretty permalinks?
Posted 2 years ago #
Ipstenu,
Hello. Thanks for getting back to me.
To best answer your questions, there are No plugins installed, this is a fresh install.
As far as permalinks, I can't tell you because I cannot see the dashboard, edit panel, options or anything because I cannot get to the login screen because I keep seeing this message only.
http://enlightenedwebmastery.com/wp-content/uploads/2009/01/redirect-error-example.png
If it's a 'fresh' install, it shouldn't be trying to upgrade at all. Otherwise you'd know if, previously, you had permalinks set.
Frankly, if it's a brand new blog, why are you trying to install an old version? Scrub it and start with 2.8 instead.
If it is a true upgrade, I'd 'back out' the upgrade and re-install 2.3 just to make sure about plugins and permalinks.
The Detailed Upgrade Instructions for 1.5.x, and versions 2.0 - 2.6.5, to 2.8.6 don't suggest a staged upgrade at all, and imply you can go 2.3 to 2.8.
You can download the various versions from the Download Archive.
Posted 2 years ago #
You asked about permalinks, so I went ahead and checked it and it was set to the default, not the same version as the previous database.
I just tried to change it to Day and name wordpress250/2009/12/09/sample-post/
Now I cannot even get back into the fresh install of 2.5.0 any longer
Why would changing permalinks provide a page "500 Internal Server Error" when I try to access the dashboard, etc. now?
Do I need to fix this in the myphpadmin page or something?
I need to get to this first and resolve it before I can get to your recent questions about upgrading directly to 2.8.x
Posted 2 years ago #
Is this the solution to permalinks? Waiting?
I have godaddy.com hosting as well.
http://www.joshstauffer.com/wordpress-godaddy-permalinks-and-404s/
I didn't suggest you change them, I was asking what you had...
And you're giving conflicting information about all this. I'm tossing out ANY and all questions about 2.5 since according to your FIRST post, you're trying to upgrade from 2.3 to 2.8 and I have NO idea how or why you ended up on 2.5 at this point (leaving out the obvious question which is 'why on earth are you doing a FRESH install of an outdated version of WP?')
What's the status of your 2.3 install right now? Were you able to roll it back as I suggested?
Posted 2 years ago #
Ipstenu,
Hello. I was refreshing this forum all morning until I saw your post. I am excited to try and finally solve this problem and get wordpress upgraded today. :)
To answer your questions, I have 2.3.3 on my test site and it's working alright, but I need to upgrade it as we know to 2.8.6
I have been doing sequential upgrades as advised by the folks in IRC chat #wordpress
It was advised that I go from where I started, 2.0.4 ->2.2.3 -> 2.3.3 -> 2.5 - > 2.6.5 - > 2.7 - > 2.8.6
The hangup is on 2.5 where I get redirect loops, so I really wonder if I will actually have more success going directly to 2.8.6 without the redirect loops?
I hope this gives us more clarity now :) I look forward to your response once again.
Thank you for that explanation. Now it all makes sense! (see how the whole story helps? Remember this next time you need help :) We can do more with details)
You should have been able to go from 2.0.4 right to 2.8 without the intermediary steps. I did it ONCE from 2.2 to 2.7 and it worked fine, so ... it's a theory, but one I'm fairly sure of.
And honestly, it can't be worse than the loop of death you've got. Do a manual upgrade to 2.8.6, and the DB should update itself when you get there.
(Sidebar: GoDaddy has permalink issues, a LOT of them, and can take a couple hours to catch up with any .htaccess changes, as it stores them on multiple servers.)
Posted 2 years ago #
Ipstenu,
Good morning. Thanks for your prompt response! :)
So, here's the thing, is the upgrade.php "smarter" than say the one in 2.5, so it won't result in loop of death like I am currently experiencing?
What makes the potential for success in upgrading to 2.8.6 greater than that of 2.5? Is it the ugprader, the better ability to convert databases?
Please let me know before I go this route. :)
R
So, here's the thing, is the upgrade.php "smarter" than say the one in 2.5, so it won't result in loop of death like I am currently experiencing?
I think so, yes.
FWIW, I have this vague memory of having a similar problem with 2.5 and all I can remember doing was waiting to 2.6 (but that was more than 10 days ago, and my memory fades on upgrades pretty fast...)
Posted 2 years ago #
Okay, I will try upgrading to 2.8.6 and see if it doesn't do this strange thing. Keep in mind it's going from 2.3.3 here.. :)
I will keep you posted shortly on this, but I suspect it will be a redirect loop again. I hope not though.
Posted 2 years ago #
I got what I expected, a redirect loop when upgrading to 2.8.6 now.
There's something happening in on all versions from 2.5 onward with the database.
What could it be?
Posted 2 years ago #
Should I read this perhaps?
This is what I am attempting to do, 2.3.3 to 2.5
http://www.thesitewizard.com/blogging/how-to-upgrade-to-wordpress-2-5.shtml
Posted 2 years ago #
Someone suggested exporting my material from 2.3.3 using the Manage>Export function in the site, then importing it into a working fresh install of 2.8.6? Would that work?
No need to "update" that content in order to bring it into a newer version?
Yeah. That could work.
Honestly it's more that somethings weird with your 2.3 install than there's something up with the upgrade itself. It could also be something about GoDaddy....
Aha. It is GoDaddy.
Posted 2 years ago #
Well, here's what did "work". The exporting/importing. The limitation was on both ends.
Apparently, it's currently set to only export a wordpress export file of no more than 8MB, which accounted for 279 out of over 3000 posts. I need everything exported, so how can I raise that export limit?
Conversely, how can I also raise the import limit on 2.8.6 on the receiving end?
That's working..so at this rate, I'm willing to go the route that's working even if it means more work for me.
Posted 2 years ago #
I figured out the redirect FINALLY!
I went into myphpadmin and it had the OLD blog FOLDER in there from the previous database! I replaced it, then it got me to the login!
Now the login password also became replaced by the previous, so I went into myphpadmin and changed it to, now I can login to the latest version of wordpress and see all of my data in there! Wow!
Now to get the aesthetics working, plugins working, and upload folder completely copied over before I can begin phasing in the new version of wordpress! :)
EXCITED!
That's ... well, yeah, that would perfectly explain that error. How'd the blog get so jiggity turned around?
Posted 2 years ago #
I'm currently looking to basically make my live site that's on URL/blog go to URL/wordpress286
I'm currently copying themes folder, uploads folder, plugins folder & photos folder to see what works, what doesn't before I "flip" the switch and have the new wordpress commanding the LIVE site. I want to make the exterior transparent so no one can tell that the backend changed at all.
Posted 2 years ago #
RESOLVED
This topic has been closed to new replies.
