Hey Hey Hey !
I would like to know how to open a specific mattermost channel in the desktop app via url. I know the command “mattermost:” but it’s just open the main channel in the desktop app.
Thanks for your help
↧
Open mattermost desktop app via url
↧
[solved] Mobile App(Android) TLS handshake error
Hi @AndreyChe,
Have you had a chance to take a look at this troubleshooting doc: https://docs.mattermost.com/mobile/mobile-troubleshoot.html#i-keep-getting-a-message-cannot-connect-to-the-server-please-check-your-server-url-and-internet-connection?
↧
↧
[solved] Mobile App(Android) TLS handshake error
Thank you, now it works. I had to put full chain in certificate file.
↧
Announce: deb & rpm packages for Mattermost
That was never the intention. And of course you could still use your config mgmt system of choice on top of our packages.
↧
[SOLVED] Slack-to-Mattermost Conduit?
We work with a lot of folks who use Slack. We don’t like Slack, but we’d still like to interoperate with them from within Mattermost by sending and receiving direct and room/channel messages, etc.
Is there currently any way to do this? If not, what would it take to implement this on a technical level?
↧
↧
[SOLVED] Slack-to-Mattermost Conduit?
Hi @ylluminate,
What currently is available is called Matterbridge: https://github.com/42wim/matterbridge.
Is this what you were looking for?
↧
[SOLVED] Slack-to-Mattermost Conduit?
Thanks @amy.blais, I think this will work! I wish there was a little better usecase explanation. A new article there is useful, but I guess I’m going to have to actually set it up to see how it works out. Thanks for sharing that - I’d forgotten about MatterBridge and never even realized it could work with Slack.
↧
Chain notifications issue
hello all,
server: 5.9.0
client: ios 1.17.0
we are facing a new issue with notifications since last release.
notifications used to pop for every message received. now when multiple messages, from the same source, are received. it seems only the last one is poping in the notification area. so users know there are messages waiting but only the last one is actually been displayed in the notification panel.
Cheers
↧
Messages stuck on send
Hi all,
server: 5.9.0
client: ios 1.17.0
We’ve got a new issue when sending messages.
At some scenario, the user tries to send a message but it stays greyed out. afterwards he tries to send another message but the new message also stays greyed out. This using wifi connection.
“no internet connection” bar doesn’t show up and the device seems to have normal connection.
After a while the red exclamation icon appears on the right side of the message but the retry nor delete seems to work.
The only way to fix it is to force restart the app. The greyed out messages disappear and new messages tend to work ok.
Cheers.
↧
↧
Client Stuck on Startup
↧
Announce: deb & rpm packages for Mattermost
.deb packages are nice but manually going to a website and downloading a new .deb and then installing it every time there is an update is not something most (lazy) people are likely to do.
Perhaps putting some effort into an official SNAP package is worth serious consideration. There is already an unofficial one out there that is quite good. You could always look at the SNAP package S L A C K has for the harder to figure out configuration parts.
Just my 2c.
Thanks for the .deb package!
Scott
↧
Server Started, unable to connect
Hi Guys,
I am hoping someone can help me with figuring what is broken or what i messed up in setting up the MatterMost server.
I’ve tried to setup the server following the install guide here.
https://docs.mattermost.com/install/install-rhel-7.html#install-and-configure-the-components-in-the-following-order-note-that-you-need-only-one-database-either-mysql-or-postgresql
with MySQL and running on Centos 7.
by the looks of things the service does start however not fully as i am unable to browes to it remotely and curl locally give and error.
The error is similar to the case here. [SOLVED] Server started but app not connecting and no logs
Unfortunetly my knowldge is now where near deap enough so i was not able to enable the loging or the DB loging.
Log
[root@QCSDEVPOLAPP01 mattermost]# tail -n20 /opt/mattermost/logs/mattermost.log
{"level":"info","ts":1554700311.1365652,"caller":"jobs/schedulers.go:140","msg":"Stopping schedulers."}
{"level":"info","ts":1554700311.1365798,"caller":"jobs/schedulers.go:75","msg":"Schedulers stopped."}
{"level":"info","ts":1554700311.1365917,"caller":"app/server.go:336","msg":"Server stopped"}
{"level":"info","ts":1554701009.7608232,"caller":"utils/i18n.go:83","msg":"Loaded system translations for 'en' from '/opt/mattermost/i18n/en.json'"}
{"level":"info","ts":1554701009.7610474,"caller":"app/server_app_adapters.go:58","msg":"Server is initializing..."}
{"level":"info","ts":1554701009.7686296,"caller":"sqlstore/supplier.go:215","msg":"Pinging SQL master database"}
{"level":"error","ts":1554701010.0195894,"caller":"app/server_app_adapters.go:119","msg":"SiteURL must be set. Some features will operate incorrectly if the SiteURL is not set. See documentation for details: http://about.mattermost.com/default-site-url"}
{"level":"info","ts":1554701010.0202277,"caller":"filesstore/localstore.go:33","msg":"Able to write files to local storage."}
{"level":"info","ts":1554701010.0222783,"caller":"app/plugin.go:130","msg":"Starting up plugins"}
{"level":"info","ts":1554701012.238218,"caller":"app/server.go:192","msg":"Current version is 5.9.0 (5.9.0/Fri Mar 15 22:02:32 UTC 2019/5ef499caae2bb751438b19151a9fcb4b27830bca/none)"}
{"level":"info","ts":1554701012.2382772,"caller":"app/server.go:193","msg":"Enterprise Enabled: false"}
{"level":"info","ts":1554701012.2382958,"caller":"app/server.go:195","msg":"Current working directory is /opt/mattermost"}
{"level":"info","ts":1554701012.2383645,"caller":"app/server.go:196","msg":"Loaded config file from /opt/mattermost/config/config.json"}
{"level":"info","ts":1554701012.243341,"caller":"sqlstore/post_store.go:1287","msg":"Post.Message supports at most 16383 characters (65535 bytes)"}
{"level":"info","ts":1554701012.291516,"caller":"jobs/workers.go:68","msg":"Starting workers"}
{"level":"info","ts":1554701012.2916234,"caller":"app/server.go:400","msg":"Starting Server..."}
{"level":"info","ts":1554701012.2921586,"caller":"app/server.go:460","msg":"Server is listening on [::]:8065"}
{"level":"info","ts":1554701012.301582,"caller":"app/web_hub.go:75","msg":"Starting 2 websocket hubs"}
{"level":"info","ts":1554701012.3043194,"caller":"jobs/schedulers.go:72","msg":"Starting schedulers."}
{"level":"info","ts":1554701012.3442574,"caller":"commands/server.go:105","msg":"Sending systemd READY notification."}
<div id='root'>
<div class='error-screen'>
<h2>Cannot connect to Mattermost</h2>
<hr/>
<p>We're having trouble connecting to Mattermost. If refreshing this page (Ctrl+R or Command+R) does not work, please verify that your computer is connected to the internet.</p>
Any help on this would be highly a[appreciated.
↧
Community Design Meeting: Folded Reply Threads
Is there any feedback on what the results of the design meeting have been? Is there a ETA time for this feature?
Best regards,
D.R.
PS: Unfortunately I couldn’t attend the meeting.
↧
↧
Community Design Meeting: Folded Reply Threads
Indeed! Sharing notes from https://community.mattermost.com/core/pl/uwatc4o49jy6xjrth8ge4kbr5a below
Design Call Notes
Meeting recording: https://drive.google.com/file/d/1WddA7BROMoVBIKpt53roxAA651k8WuSc/view?usp=sharing
- Additional products to research
- Zulip, LinkedIn (narrative feed), Reddit, Twitter, Outlook (conversation view button)
- Issues with replies in Mattermost right now
- Replies are not discoverable - meaning users are creating parent posts rather than replies. We should make it easier to reply from a click interaction stand-point
- Why not allow clicking on the whole post to reply? Seems to be consensus that this would be a better UX than requiring users to click the reply arrow. This would help people keep threads in order.
- Post hover menu with reply option is far away from the users attention. Consider showing reply option closer to the profile picture or below the message.
- Consider inline input field for replies
- Need clearer UI indicators of a reply vs a new post - grey bar is insufficient. Consider colors, intents, different sizing of profile pics
- Parent posts mixed with replies causes major distractions in the channel
- Replies are not discoverable - meaning users are creating parent posts rather than replies. We should make it easier to reply from a click interaction stand-point
- Concerns about proposed design option
- Notifications: if everything is collapsed by default messages are definitely going to be missed
- Mixed feelings about implementing an “All Threads” view, but having that option is a good idea.
- “Users love choice”
- “Might be information overload”, “want to see threads in the channels they live in”
- Mixed feelings about implementing an “All Threads” view, but having that option is a good idea.
- Most conversations happens in replies. That’s a lot of extra effort to read messages if I have to expand every thread to read messages.
- Notifications: if everything is collapsed by default messages are definitely going to be missed
- Alternate design approaches:
- On-demand expanding and collapsing of different threads
- Threads are expand by default and have an option to collapse
- We should remember the users choice for which threads are expanded/collapsed when they switch channels
- When expanding a thread, all the replies should be in chronological order without other parent posts in-between
- Smaller indicator in the post chronology that is a jump to reference/parent post or
- Treat replies as an event in the channel with a different visual treatment (ie system messages). When clicked it could expand or open the RHS to that message.
- On-demand expanding and collapsing of different threads
- Admin Control:
- Admins should have the control of the defaults for users
- Need option to disable at the system and end user level
- Consider team and channel admin level controls
- Consider this as a functionality improvement over existing threading, rather than something that should be “turned on” or “turned off”. If it’s done well there’s no need for a setting.
- Other considerations or user stories:
- We should not allow parent posts to be resorted. Chronology is important to maintain.
- “Opening up the side panel is a distraction to what happens in the center channel”
- Possibly explore inline input fields
- Threads within threads
- Designs in general should consider what provides the most value benefits for the masses rather than being afraid to break corner cases.
- Thoughts on improving design calls:
- Positive reactions to the design call
- Would like to see this happen more with other designs
- Optional introductions from people other than Mattermost
- Provide a feedback survey after the call
↧
Video/audio messages with external client
Does the mattermost has the ability to make video/audio calls with people outside the company?
If so, what are the conditions?
Another thing: if the video calls are possible, could I share the screen to every participant?
Thanks for your answer!
Cheers
↧
Log files not rotating
Hi @daveokeeffe,
A response from a community member:
AFAICS, logs are rotated once the log file reaches a size of >= 100 MB .
↧
Video/audio messages with external client
Hi @Krzysiek,
Yes, this is supported via plugins. More information about options is here: https://docs.mattermost.com/deployment/video-and-audio-calling.html
↧
↧
Client Stuck on Startup
Hi @RbDev,
Does this occur regularly? Would you be open to sharing any errors in logs you see when clicking “Report a Problem”?
↧
Chain notifications issue
Hi @RbDev,
I wasn’t able to reproduce this just now on a v1.18 build version. Do you have access to the beta app to test this on either Build 183 or 184?
↧
Issue with TLS connectivity
Hi @Miguel,
Would you be open to joining our Peer-to-Peer Help channel on our community server for more help on this issue?
I’m not sure what the solution is and I haven’t received feedback from our team in the past few days on this yet.
↧