Carl,
While all those notices (notices beat errors anyday
) may look like something has gone terribly wrong, they are actually absolutely harmless and are simply a product of implementing the functionality.
To explain a little more: Basically I added several properties to the configuration data to specify which roles the block will support. These properties are represented by the check boxes you see on the configuration page. The role specific capability is based around checking against these properties each time the block is printed or the configuration edited. If it so happens that you have not yet edited the configuration at all, then these properties are not set and really do not even exist yet (remember the data is only recorded once you access and save the configuration settings). Since the block checks for them every time it prints itself, those notices are just the program telling you it can't find the properties that haven't been created yet. If you were to check off each of the role boxes, all of the properties would be set and written into the config data and those notices would disappear.
I realize I could write a script to add these properties to the config data of every existing block instance in the DB but I'm still struggling to find time to refine the capability itself. There is still some gray area I am working on such as the lack of roles for My Moodle pages. For most uses though, this version should be just fine for now.
PS. My solution to the problem was to turn off debug
dk