On Tue, Nov 4, 2008 at 7:36 AM, nazar <[EMAIL PROTECTED]> wrote: > > Now I got it!!! > > I had TEMPLATE_STRING_IF_INVALID = 'TEMPLATE_STRING_IF_INVALID' > > So that 'items' was rendered as 'TEMPLATE_STRING_IF_INVALID' (and I > saw it clearly). And I met the bug, bacause gettext was unable to use > it as int parameter. > > Now I cleared this: TEMPLATE_STRING_IF_INVALID = '' and bug > disappeared. >
Yes, the admin rather relies on TEMPLATE_STRING_IF_INVALID being empty. See: http://docs.djangoproject.com/en/dev/ref/templates/api/#invalid-template-variables http://code.djangoproject.com/ticket/3579 However, this particular case is a genuine bug in the admin templates. Even with an empty TEMPLATE_STRING_IF_INVALID, the wrong message is displayed when there is only one error to be corrected on the page. I've opened a ticket to get that (and anywhere else in the admin that this construct is used) fixed: http://code.djangoproject.com/ticket/9514 Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
