Access real name in quote display

October 11, 2017, 12:24 pm

≫ Next: API or other way to generate topicId and discourseEmbedUrl list

≪ Previous: "likes received count" includes those received through PM too

$

0

0

@pfaffman wrote:

Continuing the discussion from Display real name instead of username in a quote?:

I need for quotes to display the user real name exactly the same way that they are displayed in posts. In this image, “sam:” should be something like “Sam Saffron (sam):”

I think that this would be more consistent, but it matters only if you have meaningless usernames.

My questions:

• Can I fix this with a theme or will it take a plugin?
• Can someone point me to a similar example?

This seems like it should be trivial, but I’m lost on this end of things and don’t know where to start.

Posts: 1

Participants: 1

Read full topic

---

API or other way to generate topicId and discourseEmbedUrl list

October 11, 2017, 2:32 pm

≫ Next: Moderating content

≪ Previous: Access real name in quote display

$

0

0

@maiki wrote:

I have Discourse comment embedding for a site generated by Hugo. Everything works fine, killer set up. My site outputs a few different formats, not all for a web browser. Also, a lot of my visitors use text browsers. So I was thinking of including a link to the topic, for all those folks that won’t see the thread load on the page.

It is kinda dicey, but I can obviously construct URLs with a pattern like https://discourse.example.org/t/$SLUG/, and that works for most cases, but doesn’t feel as nice as just linking to the exact URL as Discourse knows it.

Hugo has a function called getJSON, so I figured I would just call that at build time and key the values off of the discourseEmbedUrl, but I don’t think that is included in any output.

An aside: Do you know there are docs for the Discourse API?! I have mostly gotten along without them, but they also make an excellent reference.

http://docs.discourse.org

The question

Is there currently a way to pull in the discourseEmbedUrl fields for posts in JSON? And by that I mean without directly accessing the database as well.

Alternatively, is there a pattern to permalink generation in Discourse that can be used here?

Posts: 1

Participants: 1

Read full topic

Moderating content

October 11, 2017, 3:35 pm

≫ Next: End of Life for Ubuntu 14.04 Trusty and Discourse 1.9.0.beta10?

≪ Previous: API or other way to generate topicId and discourseEmbedUrl list

$

0

0

@testingsoftware wrote:

Hi all,

If I set up different categories, can I allow people to post freely in some but moderate the content before goes live in others?

If I set the category to Watching it will notify me of new posts but i won’t be able to moderate them before going life.

I’ve read somewhere that this might be done in the trust levels but I want to moderate by categories, not users.

Since I am asking about moderating. Sometimes in the past we had problems with some posts and had to check all the posts from specific users. Can this be done and how?

Thanks.

Posts: 1

Participants: 1

Read full topic

End of Life for Ubuntu 14.04 Trusty and Discourse 1.9.0.beta10?

October 11, 2017, 3:51 pm

≫ Next: Desired URL lost if `login required` is enabled and social logins are used

≪ Previous: Moderating content

$

0

0

@fearlessfrog wrote:

I raised this in the how-to topic linked to the upgrade page, but it’s probably better off here.

Essentially I’m trying to work out if I need to update to Ubuntu 16 to run the latest stable build of Discourse now? A good topic for doing that looks like this one:

This looks like it is due to the latest docker-ce version for 14.04 being below what is required to run the latest Discourse stable image. Not sure, so any help appreciated.

Posts: 4

Participants: 2

Read full topic

Desired URL lost if `login required` is enabled and social logins are used

October 11, 2017, 4:17 pm

≫ Next: SSO fails to login on new browser instances

≪ Previous: End of Life for Ubuntu 14.04 Trusty and Discourse 1.9.0.beta10?

$

0

0

@pfaffman wrote:

If you visit https://discourse.fictiousexample.com/t/my-fine-topic/12345 and login required is enabled, you’re redirected to https://discourse.fictiousexample.com/. Then you have to click the login button, and then you’re redirected back to the home page rather than the topic that you wanted in the first place.

