Options
Uploading in Smugmug via LR changes keywords!
Georgespyros
Registered Users Posts: 71 Big grins
As i say in Title.
Keyword is for example, 21000, when it comes in LR, it becomes 210002C (it adds 2C in the end of it).
I tried doing it in other export functions, its ok.
It only happens when it has to do with with SMUGMUG & LR plugin.
Here Are my Settings. Please help because this is so frustating, and keywords are ultimately necessary for me.
Here are my settings
And here are 1 example of photo with changed keyword (see the LR keyword field, and then the smugmug keyword field).
As i said, in any other export operation, all seems ok!
Keyword is for example, 21000, when it comes in LR, it becomes 210002C (it adds 2C in the end of it).
I tried doing it in other export functions, its ok.
It only happens when it has to do with with SMUGMUG & LR plugin.
Here Are my Settings. Please help because this is so frustating, and keywords are ultimately necessary for me.
Here are my settings
And here are 1 example of photo with changed keyword (see the LR keyword field, and then the smugmug keyword field).
As i said, in any other export operation, all seems ok!
0
Comments
You hid the URL so I can't look, but can you see which keyword works in search on Smugmug? I.e. is it REALLY 00002C, or is it really 0000, or is it "0000," despite what shows?
I'd also look at the Keyword list in Smugmug, check the options on that keyword. I see one listed as 0;20900 which looks a bit suspicious as well.
Oh... I created a 12345 keyword and (re)published and it worked fine for me, the combination of the hext and that makes me suspect some setting or keyword setup, maybe something that came into lightroom in an import, something like that?
-- Sara
In the meantime i worked around that issue, by uploading manually my photos via an internet browser.
This works fine.
The issue i mentioned sometimes goes away if i mark to republish, sometimes not. It seems almost random!
The files have their keywords imported by a CSV file. CSV files, do have a comma at the end. Maybe this comma is in the keyword, but doesnt show in LR. But it tries to publish it?
I will look at it again and come back.
Thanx for your help
I had an issue with this before, as I scraped keywords from a web page and found that the spaces were a hex A0, which appeared nicely as a space on the screen, but internally was a weird character that exploded into unicode when it made it into the actual keyword.
Cleaning out the commas and anything not simple traditional ascii alpha/numbers may be a good start. I never found the culprit in changing mine (the importing program or the export), but making it a nice hex 20 instead solved it all.
New update is out. Im going to try this out!
It seems it addreses this exact issue.
Thanx Smugmug