Hi Adam, without any further action, the error disappeared and the plugin went back to working normally. Quite inexplicable, but better that way..!
Thanks anyway!
Problem is apparently related to WP 3.5 (I’ve read a lot of problems with this update).
I downgraded to WP 3.4.2 and everything was again perfect.