updating members of modelformset with unique fields
http://stackoverflow.com/questions/30425468/django-updating-members-of-modelformset-with-unique-fields
The situation - I have a model and inline formset like:
class ProductImage(models.Model):
product = models.ForeignKey('Product')
display_order = models.PositiveSmallIntegerField(default=0)
class Meta:
unique_together = (('product', 'display_order'),)
inlineformset_factory(
Product, ProductImage, form=ProductImageForm, extra=1)
In the front end I provide a UI to reorder the images for a given product.
The problem:
- Let's say I already saved two images attached to .
- These two images have display_order=0 and display_order=1 respectively.
- now I upload a third image, give it display_order=0 while renumbering
the existing images to display_order=2 and display_order=1 respectively.
At this point I get a validation error for the unique check.
Looking through Django source code we find this in BaseModelFormSet.save:
return self.save_existing_objects(commit) + self.save_new_objects(commit)
...ok that looks all good, it will save (update) the existing objects
first. So from the perspective of the db there is no conflict in the unique
constraints.
The problem is that saving comes *after* validation, or course, and at the
point of validation the new objects will conflict with existing ones in the
db.
It seems like BaseModelFormSet needs some mechanism whereby it could take
into account the about-to-be-updated values from its form instances.
Does anyone have a workaround that does not involve pushing the problem
onto the user?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/c368d2c7-098e-4e66-94de-0406442ebead%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Reverse Lookup Failure on password change/reset views
Hmm, well after looking at the source of the `reverse` method I can see
that it's not doing what I imagined it was...
I am so used to always naming my urls in urlconfs, when I saw a full import
path to a view function like:
reverse('django.contrib.auth.views.password_reset_done')
in the auth/views.py I assumed it ought to find that vew function in
whichever urlconf it was defined
Thinking about it, it can't do that because you could easily have more than
one url pointing to that function
It means if you have something like this in your root urlconf:
(r'^accounts/', include('django.contrib.auth.urls', namespace="auth")),
then the reverse isn't going to work because it would have to be:
reverse('auth:django.contrib.auth.views.password_reset_done')
in short, don't use a namespace on the built-in auth urls
Arguably, the auth views could work out what namespace they're under and
handle it though, eg:
(django/contrib/auth/views.py #147)
resolver = resolve(request.path)
ns = ''
if resolver.namespace:
ns = resolver.namespace + ':'
post_reset_redirect =
reverse('{0}django.contrib.auth.views.password_reset_done'.format(ns))
(admittedly this assumes you have imported all of the auth urls into the
same namespace)
On Monday, 19 August 2013 12:27:57 UTC+1, anentropic wrote:
>
> This seems a bug in Django... the `reverse` function is passed the name of
> a view function, not a named url, so the fact that the url it's being asked
> to match is included under a namespace shouldn't matter?
>
> (here because I just hit the same problem myself)
>
> On Saturday, 27 July 2013 08:20:18 UTC+1, Peter wrote:
>>
>> Yep, that fixed it. Thanks.
>>
>> I still think it's wrong of django not to find it by view name though...
>>
>>
>>> Probably because you've included it under a namespace, so Django would
>>> need to look for it as "registration:whatever". There's no need to use the
>>> namespace in the include call.
>>> --
>>> DR.
>>>
>>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Reverse Lookup Failure on password change/reset views
This seems a bug in Django... the `reverse` function is passed the name of a view function, not a named url, so the fact that the url it's being asked to match is included under a namespace shouldn't matter? (here because I just hit the same problem myself) On Saturday, 27 July 2013 08:20:18 UTC+1, Peter wrote: > > Yep, that fixed it. Thanks. > > I still think it's wrong of django not to find it by view name though... > > >> Probably because you've included it under a namespace, so Django would >> need to look for it as "registration:whatever". There's no need to use the >> namespace in the include call. >> -- >> DR. >> > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: UnicodeDecodeError (ordinal not in range) when deleting an inline item - 1.2.1
Awesome, I had exactly the same problem and by chance we're on Rackspace too. I added the two lines to that file exactly as shown in the Django docs, restarted httpd, and now Sorl can handle thumbnails with unicode chars in them. cheers On Jun 27, 4:44 pm, Federico Capoano wrote: > Thanks for your help. I've been able to fix the problem thanks also to > the Rackspace technical support. > > This is the answer, i post it cos it might be useful to someone else: > > "Greetings, > > I've added the two lines you provided to /etc/sysconfig/httpd- a file > which is 'sourced' by the apache startup script and exists for exactly > this kind of need. > > To get these statements to take effect, I've restarted the httpd > service. Those two new environment variables should now exist on all > Apache processes and their child processes. > > Please test and let me know of you're still seeing the UnicodeError, > some other error, or if things are now working properly. > > Pleasure to help you; If you have any concerns or questions, please > let me know." > > On Jun 21, 12:42 pm, Matt Hoskins wrote: > > > > > Federico, > > > When trying out what Karen suggests then in the unlikely event that > > Red Hat doesn't load the environment variables from /etc/apache2/ > > envvars, one way to find it without consulting documents is to look at > > the apache start-up script (e.g. /usr/sbin/apache2ctl) so find that on > > your server and look at what that loads - for example the copy I've > > got has the following: > > > # the path to the environment variable file > > test -z "$APACHE_ENVVARS" && APACHE_ENVVARS='/etc/apache2/envvars' > > # pick up any necessary environment variables > > if test -f $APACHE_ENVVARS; then > > . $APACHE_ENVVARS > > fi > > > Of course as you can see from that it's possible to set an environment > > variable before running apache2ctl to change the location of envvars, > > but it's unlikely they'd do that. > > > Matt > > > > I am not familiar with Red Hat so I can't give you any more specific > > > advice > > > than that. If it does not use /etc/apache2/envvars (or if you are using > > > some > > > server other than Apache), then you need to consult the Red Hat doc or > > > forums to find out how to configure your web server to run with a LANG > > > other > > > than C or whatever it is currently using.- Hide quoted text - > > > - Show quoted text - -- 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.
signals and "weak reference"
in the docs there is this paragraph: "Note also that Django stores signal handlers as weak references by default, so if your handler is a local function, it may be garbage collected. To prevent this, pass weak=False when you call the signal’s connect()." Can someone please explain to me what it means? what's a "local function" in this sense? a function in the same file as the signal_name.connect(...) call? what is the rationale for the weak reference behavior, presumably it's desirable most of the time? -- 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.
Re: weird import errors in my middleware
Well, it seems pretty clear from a few further tests that you can't import models at all from within a middleware. Would be nice if that limitation was documented On Apr 16, 9:12 pm, anentropic wrote: > if it helps, my exclusive_boolean_fields function looks like: > > def exclusive_boolean_fields(model, eb_fields=[], with_fields=[]): > setattr(model, '_exclusive_boolean_fields', eb_fields) > setattr(model, '_exclusive_boolean_with_fields', with_fields) > post_save.connect(exclusive_boolean_handler, sender=model) > > ...so it's using a model signal. > > I can also import and use the middleware class just fine from the > shell. > > -- > 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 > athttp://groups.google.com/group/django-users?hl=en. -- 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.
Re: weird import errors in my middleware
if it helps, my exclusive_boolean_fields function looks like: def exclusive_boolean_fields(model, eb_fields=[], with_fields=[]): setattr(model, '_exclusive_boolean_fields', eb_fields) setattr(model, '_exclusive_boolean_with_fields', with_fields) post_save.connect(exclusive_boolean_handler, sender=model) ...so it's using a model signal. I can also import and use the middleware class just fine from the shell. -- 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.
weird import errors in my middleware
Hi,
I tried to write my first middleware today and seem to have failed
horribly.
Basically I have made a view decorator almost identical to the csrf
ones, that sets a flag on the view function. My middleware then checks
this flag and if missing it runs another function (which deletes some
session variables)
My middleware looks like:
from MySite.cart.checkout.views import _checkout_cleanup
class ReleaseOrderMiddleware(object):
def process_view(self, request, view_func, view_args,
view_kwargs):
if getattr(view_func, 'preserve_order_details', False):
_checkout_cleanup(request, True)
return None
If I turn this on I get errors like:
ImproperlyConfigured: Error importing middleware
MySite.cart.checkout.middleware: "cannot import name
exclusive_boolean_fields"
Well, exclusive_boolean_fields is a function, basically a decorator I
apply to my models. The weird thing is it's not imported directly
anywhere in the middleware or _checkout_cleanup function.
_checkout_cleanup does do this though:
def _checkout_cleanup(request, abort_order):
if CHECKOUT_KEY_ORDER in request.session:
if abort_order:
order = request.session[CHECKOUT_KEY_ORDER]
order.restore_stock()
order.delivery = Decimal('0.00')
order.delivery_label = ''
order.status = cart_models.ORDER_STATUS_ABORTED
order.fulfillment_status =
cart_models.FULFILLMENT_STATUS_ABORTED
order.save()
del request.session[CHECKOUT_KEY_ORDER]
...so we're working with a model object there.
I realise this code doesn't make an easy test case for others, but I'm
hoping I have made a basic 'aha!' type of blunder.
eg, is it possible to work with model objects at all in the middleware
layer?
Why would I get that import error?(The _checkout_cleanup method
works fine from within a view.)
--
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.
Re: formset media
{{ formset.media }} will output the script tags *and* the css link
tags
On Feb 22, 11:53 am, anentropic wrote:
> A formset should have a 'media' attribute which should include all the
> media from the widgets in the forms which make up the formset, so in
> the template you should be able to just
> {{ name_of_formset_var.media }} in the head of your page to output the
> necessary script tags.
>
> On Feb 17, 3:13 pm, kkerbel wrote:> Anybody? :)
>
> > On Feb 17, 1:19 am, kkerbel wrote:> I'm having trouble
> > getting AdminDateWidget to show in a formset. Is
> > > this possible? I've read and followed every post that mentions how to
> > > do this and I even have a page working with the AdminDateWidget,
> > > however, it uses a regular form and not a formset. I'm just having
> > > trouble getting it to show on a template using a formset. Is there a
> > > specific way to specify formset media in the template?
--
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.
Re: formset media
A formset should have a 'media' attribute which should include all the
media from the widgets in the forms which make up the formset, so in
the template you should be able to just
{{ name_of_formset_var.media }} in the head of your page to output the
necessary script tags.
On Feb 17, 3:13 pm, kkerbel wrote:
> Anybody? :)
>
> On Feb 17, 1:19 am, kkerbel wrote:> I'm having trouble
> getting AdminDateWidget to show in a formset. Is
> > this possible? I've read and followed every post that mentions how to
> > do this and I even have a page working with the AdminDateWidget,
> > however, it uses a regular form and not a formset. I'm just having
> > trouble getting it to show on a template using a formset. Is there a
> > specific way to specify formset media in the template?
--
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.
Re: What exactly does order_with_respect_to do?
I've been wondering this too, the docs aren't clear. On Nov 30, 12:50 am, Continuation wrote: > In the doc (http://docs.djangoproject.com/en/dev/ref/models/options/ > #order-with-respect-to) it is mentioned that order_with_respect_to > marks an object as "orderable" with respect to a given field. > > What exactly does that mean? Can someone give me an example of how > this could be used? > > The doc's example is: > order_with_respect_to = 'question' > > How is that different from > ordering = ['question'] -- 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.
many-to-many relation field__in - how to AND instead of OR?
I have a query like: Product.objects.filter(categories__in=cat_ids).distinct() where categories is a m2m field. As I understand it this loads products which have belong to ANY of the categories in cat_ids How would I load only products which belong to ALL of the categories in cat_ids? (is this possible in ORM?) I think in SQL you'd have to change the one IN clause to a series of ANDs -- 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.
Re: CommaSeparatedIntegerField - no suitable widget?
Ok, so the model, the formfield and the widget each take a 'choices' attribute. You have to specify the choices on the formfield for any choices to show up. incidentally the styling of CheckboxSelectMultiple seems to be buggered in the admin, on a Mac at least (FF and Safari) On Nov 18, 12:06 pm, anentropic wrote: > I am trying to use a CommaSeparatedIntegerField in one of my > models... there doesn't seem to be a suitable widget for editing this > field though? > > Seems like one of the 'select multiple' widgets would be an obvious > choice. SelectMultiple seems the default widget for it in admin, but > it renders an empty list. I wanted to use CheckboxSelectMultiple but > that renders nothing (same problem I guess) > > It even renders nothing if I specify the 'choices' again on the form > field. > > How are you supposed to use these things? -- 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=.
CommaSeparatedIntegerField - no suitable widget?
I am trying to use a CommaSeparatedIntegerField in one of my models... there doesn't seem to be a suitable widget for editing this field though? Seems like one of the 'select multiple' widgets would be an obvious choice. SelectMultiple seems the default widget for it in admin, but it renders an empty list. I wanted to use CheckboxSelectMultiple but that renders nothing (same problem I guess) It even renders nothing if I specify the 'choices' again on the form field. How are you supposed to use these things? -- 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=.
Re: syndication feed framework - how to reverse the urls?
ok, thanks!
On Oct 5, 12:09 pm, Russell Keith-Magee
wrote:
> On Mon, Oct 5, 2009 at 6:31 PM, anentropic wrote:
>
> > So I just have to hard-code the feed urls in my templates?
>
> In short, yes.
>
> The feeds framework predates the introduction of named URLs in Django,
> and as a result the original implementation didn't include named urls.
> The feeds framework is badly in need of a rewrite, and this is one of
> the issues that needs to be addressed.
>
> Yours,
> Russ Magee %-)
>
>
>
> > On Sep 30, 3:23 pm, anentropic wrote:
> >> Anyone? Is it possible to reverse those urls?
>
> >> The feeds framework implementation seems like a dirty hack to urls.py
> >> (but otherwise works great!)
>
> >> On Sep 29, 4:57 pm, anentropic wrote:
>
> >> > I've been setting up feeds using the syndication feed framework.
>
> >> > I have a line like this in my urls.py:
>
> >> > (r'^feeds/(?P.*)/$', 'django.contrib.syndication.views.feed',
> >> > {'feed_dict': feeds}),
>
> >> > How do I avoid hard-coding the feed urls into my template?
>
> >> > I want to {% url django.contrib.syndication.views.feed.feed_name
> >> > params %} in my html templates to generate the
> >> > tags
>
> >> > ...but it doesn't work for me (should it?)
--~--~-~--~~~---~--~~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
Re: syndication feed framework - how to reverse the urls?
So I just have to hard-code the feed urls in my templates?
On Sep 30, 3:23 pm, anentropic wrote:
> Anyone? Is it possible to reverse those urls?
>
> The feeds framework implementation seems like a dirty hack to urls.py
> (but otherwise works great!)
>
> On Sep 29, 4:57 pm, anentropic wrote:
>
>
>
> > I've been setting up feeds using the syndication feed framework.
>
> > I have a line like this in my urls.py:
>
> > (r'^feeds/(?P.*)/$', 'django.contrib.syndication.views.feed',
> > {'feed_dict': feeds}),
>
> > How do I avoid hard-coding the feed urls into my template?
>
> > I want to {% url django.contrib.syndication.views.feed.feed_name
> > params %} in my html templates to generate the
> > tags
>
> > ...but it doesn't work for me (should it?)
--~--~-~--~~~---~--~~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
Re: syndication feed framework - how to reverse the urls?
Anyone? Is it possible to reverse those urls?
The feeds framework implementation seems like a dirty hack to urls.py
(but otherwise works great!)
On Sep 29, 4:57 pm, anentropic wrote:
> I've been setting up feeds using the syndication feed framework.
>
> I have a line like this in my urls.py:
>
> (r'^feeds/(?P.*)/$', 'django.contrib.syndication.views.feed',
> {'feed_dict': feeds}),
>
> How do I avoid hard-coding the feed urls into my template?
>
> I want to {% url django.contrib.syndication.views.feed.feed_name
> params %} in my html templates to generate the
> tags
>
> ...but it doesn't work for me (should it?)
--~--~-~--~~~---~--~~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
syndication feed framework - how to reverse the urls?
I've been setting up feeds using the syndication feed framework.
I have a line like this in my urls.py:
(r'^feeds/(?P.*)/$', 'django.contrib.syndication.views.feed',
{'feed_dict': feeds}),
How do I avoid hard-coding the feed urls into my template?
I want to {% url django.contrib.syndication.views.feed.feed_name
params %} in my html templates to generate the
tags
...but it doesn't work for me (should it?)
--~--~-~--~~~---~--~~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
extending comments views
Hi, I am trying to extend the comments app so that I can use an alternate view for post_comment in some situations (i.e. posting via ajax...) This question is probably largely down to relative python ignorance on my part, but 1) I have made a new app in my project and set COMMENTS_APP in settings as per docs 2) in __init__.py I have made a new get_form_target() function which returns the url to my new ajax_post_comment view 3) I want to reuse all the code in the existing post_comment view function but just ask it to use a different template. in django.contrib.comments.views.comments there is: def post_comment(request, next=None): ... ... return next_redirect(data, next, comment_done, c=comment._get_pk_val()) post_comment = require_POST(post_comment) comment_done = confirmation_view( template = "comments/posted.html", doc = """Display a "comment was posted" success page.""" ) So you can see, what I want to do is change the value of comment_done from my ajax_post_comment view, then maybe call the existing post_comment view function. I can't work out how to do this though, and it's looking like I will have to just copy and paste the existing view code into my new view. Is there some way to import post_comment and comment_done into my new views.py such that I can actually affect the value of comment_done used by the post_comment function? Any help with my DRY headache much appreciated! --~--~-~--~~~---~--~~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: custom tag - render() isn't called
Any feedback on this? I have the same problem... I have some of my own custom tags working but the ones that come with django-tagging it seems like render does not get called I've tried moving things around, putting them in the same file as my tags that do work etc. __init__ of the custom tag is called, but not render. Can anyone give any pointers where to look for a solution? --~--~-~--~~~---~--~~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
