Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By andrewmccandless on
I just installed drupal 6.12 and it seems that there is no admin folder. Installation appears to have run successfully, but when I click the "Administer" link it thinks for a few minutes and ends up at a blank page. Checking by FTP, I see that there is no admin section at all.
Is this file supposed to be included in drupal-6.12.tar.gz? It doesn't show after unzipping with 7-zip, so I figure it must be added during installation, but I get no errors whatsoever during installation, so I'm not really sure what the problem is.
Comments
Extarct on the server
Hi,
Difficult to say what went wrong.
Upload the Drupal x.xx.tar.gz file using FTP or the cPanel File Manager, extract the files on server using cPanel File manager (Right click on the file and click extract). So that you don't miss out on anything.
Good luck.
Still no admin folder
Hi there,
I reinstalled drupal and unzipped it with the file manager like you suggested. While it seemed to catch a few things this time that went unnoticed before (register globals needed to be turned on, and my current config wasn't compatible with clean URL's), the installation still fails to create an admin folder.
I'm using psek hosting (www.psek.com) and php 5. The only thing I can think of as being wrong is the hosting, but I've installed things like prestashop and osCommerce with no problem in the past, so I find it somewhat unlikely.
As with the case before, decompressing the drupal-6.x.tar.gz file didn't result in the creation of an admin file. I'm guessing it's something that is supposed to be generated during installation, and not unzipping, is that right?
Can anyone think of any possible causes for this problem? This is really frustrating :(
There is no admin folder
There is no actual admin folder in a Drupal installation. The URLs in Drupal just give instructions to index.php, which calls other PHP files and pulls information from the database as needed. Technically, you're (almost) always looking at index.php. (That's why yoursite.com/admin and yoursite.com/?q=admin do the same thing.)
Drupal users usually refer to the kind of problem you're facing as "the white screen of death" or "WSOD." Typically, it happens when you run into memory problems, and it's quite common while trying to load the Admin page because Drupal does a lot of background work while loading that page.
My first suggestion is to search around in the forums for "white screen of death admin" or "wsod admin" and see if you can find anything helpful.
Possible culprit
I just saw a post about a very similar problem at http://drupal.org/node/485004, and someone seems to have posted a solution.
Disabling update module didn't work
Well, I disabled the update module, which appears to have solved this problem for numerous other users, but to no avail.
http://www.example.com/?q=admin still loads forever, then ends up on a blank page. It's odd, because I'm experiencing the exact sympotoms of other users with the same problem, but the same solution doesn't seem to apply.
I disabled the update module manually in phpMyAdmin following this guide:
http://www.tmsnetwork.org/blog/content/2008/08/22/drupal-6-slow-administ...
The process was fairly straightforward, but of course did not solve the problem.
I read in the handbook (below) that switching my databases over from MyISAM to InnoDB can help optimize database work. Do you think this might help?
http://drupal.org/node/259580
I'm really at a loss for what do do here. I can't believe disabling the update module didn't work.
.
I'd be surprised if switching from MyISAM to InnoDB would help in this case. My (limited) understanding is that InnoDB will help primarily with a high-traffic site in which users are frequently writing to the database, since InnoDB can write to the database without locking entire tables.
I'm not much good with this stuff, so I'm at a loss about what else to tell you. If you've tried all of the other WSOD solutions you can find, you might start a new thread devoted more explicitly to your WSOD problem.