Hi Jonas!
First of all, thanks for your hard work to make this module available
on Django 1.2. I'm trying to use it, but i've got a problem:
I can use the admin interface to create my flat page in the languages
that I need (brazilian portuguese and english). When I go to the site,
I can see it in the language previously defined. But if I try to
change the language, I receive a CSRF verification failed. Request
aborted.
I'm using Django 1.2 (beta 1) and django-multilingual-ng-0.1.20.
I created a template named languages.html to encapsulate this
function. The actual code is:
<form action="/i18n/setlang/" method="post">{% csrf_token %}
<input name="CSRF_Value" type="text" value="{{ CSRF_TOKEN }}" />
<input name="next" type="hidden" value="/next/page/" />
<select name="language">
{% for lang in LANGUAGES %}
<option value="{{ lang.0 }}">{{ lang.1 }}</option>
{% endfor %}
</select>
<input type="submit" value="Go" />
</form>
It is the default template suggested on the DjangoBook.com, Chapter
19. I just added the csrf_token and the input to show its value.
When the page is shown, the value of CSRF_Value input is NOTPROVIDED.
I'm a newbie on python, so maybe I'm making a mistake and can't find
it. I hope you can help me.
Thanks in advance,
Vinicius Ronconi
On 19 fev, 06:47, Jonas Obrist <ojiido...@gmail.com> wrote:
> Since the official django-multilingual [1] does not support Django 1.2 (and
> has some other annoying things in my opinion), I decided to create a new
> project based off django-multilingual which works in 1.2 and has some other
> improvements. This project is called django-multilingual-ng, it's on the
> cheeseshop [2] (so you can easy_install/pip install it) and github [3].
>
> Changes from django-multilingual:
>
> - django 1.2 (beta 1) compatible
> - deprecated language_id's in favour of languege_code's to make code easier
> to write and allow changes to settings.LANGUAGES without corrupting the
> database
> - admin UI improvements (a tabbed interface for languages instead of showing
> all languages inline and forcing users to fill all of them in)
> - an easy command to convert django-multilingual apps to
> django-multilingual-ng (database migration, requires south)
>
> The high level API stays the same, this means you can use the same syntax to
> make your models multilingual as in django-multilingual. Due to the
> language_id depreciation some low level APIs have changed. However they
> should make things easier, not harder.
>
> Currently the two things this project is missing is documentation and more
> testing. I've tested it in my project and I can't find any issues.
>
> If you have a look at it and maybe even use it, please give me your feedback
> and especially report any bugs you encounter.
>
> Jonas Obrist
>
> [1]http://code.google.com/p/django-multilingual/
> [2]http://pypi.python.org/pypi/django-multilingual-ng/0.1.0b1
> [3]http://github.com/ojii/django-multilingual-ng
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
