@supermathie wrote:

If a posting in whisper mode is started but the page is reloaded by some means, it will revert to a non-whisper.

This can cause unintentional posting of information meant to be communicated only within a team since the whisper icon can be fairly subtle.

Posts: 4

Participants: 3

Read full topic

@Ryan_Nix wrote:

Hello,

We’re using Discourse for our Cloud Operations group at Northwestern University. I’m trying to insert an example sensible-playbook file but the Ansible YAML formatting isn’t working. Sorry to be “That guy”, but my Google searches didn’t turn up much, probably because I’m asking the wrong question. What is the best way to insert YAML code into Discourse post so that proper spacing is preserved?

---

• hosts: testing
  remote_user: root
  tasks:
  • name: "Add multiple ssh keys to the root account"
    authorized_key:
    user: root
    state: present
    key: '{{ item }}'
    with_file:
    • ~/Desktop/Certs/eudald.pub
    • ~/Desktop/Certs/mike.pub
    • ~/Desktop/Certs/russ.pub
    • ~/Desktop/Certs/ryan.pub

Should look like this:

Screen Shot 2017-10-16 at 3.01.47 PM.png1792x1091 91 KB

Posts: 3

Participants: 2

Read full topic

@OnyxZ32 wrote:

What would you like done?

We have a long-running vB 4.0 forum that we’d like to migrate to Discourse. This is a legacy community, so traffic isn’t anything crazy anymore (damn you Facebook!) but stats are:

Threads 279,185 Posts 4,593,429 Members 29,946

Several years ago we approached someone from this community to see what it would take to do this, but his assessment at the time was that our database was too big for Discourse. He simply didn’t know how things would work out since a migration of our size hadn’t been done. So we decided back then to keep things on vB 4.0. Fast forward to today and it looks like several forums of our size have been moved to Discourse without any real issues, so we’re putting our project out there again!

When do you need it done?

ASAP; we’re flexible but we want as little downtime as possible!

What is your budget, in $ USD that you can offer for this task?

We realize this is a large task and are prepared to pay several thousand dollars to complete it. I’d like to discuss specific quotes with those interested. We’d really like to work with someone who wouldn’t mind direct phone calls, who can provide examples of similar work and someone who would be interested in further project support as needed.

Thanks in advance Discourse community!

Posts: 11

Participants: 3

Read full topic

@tobiaseigen wrote:

I just had an interesting conversation with a colleague, who was having some trouble with her discourse notifications. She’s a hybrid user - most of the time she just uses email to participate in discussions but sometimes she logs in to start topics and like posts. This means that she often has dozens or even hundreds of notifications which she’d just like to dismiss. She did not immediately find the “Dismiss all” link on her own and when I told her about it she said it was not obvious at all.

Facebook has a “Mark all as read” link right at the top, which is probably what she is expecting. I’m sure many users have that expectation.

The top of the notifications menu is pretty full already - maybe a “Dismiss all” link could be added to the bottom right corner, next to “view older notifications”?

Posts: 11

Participants: 4

Read full topic

@tobiaseigen wrote:

In this same conversation with a colleague, she told me she was confused by the green and blue notification bubbles. She could not figure out what the colors represent, and she was especially confused because she had alot of both of them. In this case, she has moderator privileges but does not log in often - mostly she participates by email.

Correct me if I’m wrong, but besides the red flag-related bubbles, I think the green notification bubble only shows how many new personal messages you have while the blue notification bubbles are for everything else.

I know there are probably very good reasons for having a separate green bubble for personal messages, but in my community I don’t think there is any need and they are confusing. Perhaps an admin setting could be provided to simplify the UX and just display a single blue bubble indicating the number of new notifications?

Posts: 4

Participants: 3

Read full topic

@Oxyrus wrote:

Hello!

I would like to know if it’s possible to assign users to an specific group after they have finished the registration process, automatically.

Say I register a new user, he would be put into the Members group automatically, is that possible?

Thank you!

Posts: 6

Participants: 4

Read full topic

@tobiaseigen wrote:

