jo0lz

I just noticed this only happens when I add multiple php code widgets at the same time.
If I add them one widget at a time (leaving the widget screen in between adding them) it works fine. Weird.

You can try putting in the following code

# BEGIN 404 Fix

<IfModule mod_security.c>
SecFilterEngine Off
SecFilterPost Off
</IfModule>

# END 404 Fix

instead of

# BEGIN 404 Fix

<IfModule mod_env.c>
SetEnv MODSEC_ENABLE Off
PassEnv MODSEC_ENABLE
</IfModule>

# END 404 Fix

Okay, I’ve found a fix, but I’m no server expert, so I don’t know if I just created a security issue, but here goes.

I’ve been having this problem for a while now, and I am convinced that it’s a server configuration issue. This is because on my home server and several other WordPress installation, this error does not occur. It’s strange however, that this problem only arises after installing WP 2.7.

There are a few changes I made to the .htaccess file, in order to find a solution by using a “trial and error” method. (Thanks Hanewurger, your post helped me out A LOT!)

Here’s what I added to the .htaccess file:

# BEGIN 404 Fix

<IfModule mod_env.c>
SetEnv MODSEC_ENABLE Off
PassEnv MODSEC_ENABLE
</IfModule>

#END 404 Fix

The original (WordPress generated) .htaccess looked like this:

# BEGIN WordPress

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

So, after my edit, the .htaccess looks like this:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

# BEGIN 404 Fix

<IfModule mod_env.c>
SetEnv MODSEC_ENABLE Off
PassEnv MODSEC_ENABLE
</IfModule>

#END 404 Fix

The 404 errors after updating posts are now solved. However, I’m not an expert, but why does this happen, and why do I have to make this adjustment? I wonder if this causes any security problems on my domain… Is there anyone who can shed some light on this issue?

@Hanewurger, maybe you can try this solution and see if that Avatar Plug-in issue is solved as well?

@danielbachhuber, in the link that Hanewurger provided is some information on other possible solutions. You might want to try them out, because the post was really there to help solve “Error 500” issues.

Hope anyone is helped by this, and I hope someone can shed some light on the security questions ??

Regards,
Jo0Lz.

Ok, weird thing. I’ve posted a “happy new year” blog post.
I can update that post fine, it returns to the edit screen, with the message “post updated”.

But, a post about christmas presents, still gives me the 404 after updating… ??

Navigating away from the admin panel, and moving back in, editing the same “happy new year” post, again gives me that 404 error.

In the case of error 404, it redirects to message=1, but earlier it was redirecting to message=6…

I’m at a loss here…

Hi,

this problem seems to be related to this topic: https://www.ads-software.com/support/topic/224111?replies=8

There is a 404 instead of 500 error, and it’s in 2.7 final, instead of RC1.

Still don’t know how to solve it though…

Okay, I found out the piece of URI produced by pressing the “update post” button, that doesn’t work, but do not yet know how to fix it.

The URI that I get redirected to:
https://mysite.x/wp-admin/post.php?action=edit&post=27&_wp_original_http_referer=http%3A%2F%2Fmysite.x%2Fwp-admin%2Fedit.php&message=1

The URI that works:
https://mysite.x/wp-admin/post.php?action=edit&post=27&_wp_original_http_referer=http%3A%2F%2Fmysite.x%2Fwp-admin%2Fedit.php

But it doesn’t show the “Post updated. Continue editing below or “go back” message, which I figure is added by the &message=1 …

Going to digg into this.

I’ve just tested this on a clean install of 2.7, and after pressing “Update Post” I get redirected to the edit page. So, the problem might be related to updated install’s of wordpress…

I’ll be upgrading some other blogs this week, going to see if they have the same problem. If so, I might try a clean install, and importing everything into that install.

No-one with the exact same problem?

I’m going to install a test wordpress (development server) to see if it’s related to my site.

I just tested to see if this was a template fault, but it seems that even with the default theme this error occurs.
I’ve adjusted permalink structure, set it to default, but that doesn’t matter either. The 404 error persists.

I’m going to update another blog, hope that the error won’t appear there… If it doesn’t, it still is going to be a pain to find out what is causing it. Weird because I haven’t seen any forum posts on this, so it might be just me having this error.

I was having the same problem. Changing the feed hasn’t worked, yet, I think that I’ll have to wait until Feedburner updates my feed…

Thanks for sharing this information.

See what happens if you upgrade to the 1.5.8 version available at https://brianslatestcomments.googlecode.com/svn/trunk/brianslatestcomments.zip

Sorry MichaelH, but that is another plugin. (Threaded is what he is referring to, but you posten the LATEST comments, and that’s a different plugin.)

I’ve got the same problem, with this plugin and WP 2.3.3, it just returns an not found page.
Also tried another version, called “Page Threaded Comments” wich is based on Brians, and instead of the not found page, it just forwards me to the index of my wp site.
(And doesn’t post the error.)

Any Fixxes or ideas?! I’m at a loss here.

Ok, I found out what caused this problem, I maintain tags, but with a preceeding slash.
(/me, /kids, /laugh…)

Now, that the slashes are removed from the tags, all is working ok.

Who would have thought, that IE doens’t like tags that contain slashes… ;’)

Hi there!

Yes, the entries are saved in the database.
I’ve come across these problems, but in a slightly different manner. The tags that I used, are the same, but the slug is different because of this, I had 2 “me” tags, one with the me slug, and one with jo0lz slug. Using the “me” tag in the posts, caused the seperate counts, but only one tag is displayed in the cloud. (The one with the least posts…)

Resolve your tag headache, with this great plugin:
(Manage tags, add, delete and edit.)
Advanced Tag Entry

(Check out this topic aswell…)

A sym link allways points to a real file. If this was the way it was set up, it wouldn’t have worked in the old situation.
Every installation, has to have an own wp-config.php, in order to define database connections.

I would install the both blogs in the www-root, different sub directories, linked to different (sub)domains.

Glad to see you have got it working, though.

Does the database point these blogs to use /etc/wordpress/wp-config.php, or some file? Or is it something else?

Nope. It’s the other way around. Your wp-config file points to the datebase. It also displays the username and password used to connect and the database it has to connect to.