Apologies up front if this is not the place to submit this issue:

I can edit some existing nodes;
I can create new nodes;
but some existing nodes return a page not found error after I click submit.

I can't say why some nodes return the error and others don't. I checked the database and noticed some of the tables were collated differantly - so I changed the collation for all tables to utf8 - no differance. I also repaired the database but nothing was noted as requiring repairing.
I've checked that those nodes which do return an error don't have common features like using certain reserved words but couldn't isolate any.
I've turned off all access modules like privacy_by_role and content access, as well as the more common modules like taxonomy, no change (so I've since reactivated taxonomy as it was required by the image gallery.

My only significant recent action was to install Organic Groups which I thought was to blame but when I reinstated the site from an earlier backup the errors were still occurring.

The errors started when I was running Drupal 4.7.10 so I upgraded to Drupal 5.5 but this did not address the issue.

The error is written to the logs as follows:

Type page not found
Date Monday, 24 December, 2007 - 17:56
User jhorton
Location http:///?q=node/157/edit
Referrer http:///?q=node/157/edit
Message 403.shtml
Severity warning
Hostname xx.xxx.xxx.xx

I am running the following system configuration"

Drupal 5.5
Database schema Up to date
File system Writable (public download method)
MySQL database 4.1.22
PHP 4.4.7
Unicode library PHP Mbstring Extension
Web server Apache 3

Comments

Schoonzie’s picture

Hi,

I'm not 100% sure, but I think this relates to mod_security in PHP. I have the same problem on one of my servers, where that is installed. On some pages, where the content seems to match a flag in mod_security, it produces that error (redirects to 403.shtml) which is probably not setup in your Drupal instance, and so produces a 404 error.

When this happens to me, I remove all the content from the body, and start adding it bit by bit to work out what is causing the error. It is sometimes "<?php" that causes it, but "<?" works fine.

I'd love to switch hosts, because its a real pain, but unfortunately, I don't have that option at this time.

Nick

jhorton’s picture

Status: Active » Closed (fixed)

This is almost certainly an issue of the server configuration as Nick suggests. I believe my host for some reason changed the server status and this has obviously been addressed as the problem has disappeared.