ojii / django-multilingual-ng

THIS PROJECT IS *NOT* SUPPORTED AND SHOULD NOT BE USED UNLESS YOU KNOW EXACTLY WHAT YOU'RE DOING!!!

Home Page:https://github.com/KristianOellegaard/django-hvad

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Addition translation in admin

vasylnakvasiuk opened this issue · comments

For example:
When I have models with 3 lang, in admin I add translation for one lang and save... But no error was appeared. I think, if fields in model are required - translation must be required too.
And, if I add translation for only one lang - changing translation in my site doesn't work.

When I add translation - I must restart server... Otherwise, changing lang (POST method) doesn't work.

Hi vaxXxa

I am afraid I do not understand the issue you have. Could you please provide me with the code you use that generates this issue? Also please tell me your Django version and django-multilingual-ng revision.

I use:
Django 1.2 alpha
Python 2.6.4
ojii-django-multilingual-ng-3efca42

class NewsPost(models.Model):
author = models.ForeignKey(User, verbose_name=('Автор'), related_name='newsposts')
class Translation(multilingual.Translation):
title = models.CharField(
('Заглавие'), max_length=150)
body = models.TextField(('Текст'))
timestamp = models.DateTimeField(
('Дата'))
comment = models.TextField(_('Примечание'), blank=True)

  1. WHen I try to add first instance of NewsPost's models by admin page, the first problem is ---> language: None
  2. Then I enter data and click "Save". New NewsPost's object has been saved, but if I open again this object - there are no data, but I can see normal lang ---> language: en, uk, ru... (because, data entered to "language: None")
  3. I think, if fields in model are required - translation must be required too.
    So, I don't understand. If I entered data only in one lang tab (for example "en"), and save. And, after that change in my site lang to "ru". But there no any data!!!! So, translation must be required.

please use the lastest revision of django-multilingual-ng, that bug has been fixed.

really!)))
sorry) thnx)

no worries, thanks for reporting it