nextcloud
Notifications don't trigger for actions initiated by yourself
I have set up a simple test case:
The NC Talk flow is just there to verify that I didn't misconfigure the conditions. When I edit/rename a file called test.md to test1.md (or vice versa), I get a message in Talk but no notification.
NC version: 20.0.4 Flow Notifications version: 1.0.3
Cannot confirm on 20.0.8 / 1.0.3.
Please note that the notification is not triggered, when you do the action yourself.
Cannot confirm on 20.0.8 / 1.0.3.
Please note that the notification is not triggered, when you do the action yourself.
Sorry, my mistake in testing after the update
@blizzz Oh, so this is intended behavior? IMO, this could be configurable. I don't always access files manually, but also in various automated tasks via scripts, which might be a use case for this flow.
Anyways, I'll test the app with another user and report back in a minute.
@blizzz Oh, so this is intended behavior? IMO, this could be configurable. I don't always access files manually, but also in various automated tasks via scripts, which might be a use case for this flow.
Anyways, I'll test the app with another user and report back in a minute.
Yes, it is intended and also worked like this. Does not mean it has to be like this forever (but then opt-in).
Cannot confirm on 20.0.8 / 1.0.3.
Please note that the notification is not triggered, when you do the action yourself.
Sorry, this was my fault! Is it possible that notifications are also not created if the files are in group folders? If yes: Is there a workaround to make that happen?
Is it possible that notifications are also not created if the files are in group folders?
This should not be the case. There is no introspection into files. The check for ownership as pointed out above is the only one we do in this app.