@Conor wrote:
Would it be possible to set a custom user card badge from the admin panel? Currently, it looks like the only way is to award a badge to get user card badges. It would be nice to allow staff to set custom user card badges using the admin panel, like titles can be.
Posts: 2
Participants: 2
@pocock wrote:
I recently went to a large free software event where I met a wonderful community and had a great time.
Afterwards, I tried to follow up on some discussions by posting some resources to the community's mailing list. From there I was redirected to a Discourse site which they had recently set up. Most settings were still in their default state.
I copied my emails from the mailing list over to new topics on the site and encountered a range of problems:
- one of the messages sent via the email interface has never appeared yet, with no feedback either, leaving me with a lack of confidence in the Discourse concept
- another attempt to submit an email resulted in a reply by email "Your account does not have the required trust level to post new topics to this email address. If you believe this is an error, contact a staff member."
- the first time I copied an email from the old mailing list to Discourse via the web interface, I spent a few minutes adapting all the links that I had cited into the Discourse markup. When I tried to submit the post, like a nasty little dictator, Discourse replied that it doesn't like more than 2 links in a post. I think this is the default from site_settings.yml
newuser_max_links- when I tried to copy the next message from the mailing list, Discourse again became a dictator telling me that I have to wait 1 minute before I could submit it.
- trying to copy another message from the mailing list, Discourse complained that it didn't like the URL in the link (there was only one link in this message)
- after all that, a big nasty message appeared telling me "Your post was flagged as spam: the community feels it is an advertisement, something that is overly promotional in nature instead of being useful or relevant to the topic as expected."
I understand there are spammers out there, but
- the free software community should not risk insulting and wasting the time of legitimate volunteers and contributors as these are real people
- site admins who successfully ran a Mailman list may not expect their users to be treated so badly by the default configuration
- a user who has previously participated in other online communities through mailing lists and then uses Discourse for the first time and encounters all of these rules will be particularly irked by it
- censorship is, in principle, wrong and has a corrosive effect on communities. If you imagine two communities, run running Mailman and the other running a censored platform for a period of 3 years, which one will have more contributors and more diversity of ideas at the end of that period?
- most of these restrictions are just security theater anyway. E.g. the a spammer may be quite happy only posting 1 link. Some spammers are simply happy to have their brand name appearing in subject lines, with no links at all. Spammers are paid to work around these things but volunteers lose valuable time trying to change their writing style to get under the radar of this censorship.
I'd like to share a few constructive suggestions in the hope that Discourse can treat people with more respect:
- never tell the user they might be a spammer, just tell them the message is being held for moderation
- don't give the users orders, e.g. telling them to wait or telling them to modify their messages to remove links or whatever, just put the message into the moderation queue and let the moderator give personal feedback if the message is far outside his expectations
- use other default methods, such as a captcha or moderation of the first post, to filter out spammers. Once the user has crossed that one-time hurdle, let people contribute freely without imposing on them.
- the ability for other community members to mark a message as spam is dangerous as different people have different definitions of spam and it can have an anti-social impact. It is better to send somebody a polite personal message telling them why their content is off-topic rather than an anonymous insult. If people mark a message as spam, then at the very minimum make them give a reason and show these reasons to the poster.
- tell people at the sign-up screen that their first post will be moderated, so they don't lose time writing a message and then get taken by surprise by this policy.
- think about it like joining a Mailman list: if the effort for the user or moderator on Discourse is more than it would have been in Mailman, then the user who used mailing lists before is going to feel like they are taking a step backwards and may be disappointed by their first impression of Discourse and the community that is using it.
Posts: 1
Participants: 1
@pocock wrote:
The sign-up process for Discourse is more complicated than the sign-up process for a Mailman list.
It has been said many times that for every extra field or step people must take completing a form, half the people who start the form will not get to the end of it.
A Mailman list only asks somebody for their email address and then it auto-generates their password. There is no need to choose a username or fill in any other fields.
For communities who run Discourse but want to offer a Mailman-like mailing list experience, users have to manually go into the preferences to enable the email mode of Discourse.
It would be nice to have a single sign-up page where people only see the following:
- enter your email address
- choose the sections you want to be subscribed to (much like choosing which lists to join on a Mailman server)
and everything else will automatically be set up in Discourse email-mode.
Posts: 1
Participants: 1
@pocock wrote:
The default installation of Discourse requires users to create usernames and it also offers private messaging between users. Users are not able to see the real email addresses of other users.
In traditional mailing lists, used by many free software communities, the users do see the real email addresses and they can reply personally and privately to other users when they believe it is appropriate.
With the private messaging system in Discourse, people run the risk that all their messages are seen by the Discourse administrator and anybody who hacks the Discourse installation.
While most system administrators are good people, there have been a number of cases where somebody in a leadership position in a volunteer community was subsequently found to be the subject of concern. To give an example, a senior developer left the Tor and Debian projects in 2016, the case is very widely documented so I won't repeat it here. These things happen from time to time in any organization.
Therefore, organizations that simply don't want to be too dependent on Discourse and their system administrators may not want the private messaging facility and may prefer to simply give users the option to communicate directly with each other by email.
People also have the inconvenience that they can't add a contact to their address book if they don't have a single email address for that person.
Posts: 3
Participants: 2
@nmagee wrote:
We have a fairly new installation with only a couple dozen posts, but our inline click counters are not appearing. I have not modified any of the CSS at all, but wasn't sure if they only show up after a certain base number has been reached? Or if there's a setting that I'm missing?
Posts: 1
Participants: 1
@wiliamjoaquim wrote:
I'm trying to install ssl by following this tutorial
But during rebuild of
./launcher rebuild appthe following error occurs at the end of the rebuildFAILED -------------------- Pups::ExecError: cd /var/www/discourse && bash -c "ln -s /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr}.log /var/www/discourse/log" failed with return #<Process::Status: pid 18775 exit 1> Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn' exec failed with the params {"cd"=>"$home", "hook"=>"code", "cmd"=>["git reset --hard", "git clean -f", "git remote set-branches --add origin master", "git pull", "git fetch origin $version", "git checkout $version", "mkdir -p tmp/pids", "mkdir -p tmp/sockets", "touch tmp/.gitkeep", "mkdir -p /shared/log/rails", "bash -c \"touch -a /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr}.log\"", "bash -c \"ln -s /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr}.log $home/log\"", "bash -c \"mkdir -p /shared/{uploads,backups}\"", "bash -c \"ln -s /shared/{uploads,backups} $home/public\"", "chown -R discourse:www-data /shared/log/rails /shared/uploads /shared/backups"]} 79ac568b42218337eeca4810bb478054b34f762f73ee4b20c1d7e5571520387e ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than oneIs all set up correctly, what can it be?
Posts: 1
Participants: 1
@aspn3 wrote:
I am running a development version of Discourse because I am writing a plugin and I cannot afford another droplet for production. Basically, I need to edit the SMTP details in order for the plugin to be able to send mail, because my local server doesn't support sendmail.
Since it isn't Docker, I have no containers directory, which means I cannot find the app.yml. I have looked in
~/discourse/config/but there is no app.yml there.I realize you don't usually support development versions, but it is your software and I think you should help given that I am just trying to make my plugin work without messing up my production installation. Thank you for your consideration.
Posts: 6
Participants: 3
@d00137007 wrote:
Hi,
I followed https://www.digitalocean.com/community/tutorials/how-to-use-the-discourse-one-click-application-on-digitalocean, but I never got the email at the end. I checked the logs and it says "Error connecting to redis on localhost :6379. Any idea? I can't figure it out.
Thanks.
Posts: 4
Participants: 3
@ashledombos wrote:
Hello,
This is related to Embedded comments.
I have difficulties to understand how the importation/parsing of the page or blog post is working.
The topic content (first post), imported from RSS seems OK after several test. It seems that the content imported from RSS is the section between the XML tags<description></description>.When I click «vîew full post», the rendering is not fine. It seems to be done from the HTML of the original page rather than RSS feed xml content. The result is, in my case, some tags are missing (espectially
<br />) and Images are either incorrectly imported (for instance the url of an image is http://mysite.commyimage.jpg instead of http://mysite.com/myimage.jpg — precisely:missing slash with relative path imported images) either not imported at all (for images that are like this<img src='data:image/jpeg;base64,/9j/4AAQSkZJRgABAQEAYABgA…' height='400' width='640' alt='Boot' class='adapt-img ' onmousedown='adaptImgFix(this)'/>. )Is it something that happens to other? How can i troubleshoot importation of content, and improve it? Can't «view full post» being rendered from the
<content:encoded></content:encoded>RSS XML tags, instead of HTML (because in my case, rendered RSS is neater)?
Posts: 2
Participants: 1
@sjmscott wrote:
Continuing the discussion from JSON API for Recent Popular Topics (Similar to the Email Digest):
Some of the tech blogs I read like Daring Fireball are raving about the new JSON Feed. I can't say that I truly understand what is capable here, but it would be cool to pull some topics out of Discourse based on a tag, user, or category and format it for a website. For example, I'm about to post every Monday for the next 12 weeks on a particular topic. I would love for those 12 topics to appear on a well formatted page.
I haven't dug into the Discourse JSON feed other than clicking on this link.
Has anyone else seen the new JSON Feed and thought about how we might be able to leverage this new tool?
Posts: 2
Participants: 2
@deviant wrote:
Elo Discoursers..
I have Discourse and Wordpress running on the same host, except that Discourse is inside a Docker container with Nginx setup "external" to docker using a reverse-proxy.
Installed wp-discourse on my Wordpress site, but it will not connect to Discourse.
I do have the API key from my Discourse instance and the correct URL entered into Wordpress, but when I hit Save ...
- IceCat browser says:
Secure Connection FailedChromium says:
No data receivedNginx log indicates:
SSL_shutdown() failed (SSL: error:140E0197:SSL routines:SSL_shutdown:shutdown while in init) while SSL handshakingDiscourse is installed using the Docker image. In my app.yml I have:
- "templates/web.socketed.template.yml".. so the Nginx conf has:
location / { proxy_pass http://unix:/var/discourse/shared/standalone/nginx.http.sock:; proxy_set_header Host $http_host; proxy_http_version 1.1; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto https; }I am sure this is an SSL issue. The Letsencrypt certs are installed and configured in the "exernal" host through Nginx:
ssl_certificate /etc/letsencrypt/live/forum.librenet.co.za/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/forum.librenet.co.za/privkey.pem;I have no idea how to troubleshoot or fix this. Where could the problem be? Is it the Location ("proxy_pass") directive?
Any input will be appreciated.
Posts: 3
Participants: 2
@Stefan_Fairphone wrote:
Hey everybody,
I really like the way Github handles notifications: You click on the notifications icon
and get a list of notifications. However the
stays until you've read or dismissed all notifications.
In contrast, when I click on the notification count in Discourse, the
/
/ etc. disappears at once. When I click on one of the notifications, the notification count is gone, and I might miss notifications that are buried in the "view older notifications..." screen.
What do you think? Can this behaviour be improved?
Stefan
Posts: 3
Participants: 2
@Stranik wrote:
I try to bring out (for testing) posts that are comments.
import { withPluginApi } from 'discourse/lib/plugin-api'; import RawHtml from 'discourse/widgets/raw-html'; //TABLE posts: reply_to_post_number integer function attachSignature(api) { api.includePostAttributes('reply_to_post_number'); api.decorateWidget('post-contents:after-cooked', dec => { const attrs = dec.attrs; if (Ember.isEmpty(attrs.reply_to_post_number)) { return; } const currentUser = api.getCurrentUser(); if (currentUser) { return new RawHtml({html: `<div class='reply-comm'>This is a comment on the number: ${attrs.reply_to_post_number}</div>`}); } }); }You can tell whether this code is written correctly?
Or I need to add a condition:
if reply_to_post_number > 1 (or 0, Null ...)Continuation: Adding to the comment css tags
Posts: 1
Participants: 1
@leonekmi wrote:
I have installed Discourse with this method
https://blog.imirhil.fr/2016/09/30/discourse-docker.htmlAnd i cannot make it work because the 4 sockets doesn't generate.
2017/05/20 10:31:20 [notice] 12544#0: signal process started
2017/05/20 10:31:31 [crit] 12584#0: *1 connect() to unix:/srv/www/discourse/tmp/sockets/thin.0.sock failed (2: No such file or directory) while connecting to upstream, client: 77.201.220.206, server: report.twittolabel.tech, request: "GET / HTTP/1.1", upstream: "http://unix:/srv/www/discourse/tmp/sockets/thin.0.sock:/", host: "report.twittolabel.tech"
2017/05/20 10:31:31 [crit] 12584#0: *1 connect() to unix:/srv/www/discourse/tmp/sockets/thin.1.sock failed (2: No such file or directory) while connecting to upstream, client: 77.201.220.206, server: report.twittolabel.tech, request: "GET / HTTP/1.1", upstream: "http://unix:/srv/www/discourse/tmp/sockets/thin.1.sock:/", host: "report.twittolabel.tech"
2017/05/20 10:31:31 [crit] 12584#0: *1 connect() to unix:/srv/www/discourse/tmp/sockets/thin.2.sock failed (2: No such file or directory) while connecting to upstream, client: 77.201.220.206, server: report.twittolabel.tech, request: "GET / HTTP/1.1", upstream: "http://unix:/srv/www/discourse/tmp/sockets/thin.2.sock:/", host: "report.twittolabel.tech"
2017/05/20 10:31:31 [crit] 12584#0: *1 connect() to unix:/srv/www/discourse/tmp/sockets/thin.3.sock failed (2: No such file or directory) while connecting to upstream, client: 77.201.220.206, server: report.twittolabel.tech, request: "GET / HTTP/1.1", upstream: "http://unix:/srv/www/discourse/tmp/sockets/thin.3.sock:/", host: "report.twittolabel.tech"
Nginx logI cannot make this work and i cannot find any option in the config/ folder that can help me.
Notice : I have no knowledge in Ruby (on Rails too)
Posts: 3
Participants: 3
@David_Taylor wrote:
In the interest of tracking user interaction with
@discobot, here's a data explorer query which lists each user the bot has interacted with, and the current track/state.If anyone can think of a way to actually show a percentage progress through the track that would be awesome! But as far as I can see there's no info about the sequence of
statesin the databaseTo use these queries, download the one you want, and import into the Data Explorer Plugin
All User Interactions
all-narrative-bot-interactions.dcquery.json (1.6 KB)
Shows a list of all users that have interacted with
@discobotin the last year (configurable) and shows their current state in the track:Summary of Interactions
narrative-bot-summary.dcquery.json (1.6 KB)
Shows all interactions with discobot in the last year (configurable), grouped by
current_state. This can be used to see whichstateusers got stuck on. Results will look something like this:
I've made this post a wiki, so others can add any@discobotrelated queries they come up with
Posts: 4
Participants: 2
@markaodonnell wrote:
Hi,
Has anyone been able to create infusionsoft actions, with emails, etc with Discourse new user registrations?
Posts: 1
Participants: 1
@Simon_Cossar wrote:
On this forum I am watching the support/wordpress category. A few times, I've noticed topics in that category for which I haven't received notifications. Here's an example of one: https://meta.discourse.org/t/wp-discourse-sso-continuity-issue/62897
Looking at the edit history of that topic, it has been recategorized from extras to wordpress. Possibly this is a regression from https://meta.discourse.org/t/category-watch-preferences-not-honored-on-recategorization/19441/7?u=simon_cossar
Posts: 5
Participants: 4
@averymd wrote:
When I started my Discourse site a few years ago, I was overly ambitious and split web, data, and redis into three containers on three DigitalOcean VPSes. They're using
linkto communicate on a private network and SSL is in place. It's a standard multi-container setup, per the instructions + forum posts.I'd like to merge these now into a single standalone container while retaining all data. Is this possible?
Posts: 2
Participants: 2
and get a list of notifications. However the 
stays until you've read or dismissed all notifications. 
/ 
/ etc. disappears at once. When I click on one of the notifications, the notification count is gone, and I might miss notifications that are buried in the "view older notifications..." screen.
