Using the generic views, I came across the need for
post_delete_redirect to have dictionary string formatting (interpolated
against the objects field attributes) like post_save_redirect does
By modifying the delete function in create_update.py (line 182 in
magic-removal)
from
return HttpRe
On Wednesday 12 April 2006 18:42, Joe Button wrote:
> Hi.
>
> {% ifequal thing1.id someid %}
>
> fails if I pass None as thing1. "Failed lookup for key [id] in None"
>
> Is there a good reason for this? Shouldn't it be silently ignored
> like other non-existent things referenced in templates?
I b
Hi.
{% ifequal thing1.id someid %}
fails if I pass None as thing1. "Failed lookup for key [id] in None"
Is there a good reason for this? Shouldn't it be silently ignored like other
non-existent things referenced in templates?
Ta,
Joe
--~--~-~--~~~---~--~~
You
Hi,
the sessions middleware does not support some cookie settings I'd prefer
for security, especially since the authentication middleware depends on it:
- secure flag (i.e., if a cookie has been received via SSL, only send it
over SSL)
- discard flag (i.e., it's a non-persistent cookie being
On 4/12/06, Ian Clelland <[EMAIL PROTECTED]> wrote:
> Is the problem fixed in 2684? The relevant import line was extended to
> include the relations as well as the field types.
Should be fixed in [2685], knock on wood.
Adrian
--
Adrian Holovaty
holovaty.com | djangoproject.com
--~--~-~
> __1__. Image upload (and File upload as well) is always a required
> attribute (even if I set core to False).
OK about this question, now I know what I was missing. That is
blank=True. Perhaps I need to read documentation more carefully. :)
But could anybody comment the seconf problem and to gi
On 4/12/06, Gael Chardon <[EMAIL PROTECTED]> wrote:
> After this update, none of my models is "loaded".
>
> Is there any major change in the db "model" ?
Is the problem fixed in 2684? The relevant import line was extended to
include the relations as well as the field types.
Ian Clelland
<[EMAIL
(latest MR)
I suspect that this have something to do with related field which have
unique_together and edit_inline=True set. You can
see example with my translation model from
http://djangoutils.python-hosting.com/file/trunk/nesh/translation/models.py
(Message and Registry models).
If I try to
Ok thx..
And for my second problem .. it was, as usual, a difference between
'head' and 'magic-removal' branch : django.contrib.auth.models vs
django.models.auth
Thx.
--
Gaël Chardon
--~--~-~--~~~---~--~~
You received this message because you are subscribed t
Gael Chardon wrote:
> hum I'm wrong .. seems to be more complicated than this "import fix"
>
> I'm trying to find why my model does not work after this couple of
> updates...
>
There are more missing imports see http://code.djangoproject.com/ticket/1623
--
Nebojša Đorđević - nesh
Studio Quatt
ok.. so here my two problems:
1/ [2683] breaks models (see first post)
2/ If I add a field related to models.auth.User
e.g. users = Models.ManyToManyField(models.auth.User, verbose_name =
_('users'))
it also breaks models (then, none of my model is available), and this
"feature" is not related t
hum I'm wrong .. seems to be more complicated than this "import fix"
I'm trying to find why my model does not work after this couple of
updates...
--
Gaël Chardon
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"
http://code.djangoproject.com/changeset/2683
After this update, none of my models is "loaded".
Is there any major change in the db "model" ?
Reversing fix the problem.
-- django.db.models.fields.related import ForeignKey, OneToOneField,
ManyToManyField
++ django.db.models.fields.related import
13 matches
Mail list logo
