Closed (fixed)
Project:
Drupal core
Version:
6.3
Component:
base system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Jul 2008 at 01:59 UTC
Updated:
23 Sep 2008 at 14:04 UTC
I recently used Drupal 6.2 for a project and to my surprise after I activated blog, tracker, statistics and other modules and changed to a contributed theme the /admin -administration page does not load. It does not give any error or time our but gives a blank page. Not only that nothing in /admin works like /admin/build/themes or any other URL. Other thinks work fine like adding nodes viewing them. So what may be the problem. Due to this I upgraded to 6.3 but the problem persists. My old sites in Drupal 5.x run fine with no problem. I'm using XAMPP 1.6.2 on windows Vista. What should I do?
.
Comments
Comment #1
dropcube commentedIf this happen after changing to a contrib theme, the issue is probably related with the theme. If the theme is hosted at Drupal.org, please report the bug in the theme issue queue.
Comment #2
geshan commentedI managed to change back to Garland but still the problem persists. Think there is some problem in system module may be.
Comment #3
vm commentedblank pages are apache errors, check your apache/http error logs to see if an error is being thrown.
also try clearing your cache in administer -> performance
Comment #4
geshan commentedThere are no errors, how am I supposed to go to performance when my /admin does not load, you may give the full URL to the performance but noting after /admin work.
HELP HELP
Comment #5
vm commentedI can't reproduce the problem and without any apache error messages I don't know how to debug any further.
you can try clearing your cache tables manually in the DB using a tool like phpmyadmin
Comment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #7
japanitrat commentedargh, this is bad, having the same problem. I do not use clean-url's, have garland as administration-page, but it won't display any pages which start with "?q=admin". (afaik we don't have a top-level folder "admin" in the drupal-directory)
I've contacted the server admins, but they say there is nothing reasonable in the logs.
Since we ported the database from a dev-server, we will now try to make a fresh install on the new environment, maybe its something with the database.
Comment #8
damien tournoud commentedTry visiting
?q=admin/build/modulesComment #9
japanitrat commentedas i said: Every page starting with ?q=admin didn't work which includes ?q=admin/build/modules (why is that fixed?)
anyway we found the solution now:
the update.module were blocked by the firewall (every admin page tries to repopulate the update-list), which caused the server to timeout with no errors in logfiles. we disabled it manually in the database in order to work on other things before getting a new firewall-rule applied.
further reading: http://www.tmsnetwork.org/blog/node/119
Comment #10
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.