I'm having the same problem. Using a component developed by me, as soon as i initialize my controller, the k2 content module throws that error. even if i don't initialize the controller.. I've found a workaround adding :...
More