Our Django application uses South to
manage database migrations for model changes. South seems to be universally
recommended and generally quite capable at its job. But when I went to do a
fresh install of our project, ./manage.py migrate failed with
messages about missing tables or no-such-relation. Where did things go
wrong?
The answer is in how South handles multiple apps. (Continued…) …
We had a case where we wanted to replace some static text in a template with
some text that changed depending on who was logged in. Textbook webdev 101
stuff. We added a property on the relevant model to return the correct
phrase, we made sure that the model was accessible from something in the context, replaced the text in the template with a
reference to this in some {{ curly
brackets }} … and we came up with nothing. Or it showed
up in some cases but not in other cases where we applied the
|title filter.