Possible Workaround for that Nasty Lightroom Publish/Selection Bug

I have an update on the nasty publish/selection bug that been plaguing some Lightroom users of late, in the selection shown in the grid is sometimes wrong.

It seems that the bug exists only when Lightroom is started with a section in the Publish Segmented Grid (Modified Photos to Re-Publish, etc.) is closed. So, if you ensure that all segments are open, then restart Lightroom and maintain them open, your grid-selection experience should be bug free.

Example showing two sections, one open and one closed
clicking on the little triangle to the left of a section label toggles between opened and closed

The opened/closed state of each grid section is globally shared among all collections, so opening all four possible sections (New, Modified, Deleted, and Published) once takes care of it everywhere.

Bug or not, you can always trust the selection shown in the filmstrip, so until this workaround is confirmed for sure, it's best to keep the filmstrip open so that you can notice any divergence.

This seems to be a big breakthrough in understanding this bug, and I know that Adobe is aware of it (because they tipped me off to the workaround to begin with), so I have hope we'll see a fix sooner rather than later.

I really hope sooner, because being able to close a grid section is the only thing that makes the segmented grid useful in large collections. I wish the current grid header would be sticky to the top of the screen as you scroll so that you know what section you're in if the header doesn't happen to be visible. I have some collections with more than 100,000 items, making a visual search utterly impracticable. Even a relatively small collection of 2,000 photos makes for 300+ rows of thumbnails to scan; very unfun unless you get lucky.

I wonder whether it'd be better overall to just get rid of the Segmented Grid, instead adding a Publish Status item to the Grid Filter.....

All 2 comments so far, oldest first...

This just reinforces my premonition that there is some unclosed parentheses somewhere in some computer file in some server attached to something important that will one day blow up the world.

— comment by Zak on October 25th, 2013 at 10:27am JST (10 years, 2 months ago) comment permalink

Brilliant work! Your plug-in saves a ton of time. Many thanks.


Dundas, Ontario, Canada

— comment by Brian Colborne on October 27th, 2013 at 10:38am JST (10 years, 1 month ago) comment permalink
Leave a comment...

All comments are invisible to others until Jeffrey approves them.

Please mention what part of the world you're writing from, if you don't mind. It's always interesting to see where people are visiting from.

IMPORTANT:I'm mostly retired, so I don't check comments often anymore, sorry.

You can use basic HTML; be sure to close tags properly.

Subscribe without commenting