|
|
<ol>
<li>I install <a class="zem_slink" title="Drupal" rel="homepage" href="http://www.drupal.org/">Drupal</a> 7. I realise there is no search box Huh? Come on guys, this is 21st century!</li>
<li>Knowing how Drupal works, I go to <code>admin/build/modules</code> and activate the Search module</li>
<li>Next stop is <code>admin/build/block</code> for moving the Search form where I want to</li>
</ol>
<p>As a sidenote, this could be easier, but I don’t see an easy way as of now.</p>
<p>Now is my complaint: I log off and check: no search box. How come?</p>
<ol>
<li>I come back to <code>admin/build/block</code>, 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.</li>
<li>Then I try going to theme and checking the search form box on both <code>admin/build/themes/settings</code> and <code>admin/build/themes/settings/garland</code> (by the way: this double checking is confusing too. This would be fixed I guess with switching to <em>tri-state permissions</em>, that I will talk about later on). Logging off. No better</li>
<li>Then finally, I realize this must be related to permissions. Bingo, this is it!</li>
</ol>
<p>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.</p>
<p>BUT</p>
<p>There should be a warning. Cross-referencing matters. <strong>When a block calls for a module that no one has access to</strong>, there should be a warning and a link to fix this.</p> |
IP Logged
|
|
rack and pinion |
