Any thoughts on this implementation? https://github.com/Romamo/mezzanine-modeltranslation/blob/master/mezzaninemodeltranslation/translation.py
It was mentioned in the discussion against the pull request but no comments were made. I really like how this approach doesn't require any change to Mezzanine itself, as opposed to the proposal here which is a real concern. On Mon, May 26, 2014 at 10:52 PM, Mathias Ettinger < [email protected]> wrote: > I need to take a decision, so I’ll ask here instead. > > I was trying to write some tests for modeltranslation integration and I > stumbled upon an issue. Basically I was trying to test that slugs are > always generated based on the default language using the model logic > (Page.save()) whereas the slug issue was fixed using the admin logic > (ModelAdmin.save_model()). > > Obviously my test fails. But I’m wondering wether it should be fixed by > testing the admin behavior or by implementing the slug logic into the Page > model. > > As a more general question, there are some fields that are auto-populated > based on other one and both are marked for translation. They are handled by > the admin which saves the model several times (one for each language). Is > it acceptable or should this logic be moved to the Displayable model? > > -- > You received this message because you are subscribed to the Google Groups > "Mezzanine Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Stephen McDonald http://jupo.org -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
