-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
File tags showing as the tag id not tag name #46695
Comments
Observing the same. Looks like the tag ids are listed instead of the tag names. When I click on one of the folders I actually do see a tagged folder. If I click on that it tries to open the folder id in the tags url ( Bildschirmaufzeichnung.vom.23.07.2024.12.28.07.webm |
Hi, Imho this was working ok in 29.0.2 and seems a regression of the update. |
I can confirm this issue on NC 29.0.4 This problem seems to be self-made as it is close to these bugs: I would assume that you guys do not test your own software before release it. |
hello @susnux , |
This issue also came up in the Support channel. |
Thank to you @susnux @skjnldsv @joshtrichards ;-) |
are any workarounds to fix the display of tags immediately? |
No, you will have to wait for 29.0.5 |
What about the backport to v28? |
28.0.9 :) |
Bug description
When I enable collaborative tags app I observe strange behaviour clicking on the tags section:
Steps to reproduce
Expected behavior
As far as I understand here I have to see the list of tags or something else?
Installation method
Community Web installer on a VPS or web space
Nextcloud Server version
28
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.2
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: