We got the following trace. We shouldn't completely fail and let the package import keep going. Instead, we should complain loudly (that's indeed a clue that we don't support something, and that something might be critical... or not). We also need to know the object type that's failing so we can further improve the code and handle this type, so let's add the information to the error message. We will also print the id of the related object so we can ask crafty user extracts of their entitites.xml fails if they don't want to send the whole thing for privacy reasons.
|