Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Cleaned up FAQ changes from [303]

git-svn-id: http://code.djangoproject.com/svn/django/trunk@305 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit 1c947e50c92803e0a54fe7df7d32b5bd40ea54b6 1 parent 371144f
Adrian Holovaty authored July 25, 2005

Showing 1 changed file with 17 additions and 17 deletions. Show diff stats Hide diff stats

  1. 34  docs/faq.txt
34  docs/faq.txt
@@ -111,8 +111,8 @@ where it makes sense.
111 111
 <Framework X> does <feature Y> -- why doesn't Django?
112 112
 -----------------------------------------------------
113 113
 
114  
-We're well aware that there are other awesome web frameworks out there, and
115  
-we're not adverse to borrowing ideas where appropriate.  However, Django was
  114
+We're well aware that there are other awesome Web frameworks out there, and
  115
+we're not adverse to borrowing ideas where appropriate. However, Django was
116 116
 developed precisely because we were unhappy with the status quo, so please be
117 117
 aware that "because <Framework X>" does it is not going to be sufficient reason
118 118
 to add a given feature to Django.
@@ -188,7 +188,7 @@ How do I install mod_python on Windows?
188 188
     * For Python 2.4, check out this `guide to mod_python & Python 2.3`_.
189 189
     * For Python 2.3, grab mod_python from http://www.modpython.org/ and read
190 190
       `Running mod_python on Apache on Windows2000`_.
191  
-    * Also, try this (not Windows-specific) `guide to getting mod_python 
  191
+    * Also, try this (not Windows-specific) `guide to getting mod_python
192 192
       working`_.
193 193
 
194 194
 .. _`guide to mod_python & Python 2.3`: http://www.lehuen.com/nicolas/index.php/2005/02/21/39-win32-build-of-mod_python-314-for-python-24
@@ -242,20 +242,20 @@ How do I use image and file fields?
242 242
 Using a ``FileField`` or an ``ImageField`` in a model takes a few steps:
243 243
 
244 244
     #. In your settings file, define ``MEDIA_ROOT`` as the full path to
245  
-       a directory where you'd like Django to store uploaded files (for
246  
-       performance these files are not stored in the database).  Define
247  
-       ``MEDIA_URL`` as the base public URL of that directory.  Make
248  
-       sure that this directory is writable by the web user.
249  
-       
  245
+       a directory where you'd like Django to store uploaded files. (For
  246
+       performance, these files are not stored in the database.) Define
  247
+       ``MEDIA_URL`` as the base public URL of that directory. Make sure that
  248
+       this directory is writable by the Web server's user account.
  249
+
250 250
     #. Add the ``FileField`` or ``ImageField`` to your model, making sure
251  
-       to define the ``upload_to`` option to tell Django what subdirectory
252  
-       of ``MEDIA_ROOT`` to upload files to.
253  
-       
254  
-    #. All that will be stored in your database is a path to the file 
255  
-       (relative to ``MEDIA_ROOT``).  You'll must likely want to use
256  
-       the convenience ``get_<fieldname>_url`` function provided by 
257  
-       Django (that is, if your ``ImageField`` is called ``mug_shot``,
258  
-       you can get the absolute URL to your image in a template with
  251
+       to define the ``upload_to`` option to tell Django to which subdirectory
  252
+       of ``MEDIA_ROOT`` it should upload files.
  253
+
  254
+    #. All that will be stored in your database is a path to the file
  255
+       (relative to ``MEDIA_ROOT``). You'll must likely want to use the
  256
+       convenience ``get_<fieldname>_url`` function provided by Django. For
  257
+       example, if your ``ImageField`` is called ``mug_shot``, you can get the
  258
+       absolute URL to your image in a template with
259 259
        ``{{ object.get_mug_shot_url }}``.
260 260
 
261 261
 The database API
@@ -293,7 +293,7 @@ things:
293 293
       "http://www.mysite.com/admin/" in your browser, in
294 294
       "myproject.settings.admin" you should set ``REGISTRATION_COOKIE_DOMAIN =
295 295
       'www.mysite.com'``.
296  
-      
  296
+
297 297
     * Some browsers (Firefox?) don't like to accept cookies from domains that
298 298
       don't have dots in them. If you're running the admin site on "localhost"
299 299
       or another domain that doesn't have a dot in it, try going to

0 notes on commit 1c947e5

Please sign in to comment.
Something went wrong with that request. Please try again.