Comments on: WordPress 2.82 – Changing URL is Bad

By: Scott

Scott — Tue, 27 Oct 2009 13:41:06 +0000

Apparently, this weeks hardening release has eliminated ANY redirect at all, and an edited permalink or changed permalink structure simply comes up 404. Wonderful.

By: Fixing the Wordpress 302 Blues

Fixing the Wordpress 302 Blues — Wed, 26 Aug 2009 11:10:57 +0000

[...] when did this change come about? I’m really not sure, but I was lucky enough to catch this post and eventually find a solution. Some sites have experienced the 302 for a while, but the last [...]

By: Ben Cook

Ben Cook — Mon, 03 Aug 2009 21:30:36 +0000

Scott, not a problem. As I mentioned on the other post, this isn’t a new phenomenon to WP 2.8.2 as I currently have older blogs that do the same thing.

Also, I have blogs (2.8.2 and 2.8.3) that are creating 301 redirects when a URL is changed so I’m not sure what the issue is.

Both flippingeasy.com and the site that are using 301 redirects are on the same server so it’s not a hosting issue.

Perhaps its a plugin or theme issue somehow?

By: Scott

Scott — Mon, 03 Aug 2009 20:59:56 +0000

Thanks for taking the time ben – I appreciate it – looks like 2.83 is out now too!

By: Ben Cook

Ben Cook — Mon, 03 Aug 2009 18:30:19 +0000

Mark, if the intent is that they serve a 301 redirect then the feature is not working properly.

I’ve created a quick test installation at http://test.flippingeasy.com that illustrates that it is in fact serving a 302 redirect.

However, I didn’t think this was new behavior for WordPress as I’ve seen it serve 302′s for some time now.

By: john andrews

john andrews — Mon, 03 Aug 2009 18:17:51 +0000

sorry – meant to also say that was WP 2.8.3 so there is no confusion. Wp2.8.3 was released last night, and still has the 302.

By: john andrews

john andrews — Mon, 03 Aug 2009 18:16:31 +0000

function “redirect” still is a 302 redirect (see wpp-apps.php line 1351)

By: Scott

Scott — Mon, 03 Aug 2009 01:16:59 +0000

I do see the video there, thanks, but I’m not sure what to say!

By: Scott

Scott — Sun, 02 Aug 2009 23:50:35 +0000

Thanks Michael, I was going to try what you emailed me, but I figure I’m safer this way – I break things too easily

By: graywolf

graywolf — Sun, 02 Aug 2009 23:16:53 +0000

Mark,

Here’s the code I had to edit to get to to work work it’s in the plugable.php file wp-includes

this has my edits sorry didn’t save the original

//if ( php_sapi_name() != ‘cgi-fcgi’ )
//status_header(301); // This causes problems on IIS and some FastCGI setups
header(“HTTP/1.1 301 Moved Permanently”);
header(“Location: $location”);

without the 301 line it returns a 302