Mar 10 2009
A client sends their InDesign CS3 files to a printer, who makes any correx, then returns the corrected file to my client. When the client reopens the file, they receive an error message indicating that they are missing plug-in “XMPBackEnd5.pln.InDesignPlugin.” Usually, this is just a courtesy announcement; plug-ins for InDesign are supposed to be written so that their absence doesn’t mess things up for a recipient who doesn’t have the plug-in.
But in this case, it’s not so innocuous: the file opens, but my client cannot package it after they have worked on the file. The only solution is to run it through InDesign Interchange and open the INX file; this removes all desire for the missing plug-in. Then, the file behaves normally, and can be packaged successfully. Nice that there’s a workaround, but this is no way to live.
LATER NOTE: the XMPie uDirect plug-in seems to leave this residue only if personalization data is added to the file. If a clean file is simply opened, worked on and saved, there’s no problem down the line. The issues arise when personalization data is added, and then the file is passed on to someone who doesn’t have the uDirect plug-in. So it’s not universally dangerous.
I received this response from XMPie support: “Thank you for pointing us into this problem. I have sent this request to our Product Manager and I hope that this problem will be handled in future versions of XMPie.”
If you don’t know what XMPie is, it’s a powerful and nimble variable-data solution for InDesign. I’ve seen it in action, and it is very cool. But beware of this glitch until it’s fixed.