“302 Found” after upgrading to 2.0.5

I forgot to post the link to the page describing the bug in 2.0.5 beta.
Here it is: https://trac.www.ads-software.com/ticket/3190

The funny part (if it is funny at all) is that sinse I started blogging (wordpress 2.0.3) I have got this error when you follow my trackback-links.

It is not affected my the above hack. So I still got that issue.

Br, Martin

I get this on (probably for the same reason as above) after upgrading to 2.0.5:
Found

The document has moved here.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request

I get it when I write posts, comments etc.

Hi iskwew.

We got the same problem – try to see if you can solve it the same way as I did – following the instructions in on the linked page above.

When I click you trackback-links I get the same error as on my blog.

I found an old support-ticket with someone having the same problem with trackback links. And it goes all back to 2.0.2: https://www.ads-software.com/support/topic/65315 – but noone has ever answered.

Another funny part – It look like we use the same ISP – https://www.one.com

Br, Martin

For the time being I went back to the old version, and will take a look at the new one later. I had everything copied.

Interesting that we have the same ISP. If no other solutions show up, perhaps that might be where the problem resides.

Thanks for the tip, Martin. I will pay close attention to this thread :o)

Hello,

Same issue and same host (www.one.com).

anyone else ?

This is getting interesting. I will check around if there are more on that host with the problem. And anyone NOT on that https://www.one.com with the problem, please raise a hand.

(not a raise of hand, but the same problem on one.com), with a fresh installation.

A good idea to raise a hand if you have one.com and also have the problem, Goya :o)

I have just talked with one.com support, but they could not directly help us:

Br, Martin

—-

Adrian: Thank you for using One.com 24/7 Interactive Online Support. My name is Adrian. How may I assist you?
you: I don’t know if you can help me.
you: It’s more like a comment to your tech-guys.
you: I’m using the WordPress php-software for my weblog. And its acting strange after upgrading to their new version 2.0.5, and on WordPress’ support-site I have found out, that I am not the only one.com customer with that problem.
you: Please look at: https://www.ads-software.com/support/topic/92183
Adrian: I’ll be with you in just a moment. Thanks for waiting.
you: So I don’t expect you to give me an answer, but maybe someone at one.com should look into it. I guess WordPress is the most commonly used free blogging-software out there.
Adrian: I am checking this out
you: If you are creating some kid of incident, can I then have a ticket-ID?
Adrian: It is best to contact WordPress and ask them of what could be the new changes they have made. And the system requirements before you can install or upgrade it
Adrian: Once you got it, please do send this to [email protected] so we can verify this with our technical team

I got one.com and the same problem.
I’m trying to find an older version of wordpress but I cant find it. Anyone got it?

A funny thing about the one.com support chat:
I got help from someone there and he accidently pasted an URL I guess wasn’t intended for me, it was some “find a wife in asia” site. ??

https://static.www.ads-software.com/archives is where most older versions are found.

I’m not sure if 2.0.5 introduced any database scheme changes, so would suggest making a db backup before downgrading… just in case.

Hey, I’ve got the same problem since I upgraded from 2.0.4 to 2.0.5 and I don’t have One.com hosting. I’ve got Yahoo! Web Hosting but it’s an actual install not the one click install they provide.

(Raising hand) I am also getting this same error on my site hosted by https://www.aplus.net using their unix platform host.

“I’m not sure if 2.0.5 introduced any database scheme changes, so would suggest making a db backup before downgrading… just in case.”

It did not make any new changes but the DB version was bumped so that an index was recreated if it was missing. In short the 2.0.4 DB and 2.0.5 DB are 100% compatible.

I’ve alerted the rest of the hackers and testers to this issue:
https://comox.textdrive.com/pipermail/wp-hackers/2006-October/009369.html
https://comox.textdrive.com/pipermail/wp-testers/2006-October/003191.html

If vital detail can be added on this or any other 2.0.5 roll out issue, please see that one of those threads is updated.