-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
18.0.1: user mention in comment field is not working #19523
Comments
Same here, yesterday I've updated 4 of our 17.0.3 Instances to 18.0.1 and When user inputs a correct username all is working as expected, when user inputs a wrong name, the comment is accepted but is prefixed with Unknown User |
Still not working with 18.03. any progress on this issue ? |
Hi Team we are seeing this issue specifically for us the issue is seen when commenting on a file using hte "files" app. when mentioning a user in "Deck" and "calendar" comment section its working as expected. NextCloud version 18.04 Hope the above helps. Please let us know if we can assist with further troubleshooting? ""Cheers |
Also/still broken in 19.0.0. Note that if you know the user name and type @(username) and send the comment it will work. It is 'just' the popup that doesn't work. Server configurationcloud.nextcloud.com PHP version: Nextcloud version: (see Nextcloud admin page) Browser logNo errors that I can see, just deprecation warnings.
@blizzz you might be able to have a look... |
This comment has been minimized.
This comment has been minimized.
I confirm for nextcloud 20 (docker image nextcloud:20-apache). No error or warning in the log file. In the browser console, when I open the details info, I have a list of errors like : |
Is solved with NC21 |
First I thougt its solved with NC21. Selction works but we have users with special chars as "@" in their usernames. When I select one of those users the "@" inside the username is removed and so the user mention does not work |
Steps to reproduce
Expected behaviour
popup should show all the corresponding @usernames
Actual behaviour
Nothing happend, no popup
The text was updated successfully, but these errors were encountered: