“302 Found” after upgrading to 2.0.5

I am running 2.05 hosted on Dreamhost linux server and this error was also occuring. The mentioned fix did work for me though and thanks for the link.

My fault, folks. There was a bug report for the problem on 2.1 and it slipped my mind that this change went into 2.0.5

For people who are adverse to editing core WordPress files, try this plugin on for size.

https://txfx.net/code/wordpress/wordpress-tuneup/wordpress-205-tuneup/

Edited the file manually, and it is working great.

Thanks for all the help!!

The code change can be found here:
https://comox.textdrive.com/pipermail/wp-testers/2006-October/003075.html

Wohaaa! It worked, thanks!

I have now tried the plug in and et solved the 2.0.5-bug. Thanx. I don’t like hacking the core-files.

But I still gets the same error when clicking on my trackback-links. This has been a ploblem for several releases back. I guess that all the users have have the 2.0.5-bug oalso have this trackback-bug.

Does anybody have the same trackback-bug? And does anybody know what to do to it?

Br, Martin

iskwew, I have the same problem and I use https://www.aplus.net.

They don’t allow 302 Temporary Redirects (which sucks because I would love to use the Feedburner 2.0 plug-in from Steve Smith at Ordered List).

Does anyone know of any ISPs that aren’t so rigid about what you can and can’t use on their servers? I’ve been running up against some brick walls with Aplus.net as of late and their tech support is non-existent unless you have a dedicated server.

Take a look at https://networkredux.com

I have this problem too, 2.05 and one.com as provider. The plugin solved the problem.

Hey i have the same problem and one.com, but used the fix at:

https://comox.textdrive.com/pipermail/wp-testers/2006-October/003075.html

and it seems to be working. Please try this and post the results.

This resolved the 302 errors for me, but I still get the 302 errors for trackbacks.

The plugin fixed the 302 bug. Thanks! (btw: I’m also using one.com)