Expected: all topics which are private to the joined group should be displayed in the list Actual: topics not displayed
Refreshing the page causes the topics to be displayed. But this isn't ideal, as users won't know to do this and will be confused. Have seen this problem on iPad and desktop (not yet tested on mobile)
I think variations of this have been discussed, but I wasn't able to see something quite as exact as this.
Basically in mini search (upper right) as I type, results start popping up. I'd like to see that same feature when I search in "full-screen" mode ie: https://meta.discourse.org/search
I have to press enter on the full page search before results pop up. I'm not just being lazy, I'm trying to upplay the wiki and content aspects of discourse. I think it'd make an excellent resource for documentation, etc for small teams.
In several cases I have been interested in what actions staff took on a specific user. Currently there is no (obvious) way to see what these actions were, except for going to the staff action log and clicking on the name of the relevant user.
Adding a button on the user admin page, that links to the staff action log, and targets the relevant user, would make it a lot easier for admins to see what actions have occurred on a specific user.
Gary and SpongeBob are going on an adventure. They are expected to arrive by the end of the hour.
Sometext here...
Mr. Crabs is upset that Spongebob may be absent from work.
It would be nice if the number of topics changed dynamically. I just want to create these types of links on my website to categories that the users can click to take them to the message board. The same way that you would have an ad, I want to spread these throughout app.
Is there any feature like this or do I have to pull the data and create all of my own CSS?
I've tried a few dozen searches and can't find an answer to this question so hopefully I haven't just done a really poor job of searching.
I have customized the header of my Discourse install with a link to another site. That site is on the same domain but different sub-domain (so blog.example.com vs forum.example.com). I want the link to open in a new tab but no matter what I do it opens in the same tab. If I view the source of the page I can see that the target="_blank" is set on the link but it is being ignored. Is there something in Discourse that it overriding the default HTML link behavior? If so, can it be disabled?
I've read several topics about the "open external urls" setting in the Admin panel, and have already tried it with both logged in and guest users and it does not work for this link at least. I'd prefer a solution that worked even for guest users. Any help is appreciated.
We have an existing rails app on Heroku and we're looking to incorporate a community component.
We were going to build this from scratch but then discovered Discourse and it has all the features we need. The ideal setup would allow each section (main app & community) to access the other's data. That way, we could include components from the community into the main app, and we could also tailor the community section to each user.
Is this type of setup possible? Everything I've read so far talks about installing Discourse as a completely standalone project (or subdomain, separated part of an existing app community.mysite.com).
I ran 'docker save image_id' on one host and proceeded to run 'docker load -i ' on a new host. Unlike the old host, I don't have a /var/discourse/container/.yml file for the loaded image on the new host, so I'm not sure how to go about changing the DISCOURSE_DB_HOST/PASSWORD information for the separate postgres server it will be connecting to. Can someone add some guidance on how I would go about doing this?
I've updated badge descriptions for: Basic, Member, Regular and Leader. The description changes were made under Customize->Text Content for each badge. All description changes were reflected on the Badges page except for the Basic badge. The description remains as the default Discourse description and not what I changed it to for badges.basic_user.description. The same thing applies to the long badges.basic_user.long_description. Again, this is only happening to the Basic badge and not the others. This appears to be a bug, not intended behavior. Can someone confirm?
I would to redirect users that access the discourse site on port http to port https. I have checked force https but that does not seem to be causing a redirect to happen. The SSL termination is being done external to discourse (discourse always listens on 80).
It's essential when using Disocurse as an SSO provider since you need to know the usernames of a user, given their external_id. (And since usernames can change, I don't want to manage storing them in my own database).
Any idea how to make it work? I tried appending .json with no luck.
<%= @topic_one %> by <%= @topic_one_author %>
<%= @topic_five %> by <%= @topic_five_author %>
Which gives me the following results:
"Leave Group" button on /groups page doesn't give any feedback by codinghorror Attachment / Upload email links now throw 404 if not logged in (SSO) by eviltrout
in the configuration file (standalone.yml/data.yml). I can guees what it means through its name. The issue is that my locale is CN-zh or my main language is Chinese (That means the same, lol ) and my setting is the default (pg_catalog.english, never noticed), and my pg text search work just well. So what does that do? I can find nothing useful in this site.
So, what if i change this setting to db_default_text_search_config: "pg_catalog.chinese" or db_default_text_search_config: "pg_catalog.simple". What will happened?
I'm using ruby api to integrate discourse in my website. I'm successfully posting comments for a topic using api, but posted_by is showing as admin user. How can i replace it by logged in user.
In Best Practice: Creating local user guides I mentioned setting a category to "default watched". You do this in admin>>settings (yoursite.com/admin/site_settings/category/all_results?filter=watching) Changing this does not apply retroactively. If you want to make that change apply retroactively you can do so from the CLI:
1) get the category slug from /categories.json (eg "user-guides-and-how-tos" cat id 5) 2) ./launcher enter app, rails c 3) Change the slug in the example below, then paste the script into the console.
# levels: :watching :watching_first_post level = :watching category_slug = "user-guides-and-how-tos" category = Category.find_by_slug(category_slug) group_name = "trust_level_0" # all users group = group = Group.find_by_name(group_name)
Then;
group.users.each do |user|
watched_categories = CategoryUser.lookup(user, level).pluck(:category_id)
CategoryUser.set_notification_level_for_category(user, CategoryUser.notification_levels[level], category.id) unless watched_categories.include?(category.id)
end