On Tue, Feb 20, 2007 at 06:14:34PM -, [EMAIL PROTECTED] wrote:
>
> Could someone review this ticket?
I started using it last week. I /really, really/ needed it and it seems to
work fine in a version of create_update working with newforms, so that I use
it both with form_for_model and form_fo
Simon,
I think we're both looking for the same feature. Here's another
example. Say I have an address model:
class Address(models.Model):
address1 = models.CharField(maxlength=100)
address2 = models.CharField(maxlength=100)
city = models.CharField(maxlength=32)
state = models.S
Could someone review this ticket?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, se
On 2/20/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
> 'context processor' sounds more difficult than it is. That's how it's
> actually done:
>
> from django.conf import settings
>
> def processor(request):
> return {'MEDIA_URL': settings.MEDIA_URL}
>
> ... and then add it to TEMPLATE_CONTEX
Hi,
SmileyChris schrieb:
> But whatever you use, it should be made easy to put this in all your
> template contexts without having to jump through the hoop of creating
> your own context_processor.
I'm -0 on this, I don't think it's necessary to replace such a tiny bit
of programming with just a