What I would expect to happen (and what my client using auth0 wants to happen) is when you access a topic and are not logged in, you’d go straight tot the log in and be redirected to the topic after you’re logged in.

I thought at first it was a problem with GitHub - auth0/discourse-plugin: Discourse plugin to authenticate with auth0., but the problem seems to be with the login required setting rather than the plugin.

This seems similar to the problem of trying to access a protected topic when you’re not logged in. What happens in that case is you get a 404 and are then on your own to log in and try again to access that URL.

Would it be possible to when hitting a route that is protected to give the user an opportunity to log in before giving up?

Posts: 3

Participants: 2

Read full topic

SSO fails to login on new browser instances

October 11, 2017, 6:33 pm

≫ Next: Links don't open in a new tab

≪ Previous: Desired URL lost if `login required` is enabled and social logins are used

$

0

0

@bufordtaylor wrote:

Hi all,

I’ve had SSO running for a few months successfully until suddenly Cloudflare started to throw 502’s.

My setup:

1. program.aaa.com is a heroku app
2. discuss.aaa.com is a DO discourse instance

The logs are really strange

2017-10-12T01:10:45.332164+00:00 app[web.1]: Processing by DiscourseSsoController#sso as HTML Parameters: {"sso"=>"[...]", "sig"=>"[...]"}
2017-10-12T01:10:45.578585+00:00 app[web.1]: Redirected to https://discuss.aaa.com/session/sso_login?sso=bm9uY2U9ZDdkZmEzYzYxZmU1YTJjMWFhYTExYzdlOWEwODVkMGQmbmFtZT1C%0AdWZvcmQrVGF5bG9yJnVzZXJuYW1lPUJ1Zm9yZCtUYXlsb3ImZW1haWw9YnVm%0Ab3JkdGF5bG9yJTQwZ21haWwuY29tJmF2YXRhcl91cmw9ZGF0YSUzQWltYWdl%0AJTJGcG5nJTNCYmFzZTY0JTJDaVZCT1J3MEtHZ29BQUFBTlNVaEVVZ0FBQWs0%0AQUFBSk9DQVlBQUFCQldZajFBQUFnQUVsRVFWUjRYb1M5MlhObDU1WGR1ZTQ4%0AWDh3emtITW1LWklxU2FXSkVpV1Z5MzdvZnV1TzdwZU82SCUyRlRFWGFWMnk2%0AWGJWVkpvZ2FLTTVremhod3dBeGQzbmpwJTJCYTU4RElDbktUZ1VFSmhLNHVP%0AZWM3OXZmMm11dnZYYW1PVE0zbGFUeGVLenAxUCUyRjVyWDh5bVl5JTJGbnMz%0ARzUlMkZUdmZPYm5KcE9KJTJCSEglMkJ6cmZ5MyUyRkgxY2ZKNkdXV3pXWCUy%0AQmtmJTJGaVo4WGprNyUyQlhybVF3ZjhYUFMxSiUyRlRqJTJCdHZLcjZQMTh0%0ASXZKM01SUHhQbWlncmZuOUdXV1g5cyUyQlBKUktQaFdNUGhTSVY4WHMxR1Rh%0AVmlRWnFPbGM5blZhMVZ0Ykt5cUZ1M2IycCUyQmZsYTU1RFdueW1veWxVYWpp%0AZlpldk5MSGYlMkY1VXIxNGRLcHN0S0pzdEtac3JhbmxsVFclMkIlMkYlMkZi%0AYVdGaGMwbll5MHYlMkY5U1gzejV1VjY5ZXFsJTJCZjZEcFpIcDV2WlBKMUg5%0AWE5xT1o1b3cyTmpZMFB6JTJCdlVybWtUcWV0Rnk5ZXFOVTY5M1Z6VDNxOXJn%0AYkRnU2Jqc1NxVnNoWVg1OVZvMUpRdjVEUWNEblRSdWxDMVZ0R3RXNXRhWFYx%0AVW8xRlJxWmhMbmxGVzJWeGVyMThmNk05JTJGJTJGbFRQbiUyQiUyRnBvalhR%0AWkNRVkNubmY1JTJGR1kzOE85NW9aekMlMkJOJTJCNW5NNSUyRjMwOEhDb3pu%0AYXFZenltWDVmbEljN05OM2JpeDZldXRWY3ZLNVhpZHNiS1pqSXI1a25MWkxE%0AJTJGcTE2aFVTcjcyMFlocjZhbmJia3ZUaWNxVmlncmNmNTVSTHFkQ29lRFBH%0AV1UwSEkzVjdmZjk5MXF0cmxhN284ZFBudW5WJTJGcjQ2bmE3Nmc0RkclMkZM%0ANWNYdVZ5VmNWeVJZVlNSY1ZxVGFWcVhkVjZVNVY2VThybTFPNzJKT1ZVcnRh%0Aa1RFNmRibCUyRjVZa256QzBzcUZNdnE5Z2NhVHpMJTJCV3FNeG8lMkZuNUJm%0AVjdmVDE3OWx5bnA2ZSUyQmxsS3g1SHRmTHBXOFZnYTluazZPajlYcmRKVEpU%0ARlV1RmRTb1YzMSUyRmh2Mk9CdjIyZXQyMlhyJTJGWTA4TXZ2OUQ1MmFuS2xa%0ASXlXYW5mNjRvSFVDcmtsYzJ3SmdmS0pxJTJGQm11TSUyQlRzYnNvWWttckh0%0AV0FudklLNEoxenQ3SktaZmpvNkJjTHUlMkY3Rk90MW9pbjdhREtLZmNoYVMz%0ANHVrOG41WHZNYXNSJTJCbThmckpYdVgxeEI0WkRGWE81VFhmcUtzd25tallh%0AdW05ZSUyRmYxJTJGJTJGNWYlMkY3ZnVyVzFxJTJGJTJCbHpIZTNzcUgxd3BI%0ARzdyZUprb2xJbW8wbzJxOXgwNHZVeUdRJTJCVm1VeVV6MlpWTEJUOHV2MSUy%0AQlQ0TkJYOFB4TVBhNW43VTBuckkzY2lvVVM4cmtjaHBPeGhxTyUyQlJocHhP%0AdE5KNzdXWXJIa3o5UEp4RCUyQlh6JTJCUlV6T2RWeWhjMEdQVjEzRHJSYURC%0AUUpWZnl2N0YzeHBPeEp0T3g3d0ZyMCUyRkdBd09MUU5mRm45Z0JmaTdqRDBw%0AejYlMkIlMkZoZDJXeGVtV3pPNzlldk41NWMzVGUlMkZLamMzNGlCYmVreWNt%0ARWdEWmRSVlRyMVNXYVBaV1MyOSUyRlIyOTk2dGZhZmJPYlozbjh1cGtjeHBt%0AOHhxTXBWNXZvUEZ3b3V5VVZSb2ZXVCUyRjNpZGNXajQyWU5wcU1OSndNZlc4%0AeXVZempSWjQxTk0ybzMlMkJ1cGRYNnU4WEI4ZVolMkZZMTkxdVQ2MVdTOFZp%0AVVd2cmE1cWJuVk9wd1A2VTE5M0RyejdYZiUyRm1IJTJGNmp0cDQ5VktlYVVu%0AUXpWdlRqVFpOaFRJVHRWUHNQN21YaiUyRnM1N2lrbGxERVFpbUdmWjV4RWZX%0AMDJnMDFIRFljNnp5dWVBemdYdERqT0hlOFR5NE51NXhWcms4ejczZ1dGVElG%0AeHlYaTRXOHlxV2lxcFVLdjBXRGZwY0lyakxmeDVxWlRwWExFSjk0YnZGdWF0%0AV0tZMUd6V1k5OXBZbkdvNUVtVSUyQjVoeERMaVM2RlFWTEZJM09hWlJreG1m%0AW

