404 after save or publish a post

rodrigomuniz-

Read back through this thread and you’ll find a full discussion of the error and a patch to try.

This change might help. You can either apply that diff, or download a new classes.php file here. Replace your existing wp-includes/classes.php with that one.

If you’re a subversion user, that fix and some others are available from the 2.0 branch.

Let us know if that change helps.

Ryan,

Thanks for the change info. I figured that when I and Technosailor had proposed patches that they were just patches, and not necessarily the preferred fix for the problem.

I’m running your change to the classes file on my site now, and have removed my patch to the functions file. Your change does seem to correct the problem – at least in my case, it was happening every time I used ‘save and continue’.

Hope we were able to help point you in the right direction…

rdsmes, your debugging and testing was very helpful. Thanks.

Uh, yeah none of these changes work, and I still get a constant 404 error. Any idea? This has become a very frustrating problem.

I recently encountered this problem when I changed my permalink settings (away from the default /?=123 method into something more custom, i.e. /%category%/%postname%) and added rewriting rules into my lighttpd system.

Anyhow, this is to let y’all know that the

if ( !$posts ) to if ( !$posts || !$posts[0]->ID ) patch works for me ??

Just curious… are the fixes working for people who got a blank page or a 404? I’m wondering if there are two different problems at work here and perhaps the fixes are working for one set and not the other.

I’m running into blank page issues

Hawke –

I can only speak to my experience, in which I was seeing a 404 error on the redirection after using ‘save and continue’ and then doing a ‘save’ or ‘publish’ operation – with the URL containing the long mySQL error string. I did not see a blank page.

In that case, yes, the fix that Ryan placed into the Trac system is working for me, as were the temporary patches. I could reliably reproduce the error, and it is now gone. It is possible that some of the other posters in this thread are seeing different problems.

Okay, had a chance to check it… Ryan’s change did not do anything for my blank page after save & continue editing problem. Will continue to try various things, will let you know if anything works! =)

Hawke: this would seem to be a different problem, or at least a different manifestation of the problem.

At this point it’s probably better to start a new thread, listing your specific issue in detail, rather than add not-same info into this thread.

Quite right vkaryl, several issues at work here. Mine is resolved, finally, with much help from ‘rdsmes’ offline. A heartfelt thankyou to him.

I was having difficulty with one post in particular, one that included the word “curl” as noted in this 403 error thread. I reverted back to WordPress 1.5.2 and started getting the 403 error instead of the 404.

Purely coincidental that this word in my post was at around the 1000 character mark.

I’m getting 404’s when I publish Pages and I’ve now realised what’s causing it but what’s the simplist way to overcome it?
Posts are OK but Pages fail without an error message being created until the published page is viewed. The cause would seem to be that my webhosting provider does not permit use of the root except for index.html or index.php however that’s exactly where WordPress attempts, and in my case fails, to publish them. Using version 2.0.

Im experiencing a 500 error – wordpress is spitting out an Internal Server Error when I try and post code in blog.

I’ve used the fix above – but that does not help.

Anybody got any other ideas?

I now see that my reasoning was a bit out. I have two uncorrected blogs. One does the pages correctly, e.g. ‘?page_id=18’ but the other is putting ‘/page_name/’ and hence failing to display.

Any thoughts appreciated.

Did anybody ever figure out this issue as it relates to post length? That seems to be my problem. After I try to post something that’s to long, it gives me the 404 error…if I shorten it, it will post.