I'm not clear where your screen shot was taken. The blank thumbnail suggest that the thumbnail is either missing or not rendered due to error. What happens when you click to open the image in full screen to develop? If it opens properly then we need to look closer at the reasons the thumbnail does not display. If it does not open properly, then what are the error messages displayed?
Do we have any sort of fix at this point yet? Thank youClee,
This is a known problem (see the first messages in this thread), not simply a thumbnail that isn't rendered. If you look at the top of the slide mount, you'll see that the blank thumbnail also does not display a file name, or any other info that the other thumbnails do show. That indicates that this is a false database record.
Nothing happens when I attempt to open the image. Its as if there is no image actually there. No metadata etc. I have now about 60 of these that are intermixed through out my catalogue ...I'm not clear where your screen shot was taken. The blank thumbnail suggest that the thumbnail is either missing or not rendered due to error. What happens when you click to open the image in full screen to develop? If it opens properly then we need to look closer at the reasons the thumbnail does not display. If it does not open properly, then what are the error messages displayed?
Thank you Victoria. Here is one more thought. I've been trying to think what I have maybe done different recently and the two things are I switched from LR 6 to the subscription service and I upgraded from Luminar 2018 to Luminar 3 which has the DAM. I wonder if there is a commonality with the others who have experienced this.No fixes yet. For an odd one, I've deleted the orphaned data directly out of the database, but my database skills are too limited to be comfortable (or efficient!) at doing it for more than one or two. This one will need to wait on the engineers.
Hi Victoria, would you mind sharing your database deletion technique? I have 59 that are messed up in this way - I’m happy to backup my catalog and have a go at fixing it manually.I suspect it's a bug that was introduced about a year ago but takes really specific conditions to trigger it. I've suspected a glitch importing in the cases I've seen. Are these photos you've imported since moving to subscription?
Hey Victoria - I've hit this issue also, just this week. Do you have details of the thread you refer to, or to Rikk's tool? I'd like to be able to fix my catalog. Same issue as the others.If you follow the instructions at the end of that bug thread, Rikk's now got a tool to be able to fix it until they get the fix in a shipping build.
Thanks Victoria - is there anything I can or should be doing in the meantime to help it get resolved (e.g. provide my catalogue to someone)? It's a problem with pretty serious consequences, and they've known about it for a year, so I don't hold high expectations that Adobe will fix it anytime soon. :(I know it's on their radar to fix evil.elmo, so hopefully sooner than later.