This is the last bit of feedback from a convo I had with a member of my community who is confused by the notification menu. Placing it in support because it’s probably an intended feature that I am just not understanding and need to have explained to me so I can pass it on to her.

She was sharing her screen and showing me what happens when she selects notifications on the notification menu. She had hundreds of notifications (both green and blue) and was trying to systematically work her way through them. Weirdly, each time she clicked on an unread notification to for example read a message or post she was mentioned in, and then clicked on the notification menu again, the list of available notifications was completely different.

This is not what I see myself - I keep up with my notifications so I just see the ~10 most recent notifications on that menu.

Aside from the fact that this is probably not the intended/best use of the notification menu, it still seems weird to me that she would see different notifications each time she clicks the notification menu, and I can understand why she would be very confused and not know what to do. Given that she also uses email to participate, I advised her to just dismiss all the notifications and start fresh.

What’s going on here? Is discourse just trying to encourage her to read random old messages and posts?

Posts: 4

Participants: 2

Read full topic

@Drew_Warwick wrote:

In our Discourse forum, we have a few top level categories that exist to group their child categories. For instance, we have Feature Requests which contains Client/Studio/Web Features, Bug Reports which contains Client/Studio/Web Bugs, and Lounge which contains Off Topic and Platform Discussion.

The top level categories are locked because we had too many people posting in them instead of the appropriate subcategory – we would rather them guess which subcategory and get it wrong so their thread can be seen and moved versus posting in the top level and no one noticing it. The results of locking the top levels have been mostly positive, but we’ve also had an issue of users thinking the category is locked for them.

Instead of recognizing that there are subcategories to post in, they see the locked top level and think “Oh, I don’t have enough permissions to post feature requests.” I suspect that this is because the “New Topic” button is greyed out rather than the top level not appearing in the Create a new Topic category dropdown because the complains have always been “The category is locked”.

It would be nice if there was a way to communicate to users that a thread can’t be posted in because you’re meant to use its subcategories rather than them not having appropriate permissions. For instance, the ability to mark categories as top-level and have them show no topics in their list on Latest, but instead just a list of their subcategories similar to the category list.

Posts: 3

Participants: 2

Read full topic

@pfaffman wrote:

I just did an upgrade a couple hours ago and now there are a bunch of 500 errors.

I also tweaked db_work_mem, but that seems to have improved CPU usage. Could this be a bug?

TypeError: undefined is not an object (evaluating 'this.$("textarea.d-editor-input")') Url: https://www.rbxtrading.com/assets/application-05de2c20597af13808f6c5d089a30fcde34cf8a679eb18f6ca9a5dca67b421
Uncaught TypeError: Cannot read property '0' of undefined Url: https://www.rbxtrading.com/assets/application-05de2c20597af13808f6c5d089a30fcde34cf8a679eb18f6ca9a5dca67b421e3.js Line: 7 Column: 10052 W


Uncaught TypeError: Cannot read property 'href' of undefined Url: https://www.rbxtrading.com/assets/application-05de2c20597af13808f6c5d089a30fcde34cf8a679eb18f6ca9a5dca67b421e3.js Line: 2 Column: 1071
TypeError: undefined is not an object (evaluating 'this.$("textarea.d-editor-input")') Url: https://www.rbxtrading.com/assets/application-05de2c20597af13808f6c5d089a30fcde34cf8a679eb18f6ca9a5dca67b421

Posts: 7

Participants: 3

Read full topic

@kgoetz wrote:

Hi,

I’m looking to disable a number of SSO users.

The thread below confirms only those with no posts will be deleted (good), but I’m hoping to prevent all users created/synced via sso from being deleted in discourse no matter what their post count.

I do want discourse to keep deleting spam/invalid accounts.

Is such a thing possible?

Posts: 3

Participants: 3

Read full topic

@dje4321 wrote:

I enabled read-only mode on my forums and im not able to disable it.

I cant disable read-only mode via the /admin/backups because i cant login.

---

entering the docker image and disabling it via rails does not work either.

rails c
Discourse.disable_readonly_mode

---

entering the docker image and running

discourse disable_readonly

does not work either.

---

Anything im missing?

