Lightroom: Could not upgrade your catalog for plug-in metadata.

  • 3
  • Problem
  • Updated 5 years ago
  • (Edited)
I'm getting an error message:

title: Could not upgrade your catalog for plug-in metadata.
subtitle: The value must be a string.

When attempting to enable a plugin that uses custom metadata, after approving the catalog be upgraded.

PS - Catalog originated in Lr3 - converted to Lr4 format in the normal (supported) fashion. I tried an exported version of the catalog - same problem.

I NEED TO GET THIS PROBLEM RESOLVED, AND I DON'T HAVE A CLUE WHAT IS CAUSING IT.



Any help would be appreciated - thanks.

Rob
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes

Posted 6 years ago

  • 3
Photo of jdv

jdv, Champion

  • 728 Posts
  • 56 Reply Likes
Are you the author of the plug-in? Sounds like a bad metadata definition.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
Metadata module is fine. It worked in Lr3, and Lr4b. Something else is hosed now.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
Update: The symptoms no longer occur if the toolkit-id is changed - but then all the metadata values are lost...
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
Some plugin users are reporting problems with plugins that have custom metadata.

Memory use skyrockets and Lightroom and computer hang, when trying to update the catalog to support custom metadata.

I'm talking about right after installation, after answering the prompt about whether you want to have the catalog be updated or plugin disabled.

Problem is with Lr4.0.

Rob

This reply was created from a merged topic originally titled
Lightroom 4: Can not update catalog (plugin custom metadata).
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
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

This reply was created from a merged topic originally titled
Lightroom SDK: There is a serious problem in Lr4 updating catalogs for custom metadata..
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
Problem: Lightroom can not update catalog for plugin metadata. It tries, but consumes all available ram and the system hangs before it finishes. Something like this is displayed forever as it tries (no progression):


History: I wasn't having any problems, but a client was, so I tried bumping all the version numbers on my metadata items (from 1 to 2), then I started having a problem, updating the metadata - getting uncatchable errors:

Lightroom internal error: bad parameter #1 to assert - value expected (or something to that effect).

So I bumped the schemaVersion (from 1 to 2), and now I'm dead in the water - Lightroom prompts to update catalog, then tries, but can't finish.

I've been having this problem off and on since Lr4b. Everything goes without a hitch until it doesn't, then it's h-e-l-l getting it back on an even keel...

As I recall, previous workaround solution included changing the plugin's toolkit ID. But that's a *big* problem for some plugins, since it means a loss of all custom metadata. For some plugins, it's not too big of a deal, since the custom metadata can be recreated (although it does tend to aggravate the end users, and rightfully so), but on others, it's a BIG deal. - PRECIOUS METADATA IS LOST FOREVER!!! (or perhaps I should stay, is stuck in the catalog unavailable until the end of time)

Please look into this and fix...

UPDATE: I was able to solve the problem by putting all the metadata item version numbers back (to 1). Note: I left the schemaVersion at 2 (afraid to touch it again...).

Thanks,
Rob

This reply was created from a merged topic originally titled
Lightroom: Updating custom (plugin) metadata continues to be a problem....
Photo of Dorin Nicolaescu-Musteață

Dorin Nicolaescu-Musteață, Champion

  • 703 Posts
  • 38 Reply Likes
Rob, can you upload a small catalog that fails to update to custom metadata? I'll try to submit a report.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
Thanks Dorin, when it happens again I'll do it. For now, I need to make progress while the progressing is good...
Photo of Dorin Nicolaescu-Musteață

Dorin Nicolaescu-Musteață, Champion

  • 703 Posts
  • 38 Reply Likes
So, it's not easily reproducible?
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
I've never tried to get it to come back. So far, I've only been madly trying to get it to go away when it happens (and at the moment, I've succeeded). If I try to reproduce, or if/when it happens again, I'll report results here. Likewise, if you and/or Adobe attempts to reproduce, I'm interested in knowing whether you can or can't as well.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
Bug not fixed @Lr5.3.

Note: this error occurs *before* the updateFromEarlierSchemaVersion function is called, so there has not yet been any opportunity to alter/correct field values.

Reminder: bumping version number of metadata item does not help.

The only real solution I've been able to find is to change the plugin's toolkit ID, which is a real bummer, since it's not a backward compatible change - leaves your current users out in the cold...

I'm open to suggestions.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
I was able to correct this problem by hacking the catalog (deleting rows in AgPhotoPropertySpec), still...