200 error code being sent on 404 page instead of 404

please release this fix quickly, google has been indexing plenty of 404 error pages of my site ...

It’s being worked on as quickly as possible. If it’s that urgent, you’re certainly welcome to grab the code and submit a patch if you can get to it faster than the coding team.

unfortunately, i’m a php-illiterate ( but i’m planning to learn php soon ), moreover i’m so busy ... ( studies )
but it’s not that urgent don’t worry, when i said plenty of 404 pages, there are three ( among a 20 pages site ^^ )

bye

i have just one more question, when will be released the next modx version ?? i read on modx.bugs that this 404 bug will be fixed in next version, and i’m so impatient ...
i just changed all the aliases of all my pages ( for a better google ranking ), and google is still indexing the previous ones ....

i just do snippet



and put him into 404 page

it doesn’t work ....
when i look at the response header of the page ( with the FF Web Dev Toolbar Extension ), there is a "404 OK", weird isn’t it ? ( it seems the snippet couldn’t "override" the header that was sent first )
thx

if you have any fix, please share

That won’t work because headers need to be sent before page content. PHP may just be surpressing its errors...

There are of course a near-infinite number of 404 "pages", and this is potentially a major issue.

Quote from: vbrilon at Apr 30, 2006, 11:11 AM

The problem was actually fixed, and then accidentaly unfixed in the process of putting out the security release recently. Look for an update very soon with a fix (again )

Quote from: vbrilon at Apr 30, 2006, 02:22 PM

It’s being worked on as quickly as possible. If it’s that urgent, you’re certainly welcome to grab the code and submit a patch if you can get to it faster than the coding team.

Some clue of how fast the coding team would otherwise get to it (and Victor, it’s assigned to you) would be helpful in figuring out whether I can get to it faster!

This isn’t as urgent as I first thought, as I’ve realised there’s another solution to the Google issue (see below) - but still I expect fake 404 pages to pass a 404 code to the agent if not the server and would be happier if MODx did that.

If it’s going to be more than a week or so, then I volunteer to pick up your previous fixed code and reapply it to 0.9.2.1. If you could just tell me where I can grab that fixed code from!

The bug report at http://modxcms.com/bugs/task/255?tasks=last mentions a fix at : http://modxcms.com/forums/index.php/topic,1052.0.html but I cannot access that forum page - if you could please PM me the code, it would make this do-able.

Alternatively, if you can’t get the code to me, let me know and I’ll investigate other avenues.

Fixing the Google issue
There are also 2 potential ways of solving the Google problem, by asking it not to index the fake 404 pages:
1) Custom robots.txt file with known (old) pages disallowed
2) Add to a custom template for the 404 page. (I guess you only want NOINDEX there but I don’t know if that would work so it’s probably best to leave it as per the official example.)
For more on this angle, see http://www.google.com/support/webmasters/bin/answer.py?answer=35303

I’m going to put the meta tag in my 404 template, it seems the best way forward.

thx for the tip, i didn’t think to the search engines tags !

hi again
i added the robots meta tag in the 404 error page, i hope it will work ( google doesn’t seem to crawl my site very often ... )
by the way, i am trying the etomite fix ( see the 1st post of this thread ), the solution is to modify the index.php file around line 700, but mine only have 100 ones at most ...