I’m using Lightroom Classic CC 8.0. I have a library with 75,427 photos in it, which are a combination of .NEF, .ARW, other files (.TIF, .jpg,.png, etc), and now .DNG.
I selected every file in the library, told it to convert them all to DNG (and delete the original when done and all that jazz).
However, it seems to skip a lot of the photos.
The progress bar is almost done with its 24-hour processing of this task, and when I look in the masters directory I see 26,832 DNG files and 31,692 NEF files. BS it’s almost done.
I’ve done this on smaller scales too: I’ll select one directory, tell it to convert them to DNG, and it’ll convert half of them. If I do it again on the same directory, I’ll get more. After a couple passes it’ll finally convert them all.
Why doesn’t it actually convert them all and how do I get it to do it the first time?
I’m trying to convert a core entity (menu_link_content) to revisionable with existing data. I’m trying to figure out how to accomplish this. I saw this go to guide here – https://www.drupal.org/docs/8/api/entity-api/converting-a-content-entity-type-to-be-revisionable-and-publishable
I have a D8.6 site and I’m trying to make the menu_link_content revisionable. On top of that my site has existing content for custom menus. And I cannot just delete these contents. So these has to be ideally migrated to the new revision tables thats created. When I followed the step by step approach in that guide ‘Section 2’ I get the exception –
“Drupal\Core\Entity\EntityStorageException: The SQL storage cannot change the schema for an existing entity type (menu_link_content) with data. in Drupal\Core\Entity\Sql\SqlContentEntityStorageSchema->onEntityTypeUpdate() (line 347 of /var/www/myproj/docroot/core/lib/Drupal/Core/Entity/Sql/SqlContentEntityStorageSchema.php).”
When I delete all the custom menu links content it works.
Please confirm if my understanding is correct in the Section 2 –
“If you are updating the code for an existing site and your entity type already contains some data, you will also need to provide an upgrade path in addition to the changes explained in part 1. The upgrade path is composed of two things “
- This means before performing the section 2 steps we have to make sure the Section 1 is done. This includes changing the Entity file annotations and setting fields to revisionable etc.
After this step I added the new revision fields like logs, created, time etc to install file and then created a post_update file and specified the fields which revision is set to true in that array.
Any suggestions or examples are welcome. Thanks!