Am I doing something wrong or is there anything else to do to make it disappear from the site?
We don’t want to use it as it is and will find a way to use for our users’ benefit but not as it is right now.
Also, I have changed the icon removing the robot head and replacing it with an information icon (“i” inside a circle) and this appears in the messages sent but the icon in the user menu still shows as a robot head. Can this be changed?
Weirdly, on my site when I insert an emoji, I am unable to click on the menu to switch to different sections of the picker. I can scroll through and see that e.g. the tree turns green when I am looking at nature, but I can’t click on the tree to take me straight there.
I am posting this in support because I don’t think it’s a bug - the menu works here on meta. There must be something conflicting with my customizations. Any ideas where to look?
I currently have my domain from Namecheap and hosting from Scaleway. I was able to do the installation and Discourse is perfectly working on scaleway’s server IP. I think I got confused on the hostname/domain part and wasn’t able to set it up properly, how can I link a namecheap domain to my VPS server on scaleway? is it through DNS? Thanks!
I think I misunderstood the "Hostname for your Discourse? [discourse.example.com]: " and put my domain name instead.
I’m not well-versed in these queries but I have been using this (and others with different post requirements) query I got from the Discourse meta site to reward posting to a particular category.
SELECT P.user_id, MIN(P.created_at) granted_at, MAX(P.id) post_id
FROM badge_posts P JOIN topics T ON T.id = P.topic_id
WHERE T.category_id IN (SELECT id FROM categories WHERE id = 56 OR parent_category_id = 6)
AND P.user_id >= 0 GROUP BY P.user_id HAVING COUNT(*) >= 1
I was wondering how exactly I could change this to:
A) Require new TOPICS, not just posts in the category and
B) How I could include subcategories. So not just category 6, but also subcategories 7,8, and 9.
I added this poll to my instance, but the question doesn’t appear. How can I create a poll that looks more intuitive to users?
People had voted but it displayed zero voters.
My use case is that I’d like to identify posts that were judged most valuable by the community, so I can use them the basis for articles I write for readers of my email newsletter who are not on the forum.
I typically upgrade Discourse installs once per year during downtime for my site over the December holidays. I have had version 1.6.10 since last January. Recently I was forced to move servers on DigitalOcean. I went the long route by moving a snapshot of the entire install where I ran into various problems. I then started a new install with the intention to restore from a backup.
While trying to rebuild version 1.6.10 with my old app.yml I run into the following problem:
Here is the link to the json gem versions. Is there a solution to override this Make sure that gem install json -v '1.8.3' succeeds before bundling issue without having to upgrade Discourse versions?
I am dutifully equipped with snapshots and backups if someone has a different idea to help get my install back up and running.
I noticed some interesting differences in behavior between navigating around Discourse with a topic draft editor expanded vs minimized.
If the topic editor is minimized, any time you navigate from a topic to a category, you get prompted with the “abandon post” dialog. If the editor is fully expanded and you navigate in the same manner, the dialog does not appear.
Is this behavior intentional or a bug? The main reason I could see this as intentional is to remind you that you have a draft it progress, but it seems odd to bring up the “abandon post” dialog simply upon navigation. It feels like that dialog should be reserved for when you click “New Topic.” If the main idea was to remind the user, it seems more appropriate to either automatically expand a minimized draft or display some type of reminder dialog.
Let me know what you think or if I need to be any clearer in what I’m trying to explain!
It would be nice to have an extra check box in the group options to set a group as a users’ primary group if and only if they do not already have one.
Currently, users are primarily grouped in whatever group they join last with the automatic setting applied. While this is great for groups like staff or site leaders, there are are lesser groups that it would be handy to set as a user’s primary group if and only if they don’t already have one set. This would also make it much easier to distribute flair without potential unintended consequences.
Your Discourse installation is out of date. Click here to upgrade.
Installed Latest Version v1.9.0.beta12 +52 1.9.0.beta13 Updates are available. Please upgrade!
yet, on /admin/upgrade everything is already “Up to date”:
Repository Name Status
discourse (0a31190) Up to date
discourse-details Up to date
discourse-narrative-bot Up to date
discourse-nginx-performance-report Up to date
discourse-presence Up to date
docker_manager (7b09885) Up to date
lazyYT Up to date
poll Up to date
Result: The topic appears immediately without requiring approval
I think staged users and email in just by-passes too many of the regular posting pipeline that it needs some serious review. It feels like an “add-on”.
It happens again here on Discourse, on my forum that is still in version 1.9.0.beta12 +21, updated after the fix made by @eviltrout, it continues to work.
The problem is on Firefox 56.0.1, no issue with Chrome.
I’m trying to install discourse on my server with Ubuntu Server 16.04, where I’m already running a docker compose file with nginx. All containers in my docker file are on a separate network. I followed this guide mostly. I succesfully rebuild the app and setup nginx with the following setup:
With this I cannot access talk.webserver.nl. I noticed it’s trying to call /var/discourse/shared/standalone/nginx.http.sock so I decided to add that to my nginx volumes. That didn’t work either, so it’s probably not necessary to have this in my volumes at all? I have no idea how the unix reference works and I can’t find anything on it.
When I shell access nginx I can ping to all my other containers but I’m not able to ping to the discourse container. Not sure if that has anything to do with it. What can I do to debug this?
It looks like a bug that triggers when posts are moved from one topic to another and then adds (or already exists) a solution.
I can easily reproduce it on my forum, but since I can not check here on Meta, I put it in the #support category waiting for verification by other users
My setup:
solved enabled, yes
allow solved on all topics, no
accept all solutions trust level, TL3
empty box on unsolved, no
solved quote length, 300 (default)
solved topics auto close hours, 120 hours
Step to reproduce:
user A open a topic in the support category (solutions enabled)
user B write a reply (with a link to a guide/another topic)
user A follow the guide, then instead of answering the topic he opened, he answers on the topic of the guide
as an administrator I select the A user’s reply and move it to the original topic and mark user B post as a solution
user B (or anyway the last user who wrote that topic) disappears from the topic list
