UI errors should never result from the normal operation of an addon. A nil check should really be placed in the code to prevent it from throwing an error :P
Couldn't agree more. Normally I'd immediately throw away an addon that spewed out Lua errors like this. I guess I am accepting them because this addon is simply too useful. While it does seem like there are no bad effects of these errors, I really do hope the author or current maintainer will do something about them. If it happened in a program I had developed, I would feel embarrassed.
I patched one of the errors in my own copy by simply checking for nil and then doing nothing. That has worked fine so far it seems.
Yeah I should patch my local copy as well, and maybe dump some debug data to see what is actually going on.