When I log out, all my blocks disappear

Posted by charmer on June 19, 2009 at 3:29pm

I've been scouring forums for almost two hours but to no avail so far.

I have a fresh installation of Drupal 6.12 installed from custom profile with a custom theme. I've downloaded several other themes for testing and also created several items to primary and secondary links. Everything was OK and after some toying I wanted to look at the web while logged out - then I saw all of the blocks gone, only logo and content of frontpage remained.

I've triple checked that the blocks are enabled, that the themes have default link blocks enabled (in global settings as well) and that all blocks have correct visibility settings (by default none role was selected which should mean no restrictions but I tried to check all roles as an alternative setting with the same effect - didn't work). I didn't find anything that would prevent blocks from appearing in admin/user/permissions - anonymous users can access and search content.

Then I disabled all testing themes and activated only bluemarine - still nothing, upon logout all blocks disappear. I even have another testbed installation on another server where everything is default, but even there items in primary links disappear upon logout while login block and Recent posts block remain...

This must be something mundane but I don't really know what else to check. Thanks in advance for hints.

Comments

all blocks including the

Posted by mtsanford on June 19, 2009 at 3:58pm

all blocks including the menus, login block, and search block?

all custom actually

Posted by charmer on June 22, 2009 at 7:40am

Sorry to confuse, some of the themes I tested didn't have search blocks placed and I don't need login block to be displayed. But when I put them back for testing they do show up. All my custom menus - primary and secondary links I made by hand are those that disappear...

more info

Posted by himdel on June 23, 2009 at 3:26pm

Hey, the aforementioned blocks have status=1, custom=0, and BLOCK_NO_CACHE. Setting custom to 1 doesn't help either.

Problem solved...

Posted by charmer on June 24, 2009 at 2:32pm

...and yes it was stupid.

I was only testing the menus with empty Drupal and thus added internal paths node/add to menu items.
I didn't realize that if the menu has non-existent internal target it won't show up when you log out - which is obviously a feature.

Oh, well, let's this never happen to me or anyone else again...

I had the same problem

Posted by cmcandrew on February 11, 2010 at 12:54am

I found this from someone else on here - thankfully!!!! I was about to jump off a bridge. If you target paths are using "node/add", they will disappear when you logout. If you add in a real URL, it won't happen.

Drupal has quite the learning curve - to say the least.

Chris

It has nothing to do with an

Posted by mtsanford on February 11, 2010 at 1:18am

It has nothing to do with an URL being "real" or not. node/add is a real URL just as much as node/1 is.

Only menu items that link to URLs that the user has access to are shown. Anonymous users do not usually have access to node/add since they are not granted permision to to create new nodes. However, you can easily grant node creation permission to anonymous users at admin/user/permissions and node/add *will* show up when you log out.

HI! Having a bit of the same

Posted by sledan on April 27, 2011 at 1:39pm

HI! Having a bit of the same problem.

When I logout (being a non-authenticated user), the block having the search-form is disappearing. Though when I login again, the block is visible (the search form is visible).

I've tested the visibility settings for the block, and non are checked. So that the default is that everyone can see the block. I tried check the box, so that only anonymous users can see the block. What happened was that when I was logged in, I could not see the block (which is good). Then I logged out again, and the block didn't appear there either.

I'm using Drupal 7.

Thanks in advance,
Danny

I desolved the problem. It

Posted by sledan on April 27, 2011 at 9:20pm

I desolved the problem. It was a permission problem. (@ users/permission -> allowing the search function for all users)