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 tomlan on
Hi,
I've been tasked with rescuing a drupal installation from a hosed server and getting it running on a new machine with FC7 and Drupal 5.2.
I believe the old one was a 5.1 installation.
I've been able to get the site up to the point that I can log in as admin and I'm no longer getting any errors. However, my site is completely un-themed. I've copied the old theme over to the new /themes directory, but it doesn't show up in the themes list in the admin suite. If I choose one of the default themes instead it doesn't take effect. I'm left with a very bare white site.
It seems only the main content of each page shows up - there are no sidebars.
I apologize for being vague about this, but my question is this: where do you start looking to troubleshoot the lack of a theme and sidebars?
Any suggestions are much appreciated.
TIA,
Tom
Comments
Same Problem
Tom,
I am having the same problem with my current Drupal site. The site is for my wife and was running fine on 5.1 until either yesterday or today (had not checked site in 2 days). I upgrade to 5.2 since the site had issues anyway, but it did not help. I can't get any of the themes to display properly. If you find anything out please let me know. If I am able to figure out the problem, I'll post the fix here.
David
same issue, i tried it, but
same issue, i tried it, but still isn't working
=-=
have either of you tried setting a $base_url in your settings.php ? which should have been replaced when you upgraded from 5.1 ?
___________________________________________________________________________________________________
The search tool on Drupal.org really does work. This message has been brought to you by the letter X. Thanks for watching! : )
Yeah, that generally does
Yeah, that generally does the trick when the system can't find the themes.
Is the search tool still working? ;-)
=-=
Captain she's at full power already, any more and the reactor may blow. :said with a scottish accent:
___________________________________________________________________________________________________
The search tool on Drupal.org really does work. This message has been brought to you by the letter X. Thanks for watching! : )
disable all the extra
disable all the extra modules temporarily and try working with the core modules alone. The problem may be caused some of the old-version modules.
still no luck
I set the $base_url and disabled all the modules except for core modules. It won't even display the standard themes. I also tried the search and it is not yielding any results.
=-=
without a link, we can't view the source code.
have you viewed the source code to see if the css files are actually being called and just not showing ?
have you tried clearing the browser cache and the cache tables ?
have you inspected your DB tables to insure all is well ?
any server information beyond the FC7 kernel ?
___________________________________________________________________________________________________
The search tool on Drupal.org really does work. This message has been brought to you by the letter X. Thanks for watching! : )
link
The link is http://www.davidhibler.com/crosstimbers
I cleared the browser cache and tried to view the site on 3 PCs to no avail.
I have a copy on a test server at my house and the only difference I have found thus far is a weird call to a css file in my "files" directory.
@import "/crosstimbers/files/css/c1fdd7d278d4a1a8581a3c3072cf4a13.css"
My test server doesn't include this file even though it has all the same modules installed.
re-indexed and search works now
I re-indexed the site and search works again.
Problem Solved
I'm not sure why this made a difference, but I found a similar article on the drupal.org site (http://drupal.org/node/142594) and it mentioned the files/css being created by the "Aggregate and Compress" option under performance.
I have had this set to Enabled while I was setting up the site and since it has been in production (2 months now) with no problems. I just set it to Disabled and the theme magically appeared. My files directory exists and download is set to Public, so it seems that Enabled should work; however, I'd rather have something other than a plain white site with 1 column, so I'll leave it as Disabled for now.
David
good to know about it :)
good to know about it :)
Same Problem Here - Maybe a FAQ Entry?
Hey, folks:
This thread saved my site, thanks. I had also upgraded to 5.2 awhile ago, and everything was absolutely peachy until yesterday, when my stylesheet suddenly went AWOL. One minute I was editing my blog and Drupal looked great as always, and the next minute I was at the bottom of a themeless, Access Denied rabbit hole. I had clean URLs enabled, so of course that compounded the problems. Here's what finally fixed it:
1. Turned off Clean URLs so I could at least navigate the admin pages again.
2. Edited /sites/default/settings.php to set a base_url pointing to the subdirectory that contains my Drupal installation.
3. Turned off CSS compression in the "Performance" menu.
4. Visited cron.php to make sure everyone got the memo.
5. Saw that the site was now working. Held my breath and turned Clean URLs back on. Whew - those work again, too.
Because this problem seems to pop up suddenly for no apparent reason, my guess is that there are going to be a lot of Drupal users scratching their heads over it in the coming weeks. Could we add a higher-profile item in the support files explaining how to fix it?
...
For a transfered site, my biggest suspicion is always permissions or a path isn't 'quite the same' on the moved site.
Anyone can contribute a page on this to the handbook. The appropriate spot would be as a child page to the Troubleshooting faq
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide