>>>>I was just answering your question:
>>>>
>>>>"Also, what do you normally do in such situations when you're the only one getting errors in the code which is supposed to error. Do you try to find the reason or just fix them?"
>>>>
>>>>If you didn't intend doing the former then why ask the question ? :-}
>>>
>>>Just to get general opinion and others experience in such perplexing situations.
>>
>>Well I gave my opinion. Seems to me you've just done the equivalent of putting that code in a try/catch and ignoring the exception. And, since you have failed to identify the original source of the problem, you can't know whether it, or your fix, may impact other parts of the application. In a word 'dangerous'
>
>I added code very similar to what we already had for similar filters. E.g. I added a check for existence of the variable before trying to access its properties. I see nothing dangerous here but rather a good practice.

That would depend on whether it's non-existence represented an error condition and, AFAICS, you have not determined whether that is true or not. If you were expecting it to be defined and it was not then you're just ducking the issue. Anyway, I don't have to use your code so it doesn't matter :-}

This fix eliminated problems for me.