-
Notifications
You must be signed in to change notification settings - Fork 5
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
Private Group Messages Become Direct Messages #12
Comments
@ylluminarious I have a local revision with that change reversed and it works really well. |
I'm seeing this as well with master (d887295), any tips on how to get around it? Thinking it might be because the intended room already existed I tried to import into a different (non-existent) room, but where those messages went I have no earthly idea, the import went through without problem, but no channel/room was created and the messages seems to have gone into cyberspace... |
Cleaned everything out and went with an updated master of mattermost-docker (mattermost/mattermost-docker@cb6690b), but still I get all messages sent to the imported room ends up as private messages from me to me... |
It seems to be related to the room/channel type "P", if I try to import a room/channel of type "O" it does what I expect - creates a public room of the data... |
I have messages in restricted rooms that are converted into direct messages to the user themselves.
The original room was:
The message was:
And this then becomes a private message. I really don't understand why, but clearly thought has gone into this.
I am reversing this for myself to try but I am interested in your feedback @ylluminarious
The text was updated successfully, but these errors were encountered: