document comments -- I volunteer

I have a to-do idea which I might volunteer for. As a newcomer to Drupal, I spend hours if not days browsing this site every time I have a question. I find that many times the same questions are asked over and over. And some very kind people take the time answer them. The quality of the answers are uneven. Sometimes the question gets an answer that is perfect, complete and clear. Sometimes the question gets an answer that's confusing. This may relate to how much hurry someone was in, how much experience the answerer has, a version change, etc. Sometimes you'll see a little debate in the trail of comments about whether a solution will work or not.

Two examples of commonly asked questions are:
1) how to use taxonomy and the various add-on modules to create breadcrumbs a certain way
2) how to replace the default logo.

I would guess there are over 100 comments on each question. I am planning to put together a list of bookmarked comments that I think best answers each question. (As a newcomer, my judgment could be wrong.) I am thinking about contributing that back to the Drupal community. I browsed through the instructions about documentation. I don't want to step on anyone's toes, but I don't think I'm familiar enough yet with the Drupal site to figure out the best way to implement something like this in a way that would not be too time-consuming for me.

Unexpected behavior: Apache's mod_rewrite, Drupal's clean urls, and the file system

I thought I knew how Drupal's "clean" URLs interacted with Apache's mod_rewrite and the file system. The logical flow seems obvious after observing the following code in .htaccess:

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]

The Apache 1.3 documentation for RewriteCond says:

'-d' (is directory) Treats the TestString as a pathname and tests if it exists and is a directory.
'-f' (is regular file) Treats the TestString as a pathname and tests if it exists and is a regular file.

The code checks for a file or directory that matches the request and, if neither is found, rewrites the clean URL such that Drupal can handle it. But all is not as it seems. I expected RewriteCond %{REQUEST_FILENAME} !-f to require a complete match between the file system and the URL before failing.

Here is the caveat:
Apache will not rewrite a clean URL if Apache finds a file at the base of the Drupal installation whose name matches everything up to the first slash (/) in the request. As an added twist, Apache does the same if the file ends with .txt, .diff, and perhaps some other common extensions.

Here is how to demonstrate the quirk: only shows HEAD?

    Why do:


    return the same lines of code even though my actual Drupal install (4.6.5) has different code altogether for this function?

    Offline documentation


    is there any offline documentation available for drupal? Like the handbooks and the API documentation?


    homepage question

    How do I make my website so that it doesn't go to I tried under administrator - settings and took out the default homepage with the home at the end but it still did not work.

    Separate CVS into 4.7 compatible and old

    Currently there are several modules in CVS that are in one of three states: 1. 4.7/head compatible, 2. 4.6 modules that are in development and 3. old modules that have not been updated for awhile, which is why they only reside in CVS.


    Subscribe with RSS Subscribe to RSS - Deprecated - Documentation