I think one option we would be open to is a pr that allows you to set which TL has particular blocked words, cause blocking thread from tl0 and 1 is pretty much our intent here, plus we want to make the feature better, and there are tons of missing refinements here that are missing, like teaching people why a word is blocked (optionally) vs just saying sorry, not allowed
Hey @david - Just got a chance to try out the new feature to post threads… looks like it’s not quite working or us.
I tried each syntax or a couple different threads, but just get this in response:
Loading the transcript…
Using the normal command continues to work as it did before, though.
Also, when I tried posting a transcript from a private channel, I got this:
Darn - that slash command didn’t work (error message: 422_client_error). Manage the command at Discourse
I looked at the diff from the PR and thought perhaps it’d be necessary to add the conversations:history scope to the app on Slack, but I didn’t see that as an option. I tried adding the groups:history scope instead, but that did not seem to work.
Let me know if there’s anything else you’d like me to try for either of these issues. Thanks!
For ‘Private Channels’ you need to add the groups:history scope. For “Direct Messages” you need to add the im:history scope. You will need to ‘reinstall’ the app for changes to scopes to take effect (Slack’s UI should have prompted you to do this).
Are you seeing anything at /logs when the errors occur?
I used the /discourse post command from a public channel to great effect… but threads are now more common in many channels than main channel conversations, so still hopeful that some day this will work in a thread…
Update: w00t! just tried it again and it worked!
/discourse post https://ourdomain.slack.com/archives/C0591LA4X/p1529529151000359?thread_ts=1529528304.000177&cid=C0592LA4X
/discourse post thread https://ourdomain.slack.com/archives/C0592LA4X/p1529528304000177
Another update: I was also able to post a thread from a private channel.
I really want this to be true because it would make my life so much easier, but I don’t see anything about it in the Slack API documentation. I wonder if they gave giphy special alpha-testing access? Do you see documentation that I don’t?
More information, possibly: Today at work, one person in a thread complained about slack not allowing /giphy in threads and posted an image of slack telling them that it wasn’t supported in threads, and another person used /giphy successfully, in the same thread. Seems like there might be some A/B testing going on here.
Good news! I just merged a change to the plugin which adds support for Slack’s “Shortcuts” API. Now you can hit the … on a thread, click “Post to Discourse”, and you’ll be given a button which takes you straight to Discourse. No more fussing with slash commands or thread permalinks!
I found the problem! Our Chat Integration App wasn’t in the channel I was trying to post from. After inviting the app to the channel, I was able to post a transcript. Thank you.
Is it possible to automatically add the Chat Integration App in every Slack channel automatically, now and in the case of any new channel created in the future?
Changing the “Continue on Discourse” button text to something more like “Create Transcript” or the Name of the shortcut (default “Post to Discourse” but changeable) would make sense from a UX perspective, given that not all Discourse sites call themselves Discourse
Unfortunately I don’t think so, but I’d love to be wrong on that. I will look into whether we can improve the error message here so it gives you instructions on how to add the bot to the channel.
good point. We can certainly update the default to remove the word ‘Discourse’. But in the meantime, you should be able to search for “Continue on Discourse” in the admin panel and change it to whatever you like: Customize all text in Discourse
Edit: default button text is now Continue on Forum