sorry if the bug category is not the correct category. I think this might be a bug

Posts: 2

Participants: 2

Read full topic

@uwe_keim wrote:

On the /admin/upgrade/ page, when clicking the “Processes” tab, I get the following error in the Google Chrome console:

VM176:1 GET https://entwicklergate.de/admin/docker/ps 500 ()
(anonymous) @ VM176:1
send @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
ajax @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
(anonymous) @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22
k @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
L @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
_makeRequest @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22
(anonymous) @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22
k @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
L @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
request @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22
n @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22
refresh @ docker-manager-app-0a56d906a59c60abc96e07b2366723947c14402527d1be5505b557e7caf7bb12.js:1
a @ docker-manager-app-0a56d906a59c60abc96e07b2366723947c14402527d1be5505b557e7caf7bb12.js:1
deserialize @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:11
v @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:20
runSharedModelHook @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
getModel @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
(anonymous) @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:20
O @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
C @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
E @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
invoke @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
flush @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
flush @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
end @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
run @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
join @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
l.join @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:10
(anonymous) @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:14
d @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:9
handleEvent @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:14
e.default.n.Mixin.create.u.handleEvent @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:14
_bubbleEvent @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:14
(anonymous) @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:14
dispatch @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:4
g.handle @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:1234:

And:

