What do you mean by general howto troubleshooting?<br><br>Anisa.<br><br><div><span class="gmail_quote">On 11/10/06, <b class="gmail_sendername">Steven Peck</b> <<a href="mailto:speck@blkmtn.org">speck@blkmtn.org</a>> wrote:
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">The current faq is unorganized because the previous orgainization only<br>made sense if you knew what you were looking for and had a clue.
<br><br>General how to Trouble shooting pages would be useful if people wanted<br>to write them . If we get enough we could make them their own section<br><br>> -----Original Message-----<br>> From: <a href="mailto:documentation-bounces@drupal.org">
documentation-bounces@drupal.org</a><br>> [mailto:<a href="mailto:documentation-bounces@drupal.org">documentation-bounces@drupal.org</a>] On Behalf Of Gary Feldman<br>> Sent: Thursday, November 09, 2006 2:07 PM<br>> To: A list for documentation writers
<br>> Subject: Re: [documentation] Draft (please comment): Can't<br>> open file: 'TABLE.MYI' (errno: 145)<br>><br>> Anisa wrote:<br>> > ...<br>> ><br>> > > errno: 145 is a MySQL error.
<br>> > ><br>> > I think there needs to be some context around this.<br>> How did the user<br>> > get to this FAQ item? Searching for "errno: 145"? Or<br>> searching for<br>
> > "user error: Can't open file"? The reason is that<br>> people are often<br>> > intimidated by error messages, so some help in just<br>> reading this (as<br>> > in: If you see "(errno: nnn)", where "nnn" is some number, then
<br>> > this is<br>> > a MySQL error). But I don't think that sort of help<br>> belongs here.<br>> ><br>> ><br>> > But I feel very relieved when I look in the troubleshooting faq, or
<br>> > indeed, anywhere in the handbook, when there is something with just<br>> > the right title. :)<br>> So do I. The problem is that the right title for you may not be the<br>> same as the right title for me.
<br>> > What I did with the duplicate error faq was to have a short<br>> and long<br>> > explanation. Would that do?<br>> I think I'm not explaining myself well, because I don't see how that<br>> would address the point I'm raising.
<br>><br>> One difference between this and the duplicate entry FAQ is that there<br>> are a variety of errors that can occur with regard to being unable to<br>> open a file. Suppose there's more than one FAQ on this subject. How
<br>> will the user find the right one?<br>><br>> Or suppose the user starts looking in the FAQ under "user<br>> error" (since<br>> that's the first part of the message), can't find it, and gives up?
<br>><br>> The current FAQ is thoroughly unorganized. A handful of them have<br>> actual fragments from error messages in their titles. By<br>> putting this<br>> into context, I was thinking more along the lines of having a
<br>> section of<br>> the FAQ dealing just with error messages, with perhaps the<br>> first entry<br>> being how to figure out whether the message came from MySql, PHP, or<br>> Drupal.<br>> ><br>> > ...
<br>> > I think there should be some more information, for<br>> people who know<br>> > nothing about databases. Something like "Databases store<br>> > information in<br>> > tables, which are kept in files. Do you see
<br>> 'accesslog.MYI ' in the<br>> > message? This file is used for the table named 'accesslog'<br>> > (without the<br>> > .MYI). This is the table that has a problem.<br>> Fortunately, MySQL
<br>> > has an<br>> > operation to repair tables. You can invoke it with<br>> phpmyadmin as<br>> > follows:...<br>> ><br>> > ...<br>> ><br>> ><br>> > I think anyone who is USING drupal should know what the heck a
<br>> > database table is.<br>> I suppose, though from some of the questions that get asked in the<br>> forums, I'm not so sure. But at a minimum, I think it should<br>> say that<br>> the filename 'accesslog.MYI
' corresponds to the MySql table named<br>> accesslog.<br>> ><br>> > When is this useful or possible? I get the impression it's<br>> only for<br>> > when certain tables are corrupted.<br>> >
<br>> I would think that's it's only for corruption at the MySql<br>> level (which<br>> I've never had happen), as opposed to being perfectly good as far as<br>> MySql is concerned, but having bad data as far as Drupal is concerned.
<br>><br>> Gary<br>><br>><br>> --<br>> Pending work: <a href="http://drupal.org/project/issues/documentation/">http://drupal.org/project/issues/documentation/</a><br>> List archives: <a href="http://lists.drupal.org/pipermail/documentation/">
http://lists.drupal.org/pipermail/documentation/</a><br>><br>><br>--<br>Pending work: <a href="http://drupal.org/project/issues/documentation/">http://drupal.org/project/issues/documentation/</a><br>List archives: <a href="http://lists.drupal.org/pipermail/documentation/">
http://lists.drupal.org/pipermail/documentation/</a><br></blockquote></div><br><br clear="all"><br>-- <br>*********************************<br><a href="http://www.AnimeCards.Org">www.AnimeCards.Org</a><br><br>16,000 scans and counting!
<br>*********************************