Community @ The Turning Gate

Hi Ben

Was just wondering whether another approach might be feasible. At the moment, for a non-protected album within a protected album set, when you access the url for the album it prompts to login to the album set. In some cases that is exactly what is required. But in others it might not be.

I think I could achieve what I wanted if direct access to the album did not attempt to login to the enclosing album set. In that way people could go straight to the album which would be effectively hidden. But someone with the username/password for the album set could see all the otherwise hidden ones.

It seems to me that this would be possible, as it is merely adding an album option to bypass the existing check of enclosing album sets.

Am I on a plausible track, and if so would you consider it as a feature request?

Regards
Chris

Hi Ben

I've started doing some investigation. Results so far:

• Installed a new backend with default settings - no difference.

• Installed the publisher plugin in LR on another workstation also on Win7-64, pointing at new backend. It worked.

• Re-installed and re-loaded Publisher plugin on original workstation - no difference. Nor does restarting LR or rebooting help.

• Deleted LR from original workstation, including Lightroom Settings. Reinstalled and restored settings saved from before experimenting with LUA. Created galleries in new backend with LUA. It worked.

• Tried to republish galleries in the old backend (the publisher settings for this hadn't been cleared down when I re-installed). Failed. And now I can't even publish galleries using LUA to the new backend either.

• Re-installed LR again, this time without clearing down the preferences. No difference.

• Re-installed again, and cleared down prefs. Can again publish to new backend. Tried publishing the same couple of photos repeatedly to new galleries, same template. On the third time it failed, and now can't publish anything with LUA again. I don't think I went near the original backend publisher instance but can't be sure.

• On the second workstation tried repeatedly publishing. 8 times worked ok. Now it's late at night.

It also makes no difference whether I am republishing the photos or just the metadata.

I'll keep at it but there does seem to be a certain random element involved. Wondering if it is some sort of timing window?? Workstation with the trouble is a pretty high spec, the second one is a modest laptop.

Alternatively there is some corruption in publisher info for the original instance, or something that is causing corruption. I'm on the point of blowing away absolutely everything to do with LR and Publisher on the original workstation, and starting again. On the bright side, the LUA script I had written worked first time....

Any ideas, or info from anyone else, would be greatly appreciated.

Thanks
Chris

What does the "Update Album Files" link in the Publisher Admin (referred to above) actually do? Can't find any description of it. It's a bit like having a "Don't press this button" button

Ah well never mind.

I did have one idea that I tried without success, but not sure why it didn't work. I created an album set (c) containing an album (cc). The AutoIndex template for c hid the entries for the contained cc. I could still go to cc directly with a URL. So far so good. I then created a password-protected album set (m) with a "normal" autoindex template, and within its directory structure created a symlink to c/cc. It was an attempt to fool it into thinking cc also existed under m. Not sure why but it didn't make any difference. I have FollowSymLinks on.

Is there any chance this sort of approach could work, or should I give up? No big deal if it won't work...

Thanks
Chris

All good with 604b mobile/touch. Thanks for sorting it.

Regards, Chris

Found the problem - although it is a weird one to have on Windows. 604 has galleryInfo.lrweb; 604a has galleryinfo.lrweb - note the capitalisation of the "i". Rename it to the correct capitalisation and it shows up in LR. Haven't tested it yet...

For now have switched to the Magnific Popup for mobile devices, as it is fine there.

Hi Ben. Sorry for the noise on this one. It was my fault. (Too embarrassed to post why...)
Thanks, Chris