I have seen several posts and blogs reference the error message that designers sometime get when they open up a document stating that?XMPBackEnd5.pln.InDesignPlugin?is missing.

This is caused when the XMPie uDirect or uCreate plug-in has been installed on the creator’s system and a document created and sent to another. Even if the XMPie plug-in is not used to personalise a document this issue can be created.

I recently asked Gal, from tthe R&D team about this and this is what he said

The problem that is experienced is a result of XMPie adding properties to certain components of the document. For example: A spread gets the property of whether it has a visibility ADOR or not. A box gets the property of whether it has text length handling (auto flow, copy fitting) and if so In what way.

The way this is implemented is by using the only technology available for this by Adobe which as a by-product forces that the properties are added to the document whether you actually place valid values or not (meaning whether you set them or not). If they are not set to specific values they simply get null values but still the properties are there. Since the properties are there taking the document and opening it in another InDesign installation provides a warning that there is no support for these properties i.e. the missing plug-in warning.

So, the answer here is not straight forward, and XMPie is talking to Adobe about this matter it would seem. Gal goes on to mention that they have seen this issue replicated in several other Adobe Plug-ins that make changes to the document in the same way; so it would seem that this is not solely an XMPie issue.

The best way to overcome this?

  • You could always install the XMPie plug-in I guess; free-of-charge and fully functional from www.xmpie.com.
  • If you are the creator of the document then disabling or removing the XMPie Plug-in; before resaving the document should work.
  • Exporting the document to an INX or IDML file will also do it’s best to remove any conflicting tags.
Full disclosure: At the time of writing this article the author was employed by XMPie, a Xerox Company.