404 Returning as 200 How do I fix it?!

1beb · 2009-02-21 17:35:11

Hi All,

I have an ancient textpattern site that I’ve been loathe to update… txp 1.0rc5. I’m wondering how I stop it from treating 404 error messages as 200 and returning people to the front page even if they type something like /yousuck or some other more creative expletive.

I would like to avoid updating if at all possible. The website works perfectly and the SEO took a lot of time to keep it where it is.

Cheers,

BEB

els · 2009-02-21 18:17:59

What keeps you from updating? (Expecting support for such an ancient version just may be a bit unrealistic…) Updating shouldn’t have consequences for SEO I assume.

Last edited by els (2009-02-21 18:19:05)

1beb · 2009-02-21 18:53:38

My primary concern is that changing versions will “break” the site. And it’s been so long now that I may not be able to do a direct upgrade to a newer version. Assumptions about the effect of updating aren’t an acceptable risk at this point.

I don’t “expect” support, but I certainly would appreciate it.

Cheers,

BEB

wet · 2009-02-21 19:06:26

404 handling was introduced in Textpattern 4.0.1. I don’t think you will have many choices besides upgrading.

els · 2009-02-21 20:27:31

1beb wrote:

I don’t “expect” support, but I certainly would appreciate it.

Sorry, wrong choice of words, it wasn’t meant like that.

1beb · 2009-02-22 19:38:33

So, does anyone have any thoughts or advice that would be relevant to updating from 1.0rc5 to the latest version? I mean, are there any caveats that we know that will occur? Database changes/etc?

p.s. Els, no worries. It wasn’t meant to come across as a snarky reply either! Text is never enough to really communicate. I’ll try smiling next time I type at you, but since you can’t see it – it doesn’t really help :D

els · 2009-02-22 21:20:30

Perhaps you can just try if upgrading at once to 4.0.8 works? Backup first of course ;) If it doesn’t, you could always upgrade in steps. The release history can be found here, but I’m not sure if it tells you when database changes were made. You can access all previous releases here.

Destry · 2009-02-26 09:58:14

I’m pretty sure I’ve seen folks comment in the boards before about being successful with big jumps like this. I think Reid, for one, though not positive. Somebody. Somewhere.

Anyway, I would think not upgrading will eventually catch up and put you in perhaps a worse situation than if you try to do it now.

I would imagine plugins are the main issue?

the_ghost · 2009-02-26 10:15:20

If you are so against upgrading, may be .htaccess can handle 404 request and move them to front page with returning code 200?

1beb · 2009-03-10 20:07:33

Thanks All, I think I’m going to go with updating one at a time. Sounds like the “safest” way to do it.

Cheers and thank for the feedback!

Mary · 2009-03-12 01:51:35

Remember to do the backup dance.

1beb · 2010-01-20 04:13:26

Someone will be happy to know that I just updated straight to 4.2 from RC5 no problems to report, yet. Mind you the site was quite simple… nonetheless – bravo TXP!

Textpattern CMS

Textpattern CMS support forum

#1 2009-02-21 17:35:11

404 Returning as 200 How do I fix it?!

#2 2009-02-21 18:17:59

Re: 404 Returning as 200 How do I fix it?!

#3 2009-02-21 18:53:38

Re: 404 Returning as 200 How do I fix it?!

#4 2009-02-21 19:06:26

Re: 404 Returning as 200 How do I fix it?!

#5 2009-02-21 20:27:31

Re: 404 Returning as 200 How do I fix it?!

#6 2009-02-22 19:38:33

Re: 404 Returning as 200 How do I fix it?!

#7 2009-02-22 21:20:30

Re: 404 Returning as 200 How do I fix it?!

#8 2009-02-26 09:58:14

Re: 404 Returning as 200 How do I fix it?!

#9 2009-02-26 10:15:20

Re: 404 Returning as 200 How do I fix it?!

#10 2009-03-10 20:07:33

Re: 404 Returning as 200 How do I fix it?!

#11 2009-03-12 01:51:35

Re: 404 Returning as 200 How do I fix it?!

#12 2010-01-20 04:13:26

Re: 404 Returning as 200 How do I fix it?!

Board footer