Lightroom SDK: There is a serious problem in Lr4 updating catalogs for custom metadata.

  • 3
  • Problem
  • Updated 7 years ago
Merged

This conversation has been merged. Please reference the main conversation: Lightroom: Could not upgrade your catalog for plug-in metadata.

I have had numerous complaints from clients updating to Lr4 who simply can not use plugins with custom metadata in Lr4 because they won't make it through the update.

I had this problem myself, and got through it simply by removing custom metadata definitions and then adding them back, exactly as they were, one at a time, reloading the plugin and approving catalog update after each. I obviously can not expect my clients to do the same.

PLEASE fix this before releasing Lr4.1 final!!!

Note: There's nothing wrong with the metadata definitions (I'm not sure if there would be a problem when installing a version of the plugin that has the exact same metadata definitions as last time, but certainly if the new definitions have had a few extra fields defined there can be trouble), there is something wrong with Lr4 - all dot versions so far, and beta.

This problem occurs on both Windows and Mac.

2 plugins that have drawn a lot of complaint are:
- DevMeta (installing new version with additional fields for PV2012 when they previously had version installed that did not have the additional fields)
- CustomMetadata (e.g. when trying to add additional custom fields).

Thanks,
Rob
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 386 Reply Likes

Posted 7 years ago

  • 3
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 386 Reply Likes
This problem remains unfixed @Lr4.1 final.

Only work-around I've found is to change LrToolkitIdentifier.

Note: If user does not uninstall previous instance before installing new one, the metadata can be auto-migrated, if need be.

If user has already uninstalled previous instance before installing new one, the previous metadata will be orphaned in the catalog, and not be transferable.

Rob