Closed (outdated)
Project:
Drupal core
Version:
7.x-dev
Component:
menu system
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
28 Apr 2011 at 12:53 UTC
Updated:
4 Jun 2024 at 13:09 UTC
Jump to comment: Most recent
Comments
Comment #1
naught101 commentedDoes this happen on a fresh install? Do you have any contrib modules enabled, if so, which? What server software and versions are you running (eg. apache/IIS, php, mysql/postgresql?) Are you logged in as user 1? have you checked your php error logs?
Comment #2
guykohn commentedSorry duplicate
Comment #3
guykohn commentedI've just finished installing php, mysql, apache 2.0 and Drupal 7.8. Everything works fine except the configuration page which I just can't access.
I cant find any reference. Can anyone help?
Comment #4
knalstaaf commentedI'm experiencing the same issue. There's no specific action I'm conducting, so I can't describe what could go wrong here. It's on a website that was fully running before. The only difference is that it's multilingual now.
It just happens once in a while: I hit the "Configuration" link in the upper part of the toolbar, the black transparent overlay appears (no page), and that's it. When I try to load the page without the overlay: the page keeps loading endlessly. Then, later on, or mùch later on, the problem seems to be solved. Until it occurs again...
The same thing occurs when trying to open "Status report".
After a long while the following error occurs (in Firefox 6):
Odd. Could this be hosting-related?
Comment #5
elvelux commentedI have the same problem, knalstaaf, word by word.
The only difference is that my site has been multilingual for a long time. I don´t know why it has stop working well.
Do you have drupal 7.8?
Comment #6
knalstaaf commented@ elvelux: I'm using Drupal 7.8 indeed.
The website is hosted on an account with an automated cron task every now and then. Can an automated cron task trigger this kind of behaviour?
Comment #7
naught101 commentedSorry, but there is no way this is a major issue, considering how few people are reporting it. Please, read and answer the questions in comment #1 - in particular, what non-core modules do you have enabled?
Comment #8
dublutz commentedI have the same problem. I'm running D7.8.
This happened after I have updated my php to 5.3.8 and Apache to 2.2.21
Comment #9
HFase commentedSame problem here on D7.10, I guess I will start disabling things and let you all know if I find anything.
EDIT:
Solved mine after adding a bunch of Apache2/php5 modules that I thought I had installed already. Nothing to so with php memory or modules, just server support. ;)
Comment #10
knalstaaf commentedCould you specify these Apache2/php5 modules please?
Comment #11
bennebiest commentedPlease explain how you did solved this issue.
Thanks.
Comment #12
drupalthemernet commentedTo solve this issue, we should look at it the Apache or IIS log file to figure out the problem. I see in the log these errors:
php_mcrypt.dll and php_pdo.dll are missing. the problem is solved if we install those modules
Comment #13
webmaster-eddie commentedI have this same error - a page timeout when I click on Status report or Configuration in the admin interface - for drupal 7.15 - but it only happens for multilingual sites, and the more languages (and the more modules enabled) the worse it is. If i do a translation update, then I can almost always access both Status Report and Configuration in the web admin interface right away.
Comment #14
nofue commentedI tracked this very issue to l10_update module, archive: l10n_update-7.x-2.0.tar.gz
Once I enable it, admin/config shows the WSOD. Once I disabled it, everything's fine … As this is the only installation (out of maybe 20) where this is going to happen with the l10n_update, I suppose there's possibly a conflict with another module I haven't spotted yet.
Comment #15
nofue commentedFollow Up:
After
everything is working as advertised …
Comment #16
onique commentedI was having the same issues. It seems from the logs that it lost its path to the composer manager (service binding location) and after unstalling and reinstalling it via terminus it solved the error and am now able to access the page.
Comment #17
poker10 commentedThis is a support request and there is no patch to review, so changing the status accordingly.