Nope, not a clash with another plugin. This is an error in the way a certain WordPress function is being used by Connections. I thought I had hunted down all those a year ago. There was a change in WordPress 3.5 so the error would show … or something like that. A lot of plugins had to update to use this function correctly.