put in a files directory with a readme.txt<br><br><div class="gmail_quote">On Dec 8, 2007 1:48 PM, Angela Byron <<a href="mailto:drupal-devel@webchick.net">drupal-devel@webchick.net</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Here's a usability report from one of our GHOP students:<br><a href="http://ijailbreak.com/drupal.html" target="_blank">http://ijailbreak.com/drupal.html</a> (please post feedback to<br><a href="http://drupal.org/node/197219#comment-652618" target="_blank">
http://drupal.org/node/197219#comment-652618</a>). He interviews three test<br>subjects: his mom, his brother, and his Dad.<br><br>In it, he points out that all three of his test subjects got totally<br>blocked at this error and needed him to step in and fix it in order for
<br>them to continue. This is the *second* page of the installation. If we<br>are losing people before they even get Drupal installed, we are screwed.<br><br>I realize the argument against including a files directory by default is
<br>that Mac OS does this insane behaviour of overwriting the contents of<br>"files" with another directory of the same name, so there's a chance of<br>completely blowing away someone's files directory. So as far as I can
<br>see, we're left with a couple of options:<br><br>- Revert the existing behaviour, which at least allows mere mortals to<br>get Drupal installed, even if it's a somewhat annoying thing to deal<br>with later.<br>
- Include the blank files directory anyway, and trust that people are<br>either reading upgrade instructions, or not running production websites<br>off of a Mac OSX desktop/laptop.<br><br>Thoughts?<br><br>-Angie<br></blockquote>
</div><br>