[mezzanine-users] Adding a third-party app to a multilingual site using modeltranslations

2015-06-12 Thread Lee H.
*Background* I created a multilingual site theme for mezzanine using the new multi-lingual support. I had to do two things: 1) Add translations.py file to the theme app, which defined translations for my custom page models that subclass Mezzanine pages. 2) Split my theme app into two apps:

[mezzanine-users] error on create mezzanine Multi-Lingual Sites?

2015-06-12 Thread سید محمد رضا طباطبائی
i do this work to make multi lingual Sites whit mezzanine 1- $ mezzanine-project test cd test 2- edit setting.py USE_MODELTRANSLATION = False to USE_MODELTRANSLATION = True 3- add another languge to LANGUAGES in setting.py 4- run $python3 manage.py createdb but show this message $ python3

[mezzanine-users] Re: Enable Mezzanine multilingual site support

2015-06-12 Thread سید محمد رضا طباطبائی
i tested but don't work show this message $ python3 manage.py createdb /usr/local/lib/python3.3/dist-packages/Mezzanine-3.1.10-py3.3.egg/mezzanine/ utils/conf.py:51: UserWarning: You haven't defined the ALLOWED_HOSTS settings, which Django requires. Will fall back to the domains configured as

[mezzanine-users] Re: EXTRA_MODEL_FIELDS and django 1.8 migration

2015-06-12 Thread Sergey Maranchuk
Tnx! MIGRATION_MODULES helped пятница, 12 июня 2015 г., 19:33:09 UTC+3 пользователь Mathias Ettinger написал: Hi Sergey, Since you’re using the development version of mezzanine, you'd better of reading the development version of the documentation. Have a look at the “Field Injection

[mezzanine-users] EXTRA_MODEL_FIELDS and django 1.8 migration

2015-06-12 Thread Sergey Maranchuk
In django 1.8 migration i can't set app_label in migration file and looks like not possible create migration in app A for app B. Any ideas? -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving

[mezzanine-users] Re: EXTRA_MODEL_FIELDS and django 1.8 migration

2015-06-12 Thread Mathias Ettinger
Hi Sergey, Since you’re using the development version of mezzanine, you'd better of reading the development version of the documentation. Have a look at the “Field Injection Caveats” section of https://github.com/stephenmcd/mezzanine/blob/master/docs/model-customization.rst Any feedback will

[mezzanine-users] Re: error on create mezzanine Multi-Lingual Sites?

2015-06-12 Thread Mathias Ettinger
Hi, Can you confirm that you’re using the development version of Mezzanine and not the version available through pip. Also what is your version of Django and django-modeltranslation? Even though it might not be related, you mentionned adding languages to settings.LANGUAGES; but do you have a

Re: [mezzanine-users] Adding a third-party app to a multilingual site using modeltranslations

2015-06-12 Thread Eduardo Rivas
Hey Lee. Their Readme says it's compatible up to Django 1.5. You're using 1.8 or 1.7. Could you verify against a vanilla Django project to see if you get the same error? https://github.com/dokterbob/django-newsletter/blob/master/README.rst#compatibility -- You received this message because you

Re: [mezzanine-users] Enable Mezzanine multilingual site support

2015-06-12 Thread Lee H.
Thanks Mathias, I think it must have been using the old ordering of INSTALLED_APPS, since my settings file came from pre-upgrade Mezzanie. On a clean Mezzanine, I no longer got the error. -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To

Re: [mezzanine-users] Enable Mezzanine multilingual site support

2015-06-12 Thread Mathias Ettinger
Hi Lee, To possibilities to fix your problem. Either you manually added modeltranslation to INSTALLED_APPS in a place that is too deep in the loading chain, in this case, just remove it. Turning on USE_MODELTRANSLATION will automatically add it to the list. Or you used the ordering of

Re: [mezzanine-users] Adding a third-party app to a multilingual site using modeltranslations

2015-06-12 Thread Lee H.
Hey Eduardo, Many thanks for the reply. Yes, you are right, using the django-newsletter development branch from github (which has upgrades for the newer django migrations without south) things worked, and this error no longer occurred. -- You received this message because you are