Had another clash, where I added another Playa field:  There’s already Playa fields within the form, 2 within a tab, 1 in a Matrix field and another in the main block.  I added another, and the markup went completely wonky, with the save not working.

The markup for publish form should look like this (when custom tabs works):

When it goes wrong, the markup looks like this:

Hence why the save doesn’t work as the main publish markup has fallen outside of the form.

Any ideas?

[Edit]
Error console in Firefox shows this:
Error: uncaught exception: [Exception… “Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIDOMHTMLFormElement.removeChild]”  nsresult: “0x80004003 (NS_ERROR_INVALID_POINTER)”  location: “JS frame :: http://Domain.co.uk/ee-admin/index.php?S=7379619228e5564dba3ae3c1548841658a5cdcd0&C=edit&M=edit_entry&weblog_id=2&entry_id=10 :: anonymous :: line 3626”  data: no]

Not that it helps much!?!

[Edit 2]
This is using the latest download onyour site (v0.7.2), but the extension has the version 0.7.1 and the comment references 0.7.0.

It seems to be the Matrix field that it’s struggling with (even though it was working fine with it before).

Whereas there’s normally 2 divs for each row in the publish page (one open, one closed), the markup output by your extension breaks when trying to modify the closed div, notice the id field gets markup inserted into it instead of the name:

This should read: