Hello

  1. I install Drupal 7. I realise there is no search box Huh? Come on guys, this is 21st century!
  2. Knowing how Drupal works, I go to admin/build/modules and activate the Search module
  3. Next stop is admin/build/block for moving the Search form where I want to

As a sidenote, this could be easier, but I don't see an easy way as of now.

Now is my complaint: I log off and check: no search box. How come!

  1. I come back to admin/build/block, and check the two boxes for each user, even if I should not have to (no check = visible to all). Well maybe there is a hole in the documentation. Logging off. No way.
  2. Then I try going to theme and checking the search form box on both admin/build/themes/settings and admin/build/themes/settings/garland (by the way: this double checking is confusing too. This would be fixed I guess with switching to tri-state permissions, that I will talk about later on). Logging off. No better
  3. Then finally, I realize this must be related to permissions. Bingo, this is it!

I became a proficient Drupal user with time. Still, it took me ten minutes to find out. I know about permissions, but when I see a button for search, I assume that the search box will appear. Granted, I can understand the reason why it is possible not to make it appear, not much problem here.

BUT

There should be a warning. Cross-referencing matters. When a block calls for a module that no one has access to, there should be a warning and a link to fix this.

Now:

  1. Does my complaint makes sense?
  2. Did someone already reported this?

Notice the same thing happens with Drupal 6 (I tried first with D6 before trying again with D7a3).
Thank you.

Comments

David Latapie’s picture

Just an addition:

admin/content/node-type/story (D6) has such a cross-reference below the anonymous comments options. Very handy.

yoroy’s picture

Which install profile did you use? Search is enabled in the default install profile.
It's true that the 'use search' permission is only enabled for the adminstrator role, so anonymous won't see a search box.
I agree that it'd be nicer to enable that permission for all roles by default.

adityakg’s picture

@When a block calls for a module that no one has access to, there should be a warning and a link to fix this.

I agree with that. Where should it be put if warning and a link is preferred? Maybe after the block is activated yet the permission for the module that the block calls is not already granted? (i.e. putting it in admin/build/block/list)

David Latapie’s picture

As you said: It worked by default… for root only.

David Latapie’s picture

Usual behaviour being "warnings are atop the page", I'd say: atop.

apaderno’s picture

Issue tags: -ui, -blocks, -access permissions, -warning, -adopting D7 usability to D6, -cross-reference