Quantcast
Channel: Mattermost Discussion Forums - Latest posts
Viewing all 25529 articles
Browse latest View live
↧

Disable private channels and direct Messages

February 6, 2019, 7:41 am
$
0
0

Hi @mohammedfazil,

If you are on Mattermost Server v4.9 or earlier, you can use these settings:

If you are on Server v5.0 or later, you’ll need to use Enterprise Edition feature called Advanced Permissions:

These features restrict who is allowed to create private and direct message channels, but otherwise these types of channels cannot be completely disabled.

↧
Search

Jira Plugin Failing to Post

February 6, 2019, 8:06 am
↧
↧

Jira Plugin Failing to Post

February 6, 2019, 8:09 am
$
0
0

Is there an ETA on the fix or release? We’re looking to migrate from Slack but at the moment without a working Jira integration it’s a no-go.

↧

Jira Plugin Failing to Post

February 6, 2019, 8:45 am
$
0
0

The jira Ticket is planned for 5.8

So 16.02.2019

↧

Delete this post

February 6, 2019, 11:56 am
$
0
0

delete this post
delete this post

↧
↧

Incoming Webhooks : Payload and Attachment Documentation

February 6, 2019, 2:42 pm
$
0
0

I know this is old, but for anyone wanting to do this in python3, this is the inelegant way I’ve been posting IWH attachments.

#!/usr/bin/python3
import urllib3
import json
import certifi

mmURL = 'https://<yourwebhookURLhere>'

output_data = {}
output_data['text'] = 'text)'
output_data['username'] = 'username'
output_data['icon'] = 'icon URL'
output_data['title'] = 'title'
output_data['pretext'] = 'pretext'

attachment_data = {}
attachment_data['attachments'] = [output_data]
output_data_json=json.dumps(attachment_data)

def SendToMM(output_data):
	http = urllib3.PoolManager(cert_reqs='CERT_REQUIRED',ca_certs=certifi.where())
	req = http.request("POST", mmURL, body=output_data_json, headers={'Content-Type': 'application/json'})
	print (req.data.decode("utf-8"))
	return

SendToMM(output_data)

Hopefully it’ll be of use to someone.

↧

Inline link with nested parentheses does not work

February 6, 2019, 5:58 pm
$
0
0

Summary

Posting an inline link with nested parentheses in the URL does not work.

Steps to reproduce

Mattermost 5.6, any client.
Post this message:

