Olga This won't work, you need to send the request to:
django-users+unsubscr...@googlegroups.com
(see the bottom of this email for more information.
François
On May 18, 2014, at 4:20 PM, Olga Burdonova <olgaburdon...@googlemail.com>
wrote:
> unsubscibe
>
>
> 2014-05-18 9:01 GMT+02:00 Yusuf Düzgün <ysfduzgu...@gmail.com>:
> http://yusufduzgun.com/blog/Django404/ i hope help you :) .
>
> 17 Mayıs 2014 Cumartesi 19:20:56 UTC+3 tarihinde Joris yazdı:
> Dear all, please help me with this unsolved mystery.
>
> Error: "Cannot resolve keyword u'<M2M FIELD NAME>' into field. Choices
> are: <fields of the M2M model>"
>
>
> 1) Error in admin
> In the admin it only happens when DEBUG=True. Works perfectly when
> DEBUG=False.
> The error occurs when opening the form view of the model that has the
> M2M field.
>
> 2) In code
> Here the error is also present when DEBUG=False.
> The error occurs when accessing the model field, field, for example
> self.my_m2m_field.all()
>
>
> The error doesn't happen locally on the Django/Python debug server. On
> the testing server, which is Apache2 + wsgi, it does occur. The versions
> of Python (2.7) and Django (1.5.7) are the same on both computers.
> The result is that a fellow developer is accusing me of being neglective
> with testing the code before uploading it :-(
>
> There have been people with similar problems, but it has never been solved:
> https://groups.google.com/forum/#!topic/django-users/E4UVZHf6kP8
> http://stackoverflow.com/questions/19145787/fielderror-cannot-resolve-keyword-xxxx-into-field
>
> http://chase-seibert.github.io/blog/2010/04/30/django-manytomany-error-cannot-resolve-keyword-xxx-into-a-field.html
>
> http://code.djangoproject.com/ticket/1796 (7 year old django bug which
> is reported fixed but in fact is not)
>
>
> So it seems to be a bug deep down in Django.
> This makes the use of M2M fields impossible for my application, which is
> quite a problem.
>
> Instead of trying to find the bug in Django, would anyone have any clue
> why it does work on the Python debug server and not on Apache2?
>
>
> Thank you!
> J
>
>
> --
> 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/f4184af8-10a5-4d84-b92f-448b830a1b8f%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> 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/CAEKo5h_GNuc6OAD%3DnULOUvthpY5z5%2BBJuY80GFZ5eUZshu-83Q%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP using GPGMail
