-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v114.0 - All tags has become just one long string (tag) #12516
Comments
Fixed in #12509 |
Does not work in v1.115 🙁 Now I'm on v1.115.0 and the tags are still a single long strin. Did I miss something? |
I think that is a separate issue. This fixed something related to HierarchalSubjects. Can you open another request and upload the file that isn't working (as a zip)? |
No, this issue is for multiple tags (spearated by ,) not Hierarchal tags (separated by >). But the FIX #12509 only describes Hierarchal, so maybe this is the error? Also #12542 seems like multiple tags, not Hierarchal. But while looking for an image for example, I recognize that my images are now all OK, but the old long tags are still there 🙁 |
Sounds like your issue was fixed then. Correcting old, empty tags is being worked on in #12654. |
The bug
First, thanks for adding tags (metadata) into v1.113.
And it was a rather good implementation, too
All my IPTC keywords that I had added to the pictures (from external folders) in Lightroom were parsed in a separate tags.
This is what it should look like, and it's taken from a picture that lies in an external folder
But then I uploaded pictures from my Android phone, and I discovered that those pictures had not many tags, but all tags in one long.. tag (string?)
This is the tags from the same picture when uploaded from my phone:
It seems to have similar problems when uploading from my PC as well.
Anyone else experienced this?
Thanks
The OS that Immich Server is running on
Unraid docker
Version of Immich Server
v1.114
Version of Immich Mobile App
v.114
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
Relevant log output
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: