Hi there, I am giving Mathias's fork a go to see if we can use it to deploy a multilingual site solution. I forked it here <https://github.com/cccs-web/mezzanine> and set up a branch of our mezzanine site to use it and define the modeltranslation stuff.
I am starting to raise issues against our fork which I'm attempting to address as I go. For example https://github.com/cccs-web/mezzanine/issues/1 My question is; Is this a good approach, given that I need a pragmatic solution but also want to be maximally helpful to getting any fixes into the mezzanine code base? On Tuesday, 10 June 2014 22:42:41 UTC+10, Mathias Ettinger wrote: > > Just corrected a few things for the front-end language selector and pushed > an updated version of cartridge as well. > > I tried the TabbedExternalJqueryTranslationAdmin class instead of > TranslationAdmin and couldn’t get the meta tag area to show. Does it happen > for you too? Or is there something else to do in order to get it working? > > If it is not possible to show extra area like this that are hidden by > default, we definitely need to write our own custom class on top of > TranslationAdmin (meaning: core.BaseTranslationModelAdmin). I’m also unsure > if Translation{Tabular,Stacked}Inline also need to integrates some > tabbing-awareness code (wether it is a global switch or a per field one). > But I modified a little bit their admin classes to help integrate it if > needed. > > > Le samedi 7 juin 2014 02:26:50 UTC+2, Eduardo Rivas a écrit : >> >> Hey everybody. I've been trying out Mathias master branch and everything >> is working smoothly. As I said, I'm also exploring ways to enable toggling >> translation fields in the Admin. Turns out Model Translation (MT) provides >> two admin classes (docs >> <https://django-modeltranslation.readthedocs.org/en/latest/admin.html#tabbed-translation-fields-admin-classes>) >> >> to include the required static resources for this purpose: >> TabbedTranslationAdmin >> and TabbedExternalJqueryTranslationAdmin. The first one seems to fail as >> it uses Django's jQuery, but the second one works as expected (though it >> looks kinda ugly in Grappelli) by using external jQuery resources. >> >> I have a couple of questions at this point: >> >> 1. Should we use these classes or create our own (considering >> Mezzanine already includes jQuery and jQuery UI)? >> 2. Should we create a toggle for each field (as MT does), or just a >> "global" toggle to hide/show all fields of a specified language? I favor >> the second option, as giving each field it's own toggle seems overly >> messy >> and confusing for the end user. >> >> Hope to hear from you soon. BTW, if you want to try out MT's default >> implementation, simply replace all occurrences of TranslationAdmin with >> TabbedExternalJqueryTranslationAdmin >> in mezzanine.core.admin. >> > -- 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.
