I'm sorry for uncomplete post (careless touch touchpad) I am
continuing by the second paragraph.

The fix is written according the latest Django recommendation and the
changes are small but important. The code and templates work good with
all Django 1.2, 1.3, 1.4 but the user customizations are not loaded
down by any old code.

Static files (like css, js, template images) and media files (product
images and other similad uploadable dynamically by Django are
currently by default in the same directory because it can be not
intuitive for everyone separate them. It is recommended to separate
them, otherwise the command "./manage.py collectstatic" will duplicate
product images. Separating is easy: move product images e.g. from .../
static/ to .../media/ directory and change accordingly MEDIA_ROOT.

QUESTION: Is it easy for you to separate static and media? Or you
prefer them to be the same, if you will uprgade an existing site?

Notes:
I preferred the same STATIC_URL context variable written in capital,
because it is the same in Django.

The last of four changes, part D is in
https://bitbucket.org/hynekcer/satchmo-outgoing/changeset/3848d39b63c0
if you would search it later.

(Settings for 1.4 are very similar and not critical. Django 1.2 is
currently unimportant and unsupported in the development version very
soon after the final 0.9.2 (due to node 5d01ced130fb). But with exact
0.9.2 it worked good with 1.2 out of box with different settings.py
(media url was classical /static/))

--Hynek

On 17 dub, 19:48, hynekcer <[email protected]> wrote:
> I prepared fixes for static files. I is currently for testing and
> discussion onhttps://bitbucket.org/hynekcer/satchmo-outgoing
> Exactly in 4 changesets A, B, C, D
> A) change in the code - apply
> B) changes in templates - apply similarly to own customized templates
> C) documentation
> D) changed skeleton for Django 1.3 (minimalistic change) apply
> similarly to own settings.py
>
> It is written according the latest Django recommendation. The code and
> templates work good with all Django 1.2, 1.3, 1.4. (Settings for 1.4
> is very similar and not critical. Django 1.2 is currently unsupported
> in dev very after final 0.9.2 but if someone is interested e.g. for
>
> , but Django
>
> The last of them D is 
> inhttps://bitbucket.org/hynekcer/satchmo-outgoing/changeset/3848d39b63c0

-- 
You received this message because you are subscribed to the Google Groups 
"Satchmo users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/satchmo-users?hl=en.

Reply via email to