> Here's the PATCH traceback: It's broken upstream too - we don't have a test for PATCH of a patch with APIv1.1. I can't figure out why 2.2.5 would have exposed it but I don't pretend to understand the fine detail of the patch that went in between 2.2.4 and 2.2.5. I'll send a patch for this then look at the GET issue. Kind regards, Daniel