-
-
Notifications
You must be signed in to change notification settings - Fork 181
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
Received messages in 1:1 chats are not logged in correct file #1214
Comments
You are right, there is a mistake. |
@janteau are you sure outgoing MUC PM messages are logged for you? For me they are not o_O |
If I'm not mistaken MUC PMs have not been logged at all if there was no other client sending carbons. This should add MUC PM logging functionality. We still need to make sure carbons log to the same file. Regards #1214
Add resourcepart to the outgoing carbon that is logged, so we use the correct filenames for MUC PMs. Dont log incoming carbons of MUC PMs as a workaround to faulty server behaviour. See https://wiki.xmpp.org/web/Multi-Session_Nicks#Private_Messages under 'Client-side workaround behavior'. Regards #1214
@janteau can you test with latest master? |
So MUC PMs seems where not logged at all. And I added a workaround about carbons of MUC PMs. See https://wiki.xmpp.org/web/Multi-Session_Nicks#Private_Messages under Outgoing carbons are now logged, incoming carbons ignored. |
@jubalh I don't think I've ever sent a MUC PM, so that's why I never noticed it not working. It's just not something that comes up in my use case. I talk directly to my contacts and then talk in a few MUCs; I believe a MUC PM is a different circumstance correct? I should have time this evening to try out the latest master. I'll see if I can do a MUC PM to test. |
Oh then I understood this whole issue the wrong way and implemented a new feature :) Yeah MUC PM is different. And now I implemented a workaround to treat them correctly haha. Okay but regular 1:1 logging should work. Also carbons should work. And MUC logging should work. And MUC PM should work. Just tested it and will close this issue now. Please comment still later if it works for you. Thanks! |
@jubalh I found my 1:1 received messages were getting logged into The master I pulled down this evening ( |
Expected Behavior
Messages received are logged when /chlog on and /omemo log on are enabled.
Current Behavior
Outgoing messages and message carbons sent by my JID are logged, but received messages from the other user are not logged.
This had been working, but seems not to be now. I have verified /chlog ON and /omemo log ON are set. I have tried quitting the application and restarting and the issue persists.
Steps to Reproduce (for bugs)
Environment
The text was updated successfully, but these errors were encountered: