Collaborative proofing not showing link

[defaultebm7s1z3kewb]

Anyone have an idea why I don't get a link once I "enable collaborative proofing"?  I have it enabled, but no link shows up at all.

[Jim Wilde]

Can you explain what you are doing to enable proofing? There are basically three steps, using the LrWeb interface:

1. Enable collaborative proofing in the "Technology Preview" section which you access via the settings when you click on your avatar.

2. Then select the album you want to share, and at the bottom you should see 4 icons (possibly 5, as the sort direction icon may also be showing). Click of the 4th icon from the left to start setting up proofing (hover over the icon to see that you have the correct icon), see screenshot below.

3. That will then point you to the sharing icon (top right of the page, see second screenshot), clicking on that starts the proofing procedure which includes setting up the sharing link.

Are you doing that? If so, where does it fail?

[defaultebm7s1z3kewb]

Yes, once on step 3 as you outlined, I click on "enable proofing" in the popup window. After enabling, I can set the number of selections, however there is no link. The word "link" is there but with no url present

[defaultebm7s1z3kewb]

Okay, it appears this might be a firefox issue only.  I tried on my phone with chrome and I see the link now.

[Jim Wilde]

What system are you using? I've tried it using Firefox on my Win10 system, with no issue.

[defaultebm7s1z3kewb]

Using Windows 11 Home with the latest version of Firefox.  The first image below is what I see on Firefox (my default browser), but the second screenshot is from Chrome on the same computer:

[Jim Wilde]

That's odd.....earlier this evening a poster at the lightroomqueen.com forum had a similar (but not identical) issue using LrWeb, in their case the issue was with Microsoft Edge on Windows 10. Their issue was with normal sharing, but on the sharing page the box that contains the actual URL was missing, just as in your case. Coincidence? In this case the problem was resolved by resetting the Edge browser back to default settings, perhaps that would be worth a try with your Firefox installation?