Re: weird ifnotequal issue

2011-03-08 Thread Bill Freeman
That's a weird field name. I could see there being a corner case. If it were me, I'd stick a breakpoint in the ifequal implementation, possibly, if you have a lot of other ifequal tags to get past conditioned (normal python if statement) on having gotten "." in the arguments. Then you can see

weird ifnotequal issue

2011-03-06 Thread Bobby Roberts
fieldname does in fact equal "-" so why is the TR still showing? {% ifnotequal mymodel.fieldname"-"%} Flagged Reason {{mymodel.fieldname}} {%endifnotequal%} -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group,