Doublicated Albums are created

Backlight 4 & 5 Support
#1

Hi there,

using BL5, managed by Lightroom. Somehow I managed to have a album created duplicated :frowning:

I was playing around creating a new AlbumSet. The naming was not to my liking, so I changed and did changes back and forth.

Actually I have 2 AlbumSets and deleted the one where I played around. Sadly now the strange behavior is now also with the old two AlbumSets :frowning:

So, questions how do I get rid of Albums being created twice whenever I create only on in Lightroom

Cheers
Elmar

#2

This seems to happen occasionally. One album will have the correct slug but there will be no images in it. The other will have the same slug with “-1” appended to it, and it will contain the images.

If I remember correctly, Lightroom will show only the album with the “-1” appended.

You should be able to delete the empty album using Backlight Publisher.

After deleting it, you should be able to change the slug in Lightroom Publisher.

#3

Hello Rod,

I’m not not quite sure if I understand you correctly. You mean to just delete the Album that does not Contain any picture via the webfrontend, right?
For sure I can do this but this is pain in the *** to be honest.

In my workflow I am creating hundreds of new Albums and if I always have to delete the duplicated one this would slow me down tremendously.

Or did I missunderstand you?

For clarification… I have one AlbumeSet where I created a bunch of Albums in it. Every time I create now an album I get a duplicated one. I think there is something wrong in the publisher or in der DB?

#4

Yes, using Backlight Publisher.

But that’s only practical if duplication happens only occasionally, which is my experience.

If this is happening in only one album set, I’d first try deleting that set and starting over. But if you already have lots of albums in that set, then that too would be a pain.

my guess is that there may be a database problem and @Ben will need to take a look.

#5

Yes, this is of my assumption.
Sadly now All Albumset have This Behavior.

#6

on the chance that Lightroom is creating the duplicate albums, you can try resetting the Lightroom Preferences file. That can often fix Lightroom oddities.

How do I reset Lightroom's Preferences? | The Lightroom Queen

#7

It may be that your server is redirecting your requests, causing duplicate requests from the Publisher. Can you check that your API URL set in you Lr Publisher starts with https and includes the exact URL that your site uses? One way of verifying this is to paste that URL into the browser and seeing if it is redirected to another URL. If that happens then use that final URL in your Publisher settings.

#8

There is no redirection. Checked it.

#9

Sounds good. How do I do this?

#10

Thanks for checking. I’m not sure what’s going on. The log files created in Lightroom show the details of requests and responses from between the Publisher plugin and your server, so will hopefully shed some light on it.

Can you email me the TTG log file for Lightroom? It’s called ttg.log and should reside under a directory called LrClassicLogs in your Documents directory. On my Mac it’s under /Users/ben/Documents/LrClassicLogs/ttg.log. It should be in an equivalent location on Windows PCs.

The file is likely to be very large, so can you zip it before sending? Alternatively, if you rename that file to something like ttg.log.old and then replicate the issue again from Lightroom then there should be a fresh and much smaller ttg.log that just captures that interaction with the server.

I’ve sent you a Message here with my email address. You should be able to see it by clicking on your profile picture followed by the mail icon.

It would also be helpful if you could provide me with a Backlight admin login so that I can see what’s happening in the database. The best way to do that is by replying to my direct message, or by clicking on my name followed by ‘Message’.

#11

Thank you very much. Will create and send it… give me some sec :slight_smile:

#12

sent :slight_smile:

#13

Hi @elmex04, thanks for the log file. This is quite a mystery. What looks to be happening is this:

  1. Publisher creates the album on the server. Publisher is then meant to register the returned id from the server.
  2. Publisher then tries to publish the photos. It can not find that registered id, so attempts again to create the album.

What I need to work out is why step 2. can’t see the id. One theory is that the publishing step is happening too quickly after creating the album (though this shouldn’t be a problem, it may be what’s causing it).

In your tests, had you clicked ‘Publish’ within seconds of clicking ‘Create’? If so, can you try another test where you create an album and wait a minute before publishing only photos?

Can you try one more thing:

Visit File > Plug-in Extras > Output Publisher Structure in LR. Then select the name of the Publisher instance you’re currently using followed by clicking ‘OK’. This will list the album structure that LR has for the instance. If you’re able to see a complete structure complete with ‘OK’ button like below, then select the structure and copy-and-paste it into an email.
If there is too much content there, then can you please re-send the updated ttg.log file (viewing the structure with the steps above also logs it to that file).

#14

[[{“id”:"",“parent”:"",“slug”:"",“type”:“album”},{“id”:"",“parent”:"",“slug”:"",“type”:“album”},{“id”:"",“parent”:"",“slug”:"",“type”:“album”}]]

This is all I can see right now, as I deleted all AlbumSets in hope this would somehow solve the problem but this is not the case sadly.

Will give the raceconditikns a try, waiting a minute after uploading pictures.

#15

So to have things clearly… I protocol my steps and resend you the log file :slight_smile:

  1. Delete all AlbumSets in Publisher
  2. OK - when refreshing Publisher-side there is no AlbumSet what’s or ever, so we are “clean” now.
  3. create a new publisher connection in lr called FOTOS
  4. I can now see a new publishing link in LR called FOTOS
  5. There is already a Default Album
  6. Checking result in Publisher in BL. There is not yet a Album created
  7. Created Album within FOTOS called “test1”
  8. Publishing the newly created Album “test1”. No I can see the AlbumSet FOTOS as well as the Album “test1” in BL
    Album not created double. I can only see one single Album called “test1”
  9. Waiting…
  10. Hardly 2 Minutes later I add a photo to the Album
  11. I choose publish the album.
  12. Image was transferred
  13. Now I see 2 Albums called “test1”. One with the photo and one without the photo.

So, does not seems like a race condition problem to me. Any further ides?

Logfile is being sent to you by mail

#16

Hi @elmex04, I’m keen to see what the structure looks like A) after creating an album but before publishing, and then B) after publishing (when the duplicate album is then there).

#17

So here is the Structure before adding photos (Step 1 to 7):

Output completed for for FOTOS
[[{“id”:"",“parent”:"",“slug”:"",“type”:“album”},
{“id”:"",“parent”:"",“slug”:"",“type”:“album”}]]

#18

So now I added a photo to the album and published it.
The album is now doubled once again and here the structure you asked me for:

Output completed for for FOTOS
[[{“id”:"",“parent”:"",“slug”:"",“type”:“album”},
{“id”:"",“parent”:"",“slug”:"",“type”:“album”}]]

#19

Can you try adding and publishing more photos to the album? Does that create a third album?

#20

What’s the exact version of LR you are running? I am wondering whether there’s some compatibility issue with Backlight returning the id as an integer and LR expecting a string.