I was in touch with a developer for the plug in yesterday and found it was an issue with the plug in itself and is currently being looked into. 
Might have to go the specialized client route for the moment though.