Re: #19182 backport request

On Friday, February 14, 2014 6:49:26 PM UTC+1, Chris Wilson wrote: > > I'm afraid that the documented feature is totally broken. > I have to disagree, the feature works as advertised as long as you don't use the combination of a custom filter and span relations. Regards, Florian -- You

Re: #19182 backport request

Hi Tim, On Fri, 14 Feb 2014, Tim Graham wrote: I sympathize with your frustration. On the other hand as we have over 500 bugs in Trac, and I'm not sure starting to accept documentation requests for them is the best use of our resources. I'm not sure the feature is really completely broken

Re: #19182 backport request

I sympathize with your frustration. On the other hand as we have over 500 bugs in Trac, and I'm not sure starting to accept documentation requests for them is the best use of our resources. I'm not sure the feature is really completely broken enough to warrant removing it from the docs? On

Re: #19182 backport request

Hi all, On Fri, 14 Feb 2014, Florian Apolloner wrote: as Tim noted on the ticket, we are not going to backport this as per our policy. In that case will you accept patches to remove description of the broken feature from the documentation for 1.4, 1.5 and 1.6? Cheers, Chris. -- Aptivate |

Re: #19182 backport request

Hi, as Tim noted on the ticket, we are not going to backport this as per our policy. Cheers, Florian On Friday, February 14, 2014 1:53:21 PM UTC+1, Chris Wilson wrote: > > Hi all, > > I just ran into bug #19182 : > > ModelAdmin filtering didn't

#19182 backport request

Hi all, I just ran into bug #19182 : ModelAdmin filtering didn't work when list_filter includes a ('fieldname', ClassName) tuple, but throws a SuspiciousOperation exception instead. The ChangeList would display fine, but as soon as you tried to use