-
-
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
Tagging not working stable on cloud.nextcloud.com #10774
Comments
GitMate.io thinks possibly related issues are #7801 (Nextcloud Talk APP NOT Working), #5391 (2fa TOTP stopped working on Nextcloud 12), #8310 (Disable web app by own cloud interface (NO NEXTCLOUD THEME)), #8348 (Server error response (nextcloud.com down)), and #8767 (After the update the nextcloud server is not longer working). |
@mathiasconradt I sadly can't reproduce, but will retry. Could you open the web developer console (Ctrl + F12) in your browser and then reload the page. If it doesn't work it maybe show something in the "Console" tab. That would be useful. |
@juliushaertl @skjnldsv @blizzz for the JS part of tags |
@MorrisJobke Enabled dev console, even "disable cache" is activated. Still able to reproduce the error. I can show it to you via NC Talk Screenshare if you or others want, just ping me. Tested with FF and Chrome latest versions, on Ubuntu/Gnome. |
@mathiasconradt cannot reproduce it either. What does the POST request to https://cloud.nextcloud.com/remote.php/dav/systemtags/ result in? |
There is no POST request in the devl tools, only a PROPFIND The response of the first PROPFIND returns proper values:
PROPFINDs on the documents itself: PROPFIND https://cloud.nextcloud.com/remote.php/dav/systemtags-relations/files/755194 Reponse:
I get the 404 in both cases: where the tag on a document works and where it doesn't. |
A POST should be fired when a tag was set, that's what happening for me. Do you own that file or is it a shared one? |
I'm not setting a tag (yet), I just click on "tag" word in order to open the tag input field. And that already does not always work, even before I submit any tag. |
OK, tried it again, clicking on Tags to get into the text input works for the first file (more precise: for the first file of which I open the sidebar) after a page load, but not any other, and also not when returning to the first file. Seems the click action is assigned once, but not any further. |
It's a backbone view and it seems that the click-event-binding get's lost. |
@mathiasconradt Is it this behavior: https://cloud.morrisjobke.de/s/B5CJKcNHbWKAyQa ? |
@MorrisJobke nope, the tag list does not even open for him on the second file |
fix in #10782 |
Hi, any updates on solution to this problem? |
Fix was reverted as it broke the sharing entries -> reopen |
I can confirm the problem still exists in 14.0.2 |
Confirming this still existing in 14.0.3 |
We encounter the same problem, appearing on two different NC instances (both NC 14.0.3, one updated since NC 12.x, the other started with NC 14), we tested with
|
Any idea how to fix it? |
#12231 I think this is related and might fix it. Can't test it right now though. |
Bug present on 14.0.3 production too. |
How could it be released with a bug of something that was working earlier? |
@SNAKE83 Evolve code without have any bug is a difficult art. (especially with framework/library, engines and hardware who evolve too) |
Most likely fixed by #12577. The backport will come to 14.0.5. |
Working in 15.0.0 |
Please Re-Open for 18.0.4 (just updated from 18.0.3). |
This is one and a half-year old. Please open a new issue with full details. |
Tagging files does not always work on cloud.nextcloud.com, current version as of 21.08.2018
Expected behaviour:
Tags show including the input field to add more tags
Actual behaviour:
Nothing happens upon click, not even any JS error in the dev console.
This only happen sometimes, sometimes it works.
How to reproduce it:
Reload the browser page with Nextcloud file explorer in a folder that contains multiple files.
Open document details of one file, click on "Tags": the tag input box appears.
Now open the document details of another file (without reloading the browser!), click on "Tags": the tag input box does not appear.
The text was updated successfully, but these errors were encountered: