When doing updates in "administration mode" - ex. for "content" or "people" - the after-update ends in "404 page missing".

Ex. after update my browser URL looks like this ...

... /admin/content (after update of content) - and page missing
... /admin/people (after update in people) - and page missing

The actual change is updated correctly in database - only "returning" to admin fails to a 404 - and new login to "admin" is only solution.

When doing ex. updated of content in "web site mode", no problems.

Best regards
Peter

Comments

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Postponed (maintainer needs more info)

What PHP version are you using?
Who is the service provider providing the host?
What OS is on the host?
Do you have a custom 404 page enabled in the http daemon?
What are you seeing in the host log files?

PeterRas’s picture

PeterRas commented

I have created a new internal test-site, and for now this issue is "solved".

The site causing this issue, is also a internal test-site - with minimum of content - and no changes or themes at all (I'm in Drupal "learning" mode).

The only difference is, that for the latest test-site, all modules are uploaded first and activated all at the same time. For the previous test-site, they where uploaded and activated one-by-one.

I come back, if happens again.

enochRoot’s picture

enochRoot commented
Version: 7.15 » 7.16

Hi,

I'm experiencing the same problem - not everytime, but sometimes after an update of a node, i'm getting 404.
This is also a test site and I did activate more or less all the modules at the same time.

info:
PHP 5.2.17
hosted by 1und1
OS: Linux infong 2.4 #1 SMP Fri May 18 17:32:59 UTC 2012 i686 GNU/Linux

I didn't enable custom 404 page,
access log says: GET /tests/drupal7/admin/content HTTP/1.1" 200 640

can this be caused by errors in my own module? couldn't relate changes in the code to changes in this behavior.

greetings,
eR

Version: 7.16 » 7.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Status: Postponed (maintainer needs more info) » Closed (outdated)

Automatically closed because Drupal 7 security and bugfix support has ended as of 5 January 2025. If the issue verifiably applies to later versions, please reopen with details and update the version.