I opened a ticket here:
http://code.djangoproject.com/ticket/2949
If anyone is interested, I can explain in more detail why this is a
problem and a proposed workaround I have in mind. I'm willing to write
a patch if anyone is interested, but I can't see a way for doing this
in a backwards-incompa
Hi,
I grew myself a way to output warnings in a similar way as
validations work, and I also use this to check domain names,
giving an error when the name does not resolve (this is work for
an ISP ...) For the purpose of this email, you can just consider
these warnings the same as normal valid
I'm trying to do some form of skinning with Django's templating engine.
Without going into too much detail, my project is kindof a service that
powers multiple sites. Each site can have a skin inside a site-specific
folder. These folders are not parallel to each other.
for example:
myapp/webroot
It shouldn't be. You're right.
The problem is the FormFields and Manipulators are in a sort of limbo
right now. And until we hear from the overworked core devs about it,
not much can be done.
On 10/20/06, Max Derkachev <[EMAIL PROTECTED]> wrote:
>
> FormField and its subclasses should define h
It's been noted serveral times that the Template engine is too closely
tied to the settings, which in turn is too closely tied to the core.
No one has offered a well made and clearly defined solution as to how
to really seperate it, to the best of my knowledge.
This should be discussed.
Aside:
I
In Django, URLField is still limited to 200 characters. Well, half
limited. After a ticket about this before, (#1477), a change was added
to validation, so that a maxlength parameter in your model will
override the 200 character limit for a url in validation, and in the
input form. However, beca