how about: [hmm](https://somewhere?param=(currentUser()))?

Expected behavior

Expect inline link with title hmm and URL https://somewhere?param=(currentUser())

Observed behavior

No inline link. The original markdown syntax appears directly. However, part of the URL (https://somewhere?param=) is then detected as an auto link and becomes clickable.

↧

Inline link with nested parentheses does not work

February 6, 2019, 7:34 pm
↧
Search

Unable to send websocket requests through WAF

February 6, 2019, 8:06 pm
$
0
0

For feature requests, please see: http://www.mattermost.org/feature-requests/.

For troubleshooting questions, please post in the following format:

Summary

Our installation of Mattermost was partially working, however, without the support of websockets, we are unable to use most of the useful functionalities, such as notifications and other UI features.

Steps to reproduce

Install mattermost behind a Web Application Firewall (WAF).

Expected behavior

The following functionalities should be working:

  • Notifications
  • Able to delete and edit messages
  • Able to send reaction emojis
  • The system admin able to manage mattermost

Observed behavior

The functionalities documented above are not working without websockets. I can confirm it is working if I ssh tunnel to the designated port - then I can use the functionalities above.

I need help in how to disable websockets functionality and fallback to other mechanism?

Or any suggestion on how to enable WAF to support websockets? Unfortunately we have no control over the WAF but according to the vendor, the WAF does not support websockets.

Another idea - is it possible to send websocket requests as https? then change it to wss protocol?

Any advice would be much appreciated.

↧
↧

Zoom Plugin - Are there limitations?

February 6, 2019, 9:37 pm
$
0
0

Hello!
My questions refer to the Team Free Edition:
Are there limitations when using the Zoom Plugin e.g. regarding

  • Number of participants?
  • Time limit for group conferences?
    The native Zoom Basic Edition specifies such limitations.
    Sorry, asking these details. We haven’t even installed Mattermost. We are still checking the features of products that might meet ours needs.

Best regards, bigboreshooter

↧

No Custom Emoji Button

February 7, 2019, 1:49 am
$
0
0

Hi @amy.blais,

once more thank you that your are trying to help me tracking down this mysterious error.
Well, I copied the config.json file and gave it the read and write access for the mattermost user and mattermost group. Maybe, I should stress, that the server is running without any flaws but the missing “Custom Emoji” button. The Mattermost version 5.7.0. ( and after an update 5.7.1). Before moving this Matttermost instance, I did an update from 4.0.0. to 5.7.0.

Yesterday I set the Log Level from “INFO” to “DEBUG” and followed the log. But there was nothing conspicuous. So I am not sure, if I should post a part of it and if yes, which part to post.

Furthermore, I think, that it is may be a good idea to mention, that I am handling the two mattermost instances, running right now on same server, with the help of an nginx proxy. I set two different ports and created to files in /etc/nginx/sites-available and linked them into the sites-enabled folder. May be something goes wrong here.

I am wondering, what would happen, if I deleted the Emoji table and the /data/emoji folder manually. Will Mattermost recreate them?

I do not know what to do next.

Thank you.
Nils

P.S.: A part of the debug log file:

{“level”:“debug”,“ts”:1549486313.9214416,“caller”:“web/handlers.go:50”,“msg”:“GET - /api/v4/redirect_location”}
{“level”:“debug”,“ts”:1549486313.983628,“caller”:“web/handlers.go:50”,“msg”:“GET - /api/v4/posts/768wrej4cffyjf7m7jnsqjnwko/reactions”}
{“level”:“debug”,“ts”:1549486315.3645847,“caller”:“web/handlers.go:50”,“msg”:“GET - /api/v4/files/6jk184xsqbnduk3qfby8mgbnoo/preview”}
{“level”:“debug”,“ts”:1549486315.4459167,“caller”:“web/handlers.go:50”,“msg”:“GET - /api/v4/emoji/name/bindabei”}
{“level”:“debug”,“ts”:1549486317.1389172,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/users/status/ids”}
{“level”:“debug”,“ts”:1549486318.0887284,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/channels/members/me/view”}
{“level”:“debug”,“ts”:1549486318.1288483,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/channels/members/me/view”}
{“level”:“debug”,“ts”:1549486318.198599,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/channels/members/me/view”}
{“level”:“debug”,“ts”:1549486318.2298832,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/channels/members/me/view”}
{“level”:“debug”,“ts”:1549486318.2849278,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/channels/members/me/view”}
{“level”:“debug”,“ts”:1549486332.6083848,“caller”:“app/email_batching.go:110”,“msg”:“Email batching job ran. 0 user(s) still have notifications pending.”}
{“level”:“debug”,“ts”:1549486339.2522783,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/users/status/ids”}
{“level”:“debug”,“ts”:1549486342.8636494,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/users/status/ids”}
{“level”:“debug”,“ts”:1549486350.761374,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/channels/members/me/view”}
{“level”:“debug”,“ts”:1549486350.8718364,“caller”:“web/handlers.go:50”,“msg”:“GET - /api/v4/users/me/teams/313ecjjg3tgui8qpo77qkfo5zh/channels”}
{“level”:“debug”,“ts”:1549486350.8725932,“caller”:“web/handlers.go:50”,“msg”:“GET - /api/v4/users/me/teams/313ecjjg3tgui8qpo77qkfo5zh/channels/members”}
{“level”:“debug”,“ts”:1549486354.0474448,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/channels/members/me/view”}
{“level”:“debug”,“ts”:1549486354.1020472,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/channels/members/me/view”}
{“level”:“debug”,“ts”:1549486354.1823897,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/channels/members/me/view”}
{“level”:“debug”,“ts”:1549486354.2397785,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/channels/members/me/view”}
{“level”:“debug”,“ts”:1549486354.298507,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/channels/members/me/view”}
{“level”:“debug”,“ts”:1549486362.6084046,“caller”:“app/email_batching.go:110”,“msg”:“Email batching job ran. 0 user(s) still have notifications pending.”}
{“level”:“debug”,“ts”:1549486369.6287596,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/users/status/ids”}
{“level”:“debug”,“ts”:1549486370.5399833,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/users/status/ids”}
{“level”:“debug”,“ts”:1549486371.7397945,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/users/status/ids”}
{“level”:“debug”,“ts”:1549486371.7987869,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/users/status/ids”}
{“level”:“debug”,“ts”:1549486377.1304507,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/users/status/ids”}
{“level”:“debug”,“ts”:1549486383.720822,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/channels/members/me/view”}
{“level”:“debug”,“ts”:1549486383.8308098,“caller”:“web/handlers.go:50”,“msg”:“GET - /api/v4/users/me/teams/313ecjjg3tgui8qpo77qkfo5zh/channels”}
{“level”:“debug”,“ts”:1549486383.8312895,“caller”:“web/handlers.go:50”,“msg”:“GET - /api/v4/users/me/teams/313ecjjg3tgui8qpo77qkfo5zh/channels/members”}
{“level”:“debug”,“ts”:1549486387.9609182,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/channels/members/me/view”}
{“level”:“debug”,“ts”:1549486387.9836218,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/channels/members/me/view”}
{“level”:“debug”,“ts”:1549486388.1024904,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/channels/members/me/view”}
{“level”:“debug”,“ts”:1549486388.1455967,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/channels/members/me/view”}
{“level”:“debug”,“ts”:1549486388.217537,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/channels/members/me/view”}
{“level”:“debug”,“ts”:1549486392.608404,“caller”:“app/email_batching.go:110”,“msg”:“Email batching job ran. 0 user(s) still have notifications pending.”}
{“level”:“debug”,“ts”:1549486395.0745063,“caller”:“app/web_conn.go:149”,“msg”:“websocket.read: closing websocket for userId=3xtkcg1wafys3mnfjk6bz1hd5e error=read tcp 127.0.0.1:8066->127.0.0.1:42810: i/o timeout”}
{“level”:“debug”,“ts”:1549486395.725799,“caller”:“web/handlers.go:50”,“msg”:“GET - /api/v4/websocket”}
{“level”:“debug”,“ts”:1549486395.7351317,“caller”:“web/handlers.go:50”,“msg”:“GET - /api/v4/plugins/webapp”}
{“level”:“debug”,“ts”:1549486395.7487931,“caller”:“web/handlers.go:50”,“msg”:“GET - /api/v4/users/me/teams/313ecjjg3tgui8qpo77qkfo5zh/channels/members”}
{“level”:“debug”,“ts”:1549486395.7487926,“caller”:“web/handlers.go:50”,“msg”:“GET - /api/v4/users/me/teams/313ecjjg3tgui8qpo77qkfo5zh/channels”}

↧

Developer setup bad node & npm version?

February 7, 2019, 6:41 am
$
0
0

Hello,
I clean installed node(v11.9.0) and npm (6.5.0) and launched “make run” to build run mattermost server & webapp but I get this error:

ERROR in ./root.jsx
Module build failed (from ./node_modules/babel-loader/lib/index.js):
SyntaxError: /home/pierre/go/src/github.com/mattermost/mattermost-webapp/root.jsx: Unexpected token (55:8)

53 | function renderRootComponent() {
54 | ReactDOM.render((

55 |
| ^
56 |
57 | <Route
58 | path=’/’

Can’t get it working, tried to change node/npm version to lower but didn’t work either . :frowning:

↧

Unable to import Slack private channel's data into Mattermost

February 7, 2019, 6:58 am
$
0
0

Hello
Are there any updates on “slack corporate export” import feature ?
can not move to mattermost without it…

↧
↧

Channel Notifications

February 7, 2019, 8:10 am
$
0
0

Good Morning,

Thank you for your response! The use case I am using here is to keep individuals within our company updated on client communications through Mattermost channels. So let’s say I am the account manager for client A, B, and C. If someone in the organization goes to client A and gets some information I would like that person to post that information in client A’s channel. Myself as the account manager, using keywords (see below) then I would get a notification in email. If someone goes to client D and posts an update in their channel, then I wouldn’t get an update in my email because I am not concerned with client D.

It is my understand based on the screen shot below, that if I place a keyword in the string, that I would get email notifications of any activity mentioning these keywords. Is that incorrect?

I hope that this helps with the understanding of my use case, let me know if I can provide further clarification.

Notifications%20on%20Mattermost
Notifications on Mattermost.png1000×848 62.8 KB
↧

Inline link with nested parentheses does not work

February 7, 2019, 12:03 pm
↧
Search

Developer setup bad node & npm version?

February 7, 2019, 12:05 pm
↧

Zoom Plugin - Are there limitations?

February 7, 2019, 12:16 pm
↧
↧

Channel Notifications

February 8, 2019, 3:23 am
$
0
0

You need to configure it differently. Like you did it will work when each message contains clienta as text.

Go to Channel Client A and klick on the channel name. You should see some options. Click Notification Preferences. Then you can change for desktop and mobile the behavior for reacting on every activity. The repeat it for every channel you need.

↧

No Custom Emoji Button

February 8, 2019, 3:05 pm
$
0
0

Hi @nils-schween,

Tips from a community member:

We’d recommend you to rename /data/emoji instead of deleting it to test what will happen (allows you to move it back in case it doesn’t help). Thanks for the log output. It might be interesting to see the log output during Mattermost’s start. Also, configuration values of EnableCustomEmoji would be appreciated.

↧

Unable to send websocket requests through WAF

February 8, 2019, 3:08 pm
$
0
0

Hi @zhaokoh,

Websocket support is a prerequisite for Mattermost.

Also, from a community member:

" Web Application Firewall " is rather generic, a software name and version would be helpful. Furthermore, more details regarding your network topology / security requirements are needed for suggestions. (But if you cannot modify the WAF and the vendor told you that your WAF doesn’t support Websockets, then that’s a bad omen, in my opinion.)

↧
Viewing all 25529 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>