There are TONS more of this omitted ^

My SSO code is straight out of the doc: Official Single-Sign-On for Discourse (sso) this is my class: discourse/single_sign_on.rb at master · discourse/discourse · GitHub

This is my controller

class DiscourseSsoController < ApplicationController
  def sso
    secret = ...
    sso = SingleSignOn.parse(request.query_string, secret)
    sso.email = ...
    sso.name = ...
    sso.username = ..
    sso.external_id = ...
    sso.sso_secret = secret

    redirect_to sso.to_url("https://program.aaa.com/session/sso_login")
  end
end

The logs I get from verbose SSO logging in discourse don’t really tell me much

/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/logster-1.2.7/lib/logster/logger.rb:93:in `add_with_opts'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/logster-1.2.7/lib/logster/logger.rb:50:in `add'
/usr/local/lib/ruby/2.3.0/logger.rb:498:in `warn'
/var/www/discourse/app/controllers/session_controller.rb:35:in `sso'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_controller/metal/basic_implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/abstract_controller/base.rb:186:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_controller/metal/rendering.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:131:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_controller/metal/rescue.rb:20:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-5.1.4/lib/active_support/notifications.rb:166:in `block in instrument'

Does anyone know where to start digging on this one. My discourse is currently down.

UPDATE:

It turns out I was sending raw image data to Discourse which went over the http header limit

