Theme: Garland, Browsers: IE7 and Firefox 2, Version: Drupal 5 beta1
The problem appeared when I wanted a block to appear on the first page only. So I set 'node' for it in the block admin section. After all there is no way back: I cannot undo it. The site appears as in the attached screenshot. For instance: the user login and search blocks are set to be on the top of the RIGHT sidebar. Now my site doesn't appear properly until i reach the '/admin' link. I really tried everything but i by no means could undo this. Now my entire site is messed up.
| Comment | File | Size | Author |
|---|---|---|---|
| screenshot_0.JPG | 33.66 KB | tiwaz |
Comments
Comment #1
cog.rusty commentedDid you disable that block in admin/build/block?
Comment #2
chx commentedComment #3
chx commentedsorry bad classification on my side
Comment #4
tiwaz commentedWhat shall I do now in order to repair my site? Need I really re-install everything?
Comment #5
cog.rusty commentedYes, one way is to reinstall everything.
Another way is to try to find out what the problem is.
Did you disable that block in /admin/build/block?
Did you try to change the theme?
Have you installed any contributed modules, and did you try to disable them?
Comment #6
PAAHCweb commentedIt appears you can still log in as admin, if not in the login block, then at example.com/user. Try to get to administer --> block, uncheck the offending block, and save the change. Not sure what version you're using -- I'm still using 4.6, but for me the block configuration instructions say to use to put something only on the front page. Small problems can make your site blow up like this but there's almost always a way back without reinstalling.
Comment #7
cog.rusty commentedtiwaz is using 5.0 beta.
He should be willing to try to fix many problems in the next months.
Comment #8
tiwaz commentedWell, it appears that the theme is injured because the problem doesn't appear with bluemarine. The site looks normal. What should i change in drupal to restore my garland theme back to normal? It used to work just a few hours ago.
Comment #9
cog.rusty commentedOk, you have started to locate the problem.
One thing you can tell now is that Garland does not work together with *some other thing* that you set up afterwords.
Next, you have to find out what that other thing is and disable it. Then you will file a better bug report for Garland or for that other thing, so that they know what to fix.
Keep Garland and start disabling blocks and modules one by one, until you find out the guilty one. When Garland starts working again then you will know what caused the problem.
Comment #10
tiwaz commentedThanks Crog. My question might be stupid but can it be a database problem. Coz I was messing with 'node' when the problem occured. And in the node table of MySQL I can see error messages that i cannot see in other tables. The warnings are as follows:
! PRIMARY and INDEX keys should not both be set for column `nid`
! More than one INDEX key was created for column `status`
Comment #11
cog.rusty commentedI think this is a second problem you have there, a different one. I don't think it has to do with Garland. Bad news, you may have to reinstall everything after all.
I also thought of something about the first problem. Maybe it is not Garland's problem at all... When you switch to Bluemarine, does your block appear (the one you created)?
Comment #12
tiwaz commentedSorry Cog for misspelling your name above, and I yes I came to the conclusion that i can only see the problem in the case of "/node" alias frontpage. In all, this must be the gist of the problem. This happened when I wanted a block only be to be shown on the frontpage so I typed 'node' under 'Show on only the listed pages' in the block administration section. The block item was a 'partner sites' menu created by me. But now it is ofcourse set back to normal, only the problem remains.
Comment #13
tiwaz commentedYes all the blocks appear, but in the wrong place, interfering with the left-sidebar items, while they should be on the top of the right sidebar. Still, it only happens in the case of the first page otherwise even now it is normal on other pages eg. when i go to /admin.... it is still ok.
Comment #14
cog.rusty commentedJust to know:
-
<front>means "front page" (this is what you should have used for the block visibility).-
nodemeans "a teaser list of all published nodes".- When you set your front page to "node" in general settings that means "show a teaser list of all published nodes on the front page"
Comment #15
cog.rusty commentedAlso, I would disable that block completely. It seems to be buggy, probably the only cause of all your theme problems. When Bluemarine works, it is probably because this block does not appear at all.
Comment #16
cog.rusty commentedor it contains a wide image or a pixel size which makes tableless themes collapse.
Comment #17
tiwaz commentedBut why isn't this screwed up in bluemarine theme? Only garland/minelli does this (both of them). And again it is looking normal (=the blocks are properly on top of the right sidebar) other than links beginning with 'node...'
The plain question is how can I fix this problem? Can we fix this at all? Thanks Lord my site is just one week old and hasn't really been launched yet so in the worst case i can reinstall without significant loss of data.
Comment #18
cog.rusty commentedBluemarine is not a pure css theme. It uses some "good old" tables for its layout. Tables are flexible. A pure css theme has more restrictions and it is easier to break.
I repeated the question whether this particular block appears at all in Bluemarine because block settings are per theme.
Comment #19
cog.rusty commentedIf you want to fix and use Garland... it is not trivial to customize a css theme. They fall apart easily with tinkering. You would have to find someone who can do the job (I am not one).
Alternatively, you may want to try to customize your block, see if there are any fixed wide elements or any buggy markup.
Comment #20
tiwaz commentedYeah it appeared perfectly. And it appeared perfectly in garland as well as long as the link didn't begin with 'node'. It is about 4 blocks actually, not one, which appeared on the wrong side.
Comment #21
heine commentedIf you file something as a bug report, please focus on solving the perceived bug.
What do you mean with 'the link' here?
I've tried to set several (core) blocks to "Show on only the listed pages." where the listed page was 'node', but I could not reproduce the issue.
So it appears we need some extra information.
Comment #22
bdragon commentedClosing issue, no feedback, assumed this was fixed before Drupal 5.0 was released.