VM98:27 Error while processing route: processes Request was rejected due to server error Error: Request was rejected due to server error
    at p.n (https://entwicklergate.de/assets/docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22:17893)
    at new p (https://entwicklergate.de/assets/docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22:18532)
    at i.handleResponse (https://entwicklergate.de/assets/docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22:24458)
    at Object.e.error (https://entwicklergate.de/assets/docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22:22249)
    at l (https://entwicklergate.de/assets/docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:3:29067)
    at Object.fireWith [as rejectWith] (https://entwicklergate.de/assets/docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:3:29838)
    at r (https://entwicklergate.de/assets/docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5:1803)
    at XMLHttpRequest.<anonymous> (https://entwicklergate.de/assets/docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5:6638)
window.console.error @ VM98:27
h @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:11
error @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:12
v @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:11
p @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:20
trigger @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
(anonymous) @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:20
O @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
C @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
E @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
b @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
invoke @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
flush @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
flush @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
end @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
run @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
join @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
l.join @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:10
e.error @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22
l @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:3
fireWith @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:3
r @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
(anonymous) @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
XMLHttpRequest.send (async)
(anonymous) @ VM176:1
send @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
ajax @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
(anonymous) @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22
k @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
L @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
_makeRequest @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22
(anonymous) @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22
k @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
L @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
request @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22
n @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22
refresh @ docker-manager-app-0a56d906a59c60abc96e07b2366723947c14402527d1be5505b557e7caf7bb12.js:1
a @ docker-manager-app-0a56d906a59c60abc96e07b2366723947c14402527d1be5505b557e7caf7bb12.js:1
deserialize @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:11
v @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:20
runSharedModelHook @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
getModel @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
(anonymous) @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:20
O @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
C @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
E @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
invoke @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
flush @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
flush @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
end @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
run @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
join @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
l.join @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:10
(anonymous) @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:14
d @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:9
handleEvent @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:14
e.default.n.Mixin.create.u.handleEvent @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:14
_bubbleEvent @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:14
(anonymous) @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:14
dispatch @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:4
g.handle @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:1234:

And:

VM98:27 Error: Request was rejected due to server error
    at p.n (docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22)
    at new p (docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22)
    at i.handleResponse (docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22)
    at Object.e.error (docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22)
    at l (docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:3)
    at Object.fireWith [as rejectWith] (docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:3)
    at r (docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5)
    at XMLHttpRequest.<anonymous> (docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5)
window.console.error @ VM98:27
a @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:9
o @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:9
r @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:12
trigger @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
(anonymous) @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
invoke @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
flush @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
flush @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
end @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
run @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
join @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
l.join @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:10
e.error @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22
l @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:3
fireWith @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:3
r @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
(anonymous) @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
XMLHttpRequest.send (async)
(anonymous) @ VM176:1
send @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
ajax @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
(anonymous) @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22
k @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
L @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
_makeRequest @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22
(anonymous) @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22
k @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
L @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
request @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22
n @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:22
refresh @ docker-manager-app-0a56d906a59c60abc96e07b2366723947c14402527d1be5505b557e7caf7bb12.js:1
a @ docker-manager-app-0a56d906a59c60abc96e07b2366723947c14402527d1be5505b557e7caf7bb12.js:1
deserialize @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:11
v @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:20
runSharedModelHook @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
getModel @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
(anonymous) @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:20
O @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
C @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
E @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:21
invoke @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
flush @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
flush @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
end @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
run @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
join @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:5
l.join @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:10
(anonymous) @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:14
d @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:9
handleEvent @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:14
e.default.n.Mixin.create.u.handleEvent @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:14
_bubbleEvent @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:14
(anonymous) @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:14
dispatch @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:4
g.handle @ docker-manager-vendor-69993a285f235a9550dea5fbb48df8eb27cc48ffb65d68a942744a95ce673fb8.js:1234:

On the server logs, I see nothing special, just the errors reported here.

The “Processes” tab is empty after this error, no content.

Posts: 2

Participants: 2

Read full topic

@HAWK wrote:

Continuing the discussion from Advertising Plugin for Discourse - Serve Ads on your Discourse Forum (Official Endorsed):

Interesting question.

The community manager side of me says that it would a case-by-case thing. In some communities I’d expect to see ads and therefore wouldn’t be bothered, in others perhaps not. (I don’t use an ad blocker.)

I’d also be skeptical of the kinds of ads and how they were introduced. When we introduced them on the forums when I was at SitePoint we managed the communication ok but the ads weren’t great and there was a backlash. They weren’t relevant in the context of the community.

I also know of organisations that are seeing a very serious drop in ad revenue and are having to find other ways to generate income. That implies that something isn’t working – I don’t know how much of that is people choosing not to visit because of the UX or whether it can be attributed to ad blockers.

Posts: 1

Participants: 1

Read full topic

@strategy_sprints wrote:

hello, client just told me the twitter sign-up does not work!
please help…

Posts: 2

Participants: 2

Read full topic

@meglio wrote:

Any global statistics on how the number of pageviews correlate to the earnings from ads shown? Will it make any sense to display advertisements for 200k pageviews / month, or will it bring just cents / a few dollars per month (in which a case it’s not worth the effort)?

Also, @HAWK, since you know lots about communities, how much showing ads will affect user experience in an online community? Is it important to make it ads-free for logged-in users? And any other advice is very appreciated.

Posts: 2

Participants: 1

Read full topic

@calavera wrote:

Hello folks!

I am a new member here. I am also new on discourse. I bought a server with installed discourse. Because of send out mail problem I can not invite new members. I see user and system on the users page. I can not manage system user. And there is no email defined. Fot eh second user is user. It has mail defined user@example.com. I can not change it. It asks need to sonfirm the sending mail activations etc. How can I manage these all?

Posts: 3

Participants: 3

Read full topic

@schungx wrote:

On and off I’ve seen posters asking about how to use Discourse as a support (or ticketing) platform. I’d like to share my setup here for those with similar needs.

Background

You run/work for an organization. You need to provide pre-sales, after-sales, technical and/or one-on-one support to your customers, agents, distributors and/or partners (which organization doesn’t?).

What is Discourse

Discourse is primarily a forums software, geared towards public, open conversations of various topics. It is incredibly modern and performant, runs at lightning speed, and you hare a lot of flexibility in how to setup your environment.

You want to see if you can coerce this fabulous piece of software to do what it isn’t originally designed to do.

What You Want

Your customers will open issues, or help tickets, on the system. They either open it under their own folder/category, or you can have some systematic/manual way of reclassifying them later on.

There may be sensitive things discussed, so by default you don’t want each customer to be able to see the issues or inquiries raised by other customers. In other words, each customer conversation should be private.

You want your support teams to each work on their allocated areas/categories. In other words, your teams should be able to see a list of all the support requests in their own categories, and be able to easily sort through them, manage them and follow-up on them without a lot of searching and filtering.

Some information may be sensitive, so each team’s area may be separated from another team’s, so they cannot view each other’s data.

Your Problem

1. Some core features are geared towards an open community, and may not be relevant to a private support forum, for example the badges.

2. You looked at the security/permissions system and you don’t find what you want: basically pure Create and Create/Reply permissions do not exist.

3. Your customers don’t really want to go through the hassle of creating an account on your forum just to ask a support question. But you also don’t want to open up your forum to the public and have silly posters come in and waste your time.

   You want a way to detail with these one-off inquiries quickly, but leave open the possibility of maintaining a long-term relationship with certain customers.

4. A lot of your customers work with emails, and you want to reply to them via email, but you also want your support teams to be able to manage these requests quickly and easily without digging through piles of email.

How it Will Work

• You have a bunch of email addresses published for customers to send inquiries. For example, you may have an email address called wonderful_product@support.example.com for people to send questions regarding the Wonderful Product product line of your company.

• A customer sends an email to this address.

• The email is automatically turned into a topic in the appropriate Wonderful Product category.

• A staged user (say, MrFoo) with no rights is created on the system to track all the requests sent by that email.

• You internal team support staff, under the group WonderfulProductTeam, which has Reply/See permission on the Wonderful Product category, sees the topic and post replies.

• Each reply turns into a reply email back to the originating customer.

• The customer feels that his/her email is being replied personally.

• The customer has no way to see the emails of any other customer on the system. Meanwhile, the WonderProductTeam sees all the emails sent to wonderful_product@support.example.com all together in a single list.

• You find that user MrFoo has been a great contributor and would actually like to involve him into your support pipeline. Go to his user profile and send him an invitation to become a member. Put him in an appropriate Group with appropriate access rights.

• MrFoo, now an valued member of your support organizatio, logs in and sees all his previous emails neatly under his account.

Setup Instructions

Basic Discourse setup

• Turn off Settings|Basic Setup|enable badges because badges are not awarded for posts in non-Everyone categories, which most of your categories will probably be. They will just confuse your users. Keep it if you have large, open-to-all-users categories.

• Turn on Settings|Basic Setup|enable whispers if you want whispers. This may be useful when you have many moderators.

• Turn on Settings|Login|invite only unless you want to allow customers to self-register themselves. You may not want the hassle.

• Turn on Settings|Login|login required because you are not running a public forum.

• Set Settings|Trust Levels|default trust level to 0 to make sure staged users created via email is level 0.

• Set Settings|Trust Levels|default invitee trust level to 1 to make sure that the users you actually want to be on the system are level 1.

• Turn on Settings|Email|enable staged users

• (Optional) Settings|Login|must approve users may not be necessary if your forum runs on invitation only.

• (Optional) Set Settings|Posting|approve new topics unless trust level to 1 so that your staged users (which will be created as level 0) will have their topics pending staff approval.

  Note: As of 1.9.0beta13 this doesn’t work because topic approvals by-pass all staged users. This may be corrected in the future.

• Turn off SSO because you obviously don’t want any unknown persons to sign into your forum.

Set Up the Appropriate Email Addresses

• On your email system, setup a MASTER mail-in email account, for example: master@support.example.com.

• For each area/team/category, create a new, specific email account, for example: wonderful_product@support.example.com.

• FORWARD all emails to those specific accounts to the MASTER email account. For example, an automatic forwarding should be created to forward all mail received by wonderful_product@support.example.com to master@support.example.com.

Turn on email in

• Turn on Settings|Email|reply by email enabled

• Turn on Settings|Email|email in

• Turn on Settings|Email|pop3 polling enabled

• (Optional) Turn on Settings|Email|pop3 polling ssl if your POP3 email server requires SSL.

• (Optional) Turn on Settings|Email|pop3 polling openssl verify if your POP3 server uses SSL.

• Turn on Settings|Email|reply by email enabled

• Set Settings|Email|reply by email address to the MASTER email account in the section above (for example: master@support.example.com).

• (IMPORTANT) If your email system does NOT support the + feature, then turn off Settings|Email|find related post with key. This will use each email’s In Reply To header to find the correct thread, with certain security considerations.

• Set Settings|Email|pop3 polling host, pop3 polling port, pop3 polling username, pop3 polling password for your POP3 email server. The username and password should be for the MASTER email address.

• Set Settings|Email|email in min trust to 0 because your staged users will be created with trust level 0.

• Set Settings|Email|maximum staged users per email to a small number unless you have a good reason to allow creating large number of staged users from an email.

• Set up suspected SPAM email domains in Settings|Login|email domains blacklist. This prevents emails from unwanted domains from creating staged users in your forum and littering them with SPAM topics.

  Notice that regexp expressions work in this, EXCEPT for the dot (.). You do NOT need to escape the dot because it will be automatically escaped. In other words, \d+\d\d\d.\w+ will actually be \d+\d\d\d\.\w+$ and will match any domain that is a string of digits more than 3 long plus a root domain (.com, .org etc.).

• Set up suspected SPAM email subjects in Settings|Email|ignore by title. This prevents emails with suspicious subjects from creating topics.

  Notice that regexp expressions work in this. Wrap your entries with \b if you want to match whole words in English. BEWARE, \b works for English language only!!!

Attachments

• Add allowed attachment formats in Settings|Files|authorized extensions because customers who requires support will typically send in attachments other than photos (maybe a PDF file, an Excel spreadsheet, a CAD drawing, an error log file, or a zip file).

• Set Settings|Files|max attachment size kb large enough so that reasonable attachments do not bounce. Typically 1MB to 2MB is enough.

Set Up Email Info in Categories

• For each category that will receive emails from outside, set Custom incoming email address (in the Settings of the Edit dialog of that particular category) to the appropriate email account.

  For example, in the Wonderful Product category, press Edit and go to the Settings tab. Custom incoming email address should be set to wonderful_product@support.example.com. Then, all emails sent to wonderful_product@support.example.com will be created as topics in this category.

Set Up Security in Categories

• Remove the Everyone group from each category’s access list.
• Use Groups to manage access to each category.

If You Have a Multi-Lingual (Worldwide ) Customer Base

• Turn on Settings|Basic Setup|allow user locale

• Turn on Settings|Basic Setup|set locale from accept language header

• Consider the discourse-translator plugin

• If you have Chinese users, please make sure to search meta for the settings required to support Chinese language posts.

  Notice that it doesn’t work for redemption from invitations as of 1.9.0beta13.

Posts: 1

Participants: 1

Read full topic

@mcwumbly wrote:

When a user has been deactivated, they can no longer be @mentioned in a post (the pop-up does not help with auto-completion). This makes sense to a large degree, as that user will not be notified. (That said, it could be argued that it’s still be nice to be able to reference them easily via a mention and perhaps find some other way to indicate they are no longer active.)

But in the case of search I have found myself often wishing I could more easily find posts from users who have been deactivated.

Search does properly filter to posts by a deactivated user if you type the user name perfectly, but it’s much more difficult to do that without auto-complete.

I think it’d make sense to have search assist with autocompletion here by default (a refinement would be that it only works if the user has made any posts).

Posts: 1

Participants: 1

Read full topic

@cashable wrote:

What would you like done?

I have discourse set up, but I am having major issues getting a vbulletin database moved over. I have tried following the script but just get errors, so I could use some help.

When do you need it done?

Soon?

It would be great if someone could help me out on this. I would be happy to pay, just let me know what you are expecting. Really looking forward to using discourse!!

Forum info: Threads 59,797 Posts 1,129,529 Members 12,352

Posts: 1

Participants: 1

Read full topic

@Miszo wrote:

Hi! First, thank you for creating such a great software and community!

But to the point: When I type (and it’s the way everyone in Poland types it) Polish diacritics “ś” on my keyboard by pressing right alt + s, search popup pops up, capturing the text that follows. This isn’t a big problem, but it’s very annoying. Is there a way to change it or turn it off ?

Posts: 13

Participants: 6

Read full topic