Posts: 2

Participants: 1

Read full topic

Links don't open in a new tab

October 11, 2017, 6:38 pm

≫ Next: Discourse works only from localhost (using PuTTy), Unable to connect via IP Address or domain name

≪ Previous: SSO fails to login on new browser instances

$

0

0

@jonobacon wrote:

Currently using v1.9.0.beta12 +21 in a deployment and have the option checked to open links in a new tab and it opens in the same tab.

I am testing this in Chrome on a Mac. The issue occurs in both starting posts in a new topic and replies.

Anyone else seeing this?

Posts: 7

Participants: 4

Read full topic

Discourse works only from localhost (using PuTTy), Unable to connect via IP Address or domain name

October 11, 2017, 7:01 pm

≫ Next: Daily usage streak and badges (for building a habit)

≪ Previous: Links don't open in a new tab

$

0

0

@CyberSathya wrote:

Hello there,

I’ve installed Discourse on Docker with Ubuntu from Azure (not from one-click-install). I’ve connected to the system via Putty, and have made a tunneling to local host, and thereby, i’m able to complete the installation process with the help of localhost. Now, i’m unable to reach the site via IP address or via domain name. How to take things forward.

Screenshot (398).png792x396 23.9 KB

Details:
Virtual IP address: 52.172.38.9
Domain name: forum.vaaithaa.com
Method: Created a ‘A’ record for ‘forum’ pointing to “52.172.38.9”.

Posts: 4

Participants: 2

Read full topic

---

Daily usage streak and badges (for building a habit)

October 11, 2017, 7:02 pm

≫ Next: What plugins do you use - and why?

≪ Previous: Discourse works only from localhost (using PuTTy), Unable to connect via IP Address or domain name

$

0

0

@jonobacon wrote:

Hi Everyone,

