I had been getting "Model doesn't have field xxx" errors in the admin, and got a quick solution up myself, because I didn't have the time to figure out what's wrong. I simply added field_lang columns to my model, and wrote a template tag to fetch the correct column based on column basename and the current's request language.
Also, I had to explicitly import and subclass the Translation class for the inner Translation class in models. This one wasn't in the docs. I guess d-m is cleaner, but the lack of documentation made me write my own. Anyone about admin usage? El dom, 07-10-2007 a las 16:09 +0000, Alex Koshelev escribi�: > I've use django-multilingual in many projects and happy. It's simple > to integrate and use. No other implementations can do it so > transparent for developer and end user( django-multilingual extends > admin edit page and allows edit entry in all languages very simple). > Use it! > > Chris Hoeppner: > > Hi there! > > > > I wonder if someone has been using django-multilingual. I'd like to > > "push it into" a live database, and am wondering what kind of > > alterations to the schema this might involve. Would it be easier to just > > add _lang columns for all the fields I'd like to translate, and > > conditionally outputting based on the LANGUAGE context var? It seems > > cleaner and more flexible the way django-multilingual goes, but the > > alterations are frightening me a bit. > > > > ~Chris > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
