For some reason I tried this (probably a result of the mindset necessary for hacking around IE's CSS bugs)... in my templates which are the master for another template, I made the following change:
On any element that contained a py:def, I made sure that the py:def was the FIRST attribute. I haven't tested this enough to be sure, but this might just be a bug where kid doesn't see the py:def under certain circumstances (what, I don't know)... resulting in trying to call a NoneType at the point where you later try to use that function. An initial romp through my app says this probably fixed it. I'll report back later with something more definitive. Anyway... HTH...
