By iancawthorne on

A large number of our sites built on Drupal 5 have just recently started showing "page not found" errors when choosing a content type to add.

What is really confusing is that it seems to only be some content types.

They always seem to be ones that have been added after install (eg not page or story).

They are pretty standard content types with just a few cck text fields.

I've tried patching to the latest verison of Drupal and all contributed module to no avail.

Disabling clean url's has also had no effect.

I've also tried clearing the cache under performance settings.

We have several Drupal 6 sites and none of these seem to be effected.

Any suggestions with this problem would be much appreciated.

⋅ Categories: Drupal 5.x

Comments

jevets’s picture

jevets commented

Did you run update.php after updating the modules?

iancawthorne’s picture

iancawthorne commented

Yes, I ran update.php on each update that was made.

Hydrant Ltd
www.hydrant.co.uk

jevets’s picture

jevets commented

Have you taken a look at the watchdog table?

iancawthorne’s picture

iancawthorne commented

The watchdog logs the problem each time as a 500.shtml warning.

Hydrant Ltd
www.hydrant.co.uk

lucyconnuk’s picture

lucyconnuk commented

I am having a similar problem. What's more, it doesn't always happen and I can't figure out a pattern - one minute I will be able to add a new whatever, then the next minute I can't - I just get page not found.

Anyone else?

iancawthorne’s picture

iancawthorne commented

I've also discovered that this is happening for some, but not all edit pages. This is also some but not all edit pages for the content type that is getting page not found when creating too.

Hydrant Ltd
www.hydrant.co.uk

iancawthorne’s picture

iancawthorne commented

After disabling a lot of modules, I've found that the "page not found" is being caused by the core menu module. If I disable this module, the pages load ok.

How to proceed from here I do not know as the menu module being enabled is pretty crucial for all my effected Drupal sites to work.

Hydrant Ltd
www.hydrant.co.uk

lucyconnuk’s picture

lucyconnuk commented

I can also solve the problem by disabling the menu module.

Like you I don't know what to do next but I'm still looking...

iancawthorne’s picture

iancawthorne commented

I am following the progress of this thread : http://drupal.org/node/117503 I think it started off as a php4 issue, but now a few people have the problem with php5.

Hydrant Ltd
www.hydrant.co.uk

lucyconnuk’s picture

lucyconnuk commented

See also http://drupal.org/node/621214

iancawthorne’s picture

iancawthorne commented

Our hosting company has now reverted our server back to php5.2.10, rectifying this problem. This makes it difficult to test.

However, I do have one theory. The cache_menu table sounds like it could be to blame. Try dropping all the data (not the structure) form this table and see if it solves the problem. You can do this using the devel module or directly in the database by phpmyadmin or similar.

The thought behind this is that the data in that table may not be compatible between the two versions of php causing the data to be corrupt.

Hydrant Ltd
www.hydrant.co.uk

lucyconnuk’s picture

lucyconnuk commented

I tried emptying cache_menu but it didn't make any difference. I've just had to keep the menu module turned off.