When I roll out Discourse to my clients, a key point I always emphasize is the importance that (a) people across the organization use it (not just “community managers”, and (b) they use it on a daily basis.

For the latter, I explain habit theory and the notion that if we commit to something for around 66 days it becomes a habit. As such, I ask people to commit time in their calendars (if only 15 - 30mins a day) to visit the forum, respond to topics, and post new topics.

As such, this daily use is (I believe) key in making Discourse communities “stick”. One idea I wanted to propose here is that there is a way in which users can see their daily usage streak in the same way other services work such as fitness and mindfulness apps.

A few ideas how this could work:

• At a simple level, this could be delivered via badges (e.g. badges for 5, 10, 15, 30, 60, 100, 150, 300, 365 days).
• Ideally, on top of this, users can see their own run streak and admins can sort users by a run streak (important for people who run Discourse rollouts to see which people are participating and which are not).

Sadly, I don’t have time to build this myself (you also don’t want my terrible code), but is anyone else interested in something such as this, and maybe want to build it?

Posts: 5

Participants: 4

Read full topic

What plugins do you use - and why?

October 11, 2017, 7:53 pm

≫ Next: Docker version 1.10.3 not supported

≪ Previous: Daily usage streak and badges (for building a habit)

$

0

0

@CarsonWeitnauer wrote:

Hi,

I’m curious what plugins established Discourse forum owners are using - and why. It’d be interesting to understand not only what plugin(s) you use, but what purpose you use it for. Hopefully this sparks some new ideas for everyone.

Posts: 2

Participants: 2

Read full topic

Docker version 1.10.3 not supported

October 11, 2017, 8:01 pm

≫ Next: Slack threads and chat integration plugin transcripts

≪ Previous: What plugins do you use - and why?

$

0

0

@Jose_C_Gomez wrote:

HELP,
All of the sudden when I run ./launcher rebuild app I get this error
ERROR: Docker version 1.10.3 not supported, please upgrade to at least 17.06.2, or recommended 17.06.2

The last thing I did was run the “upgrade” command from the web interface and it failed.

Posts: 2

Participants: 2

Read full topic

Slack threads and chat integration plugin transcripts

October 11, 2017, 9:57 pm

≫ Next: Selecting new message in Slack "post transcript", slackbot returns an error

≪ Previous: Docker version 1.10.3 not supported

$

0

0

@mcwumbly wrote:

Continuing the discussion from Set up Slack notifications using the discourse-chat-integration plugin:

Just tried typing /discourse post in a Slack thread and got this response:

/discourse is not supported in threads. Sorry!

Interestingly though, typing /discourse post in the normal channel composer does pick up messages from within threads.

I also tried creating two threads and then alternating posting messages in each thread.

Then, when I did /discourse post 10, the transcript created had each of these messages interleaved…

Posts: 1

Participants: 1

Read full topic

Selecting new message in Slack "post transcript", slackbot returns an error

October 11, 2017, 10:26 pm

≫ Next: Remove emojis from browser tab title (not from topic title, please reopen!)

≪ Previous: Slack threads and chat integration plugin transcripts

$

0

0

@mcwumbly wrote:

When I use the /discourse post slash command and then choose some other starting message from the dropdown, slackbot responds with this message:

Darn – that didn’t work (error message: 500_service_error). Manage the app at

slackbot-error-transcript.png1168x104 23.5 KB

However, if I then click the “Click here to draft a post on Discourse with a transcript” link, it does start with the message I chose, so in fact, it all seems to be working.

But the error message is still confusing…

Posts: 3

Participants: 2

Read full topic

Remove emojis from browser tab title (not from topic title, please reopen!)

October 12, 2017, 1:00 am

≫ Next: Moderating posts in some categories

≪ Previous: Selecting new message in Slack "post transcript", slackbot returns an error

$

0

0

@jack2 wrote:

Emojis in a topic title:

• uselessly increases the length of the browser tab title,
• add icons in a place where only tab icons should be.

See here (the tab title almost disappears because of the ‘glasses’ emoji, and the additional icon is a UI nuisance):

Summarizing the title as much as possible for areas where space matters should be a goal, and removing emojis from the tab title looks like an easy win.

EDIT: Notice that I’m not talking here about removing emojis from topic titles, which is a great feature.

Posts: 4

Participants: 2

Read full topic

Moderating posts in some categories

October 12, 2017, 1:35 am

≫ Next: [PAID-job] Create an import/export script for Modx Discuss

≪ Previous: Remove emojis from browser tab title (not from topic title, please reopen!)

$

0

0

@testingsoftware wrote:

Hi all,

If I set up different categories, can I allow people to post freely in some but moderate the content before goes live in others?

If I set the category to Watching it will notify me of new posts but i won’t be able to moderate them before going life.

I’ve read somewhere that this might be done in the trust levels but I want to moderate by categories, not users.

Since I am asking about moderating. Sometimes in the past we had problems with some posts and had to check all the posts from specific users. Can this be done and how?

Thanks.

This post is in “community” but cannot delete it to change it to here.

Posts: 1

Participants: 1

Read full topic

---

[PAID-job] Create an import/export script for Modx Discuss

October 12, 2017, 2:07 am

≫ Next: Safari press ESC close edit model

≪ Previous: Moderating posts in some categories

$

0

0

@Carlo wrote:

What would you like done?
I have a forum powered by Discuss on Modx cms (Discuss 1.2-pl).

I want to create to export the forum ( users, categories and posts ) to Discourse.

I can provide a local install of Modx/discuss from Mamp on Mac.

Optional work:

Even if the final result would be importing datas to Discourse. I’m also interested in customizing Vanilla Porter. (Vanilla Porter 2.3 — Vanilla Forums)

Vanilla export file works like a charm with Discourse. And I am sure I will be able to re-use the script the future.

When do you need it done?
In a week max.

What is your budget, in $ USD that you can offer for this task?
$250-550. Of course, it is negotiable, but depends on your experience.

Bear in mind you’ll have to work locally. I won’t give you access to a live server.

Thanks

Posts: 3

Participants: 2

Read full topic

Safari press ESC close edit model

October 12, 2017, 3:19 am

≫ Next: Discourse build is broken

≪ Previous: [PAID-job] Create an import/export script for Modx Discuss

$

0

0

@Leon_Tian wrote:

I can’t close edit model when I press ESC btn in Safari.

Posts: 1

Participants: 1

Read full topic

Discourse build is broken

October 12, 2017, 3:29 am

≫ Next: Reply bot for Discourse?

≪ Previous: Safari press ESC close edit model

$

0

0

@Bas wrote:

Got an error when rebuilding (without any changes in app.yml):

I, [2017-10-12T10:23:27.710239 #13]  INFO -- : > cd /var/www/discourse && chown -R discourse /var/www/discourse
chown: cannot access '/var/www/discourse/config/initializers/000-rails-master-polyfills.rb': No such file or directory
chown: cannot access '/var/www/discourse/config/initializers/100-rails3_ar_after_commit_tests.rb': No such file or directory
155:signal-handler (1507803822) Received SIGTERM scheduling shutdown...

Saw this commit Remvoe unused file. · discourse/discourse@630f7bf · GitHub

Seems like the file removed by @tgxworld isn’t as unused as it seems?

[edit] removed support tag, I succesfully downgraded to the Beta branch, will be using that from now on; have been bitten a bit too much by suddenly broken builds.

Posts: 1

Participants: 1

Read full topic

Reply bot for Discourse?

October 12, 2017, 3:57 am

≫ Next: Emoji's in title shown as code on initial load of a topic page

≪ Previous: Discourse build is broken

$

0

0

@Sujan wrote:

Has anyone built a bot like thing that can reply to posts if specific conditions are met (e.g. "topic in category foo, does not contain string bar)?

I have quite a few “issue” type topics in the developer community I am moderating, and 75% of my replies are just asking for software and environment information. It would be great if I could have a bot version of myself that could check with some simple rules and then create a reply to the topic if they are not met.

Posts: 3

Participants: 2

Read full topic

Emoji's in title shown as code on initial load of a topic page

October 12, 2017, 5:25 am

≫ Next: Mentioning @trust_level_0

≪ Previous: Reply bot for Discourse?

$

0

0

@schungx wrote:

Steps to Reproduce

1. Load meta.discourse.org (Refresh)

2. Click on any topic with an emoji in the title

3. Look at the tab title – emoji as code

Note: Reloading content via XHR sets the emoji correctly. It is only with a fresh load that the emoji code appears (e.g. from clicking on a notification link jumping directly to a topic).

Posts: 1

Participants: 1

Read full topic