following 30 minute configuration guide. Using local postfix MTA. ./launcher mailtest app* works fine. Via discourse itself fails. Was able to login and see the admin/email interface via: ./launcher enter app rake admin:create* Sidekiq errors were "ECONNREFUSED"
admin/email settings: has all the settings filled in correctly, except for a Delivery Method.
Attempts to try a sendmail -i style by not configuring the SMTP_ADDRESS, had a similar effect. the argument of '-i" was there in the webui, but not the method.
tcpdump of the local interface showed mailtest working correctly. discourse itself never even attempted to connect to port 25.
Additionally, having to wait some 5-8 minutes of downtime for a rebuild to configure or change email server settings is unwelcome.
I just checked in a change that adds the class .bookmarked to any bookmarked topics (a bookmarked topic is a topic with 1 or more bookmarks) and the class .liked to topics with liked posts.
Bookmarks are in many ways stronger than likes, when you bookmark a topic you are registering "interest" in a topic.
It works for me but is probably a bad pattern for general consumption. People will be scratching heads wondering why some topics have a yellow underline.
My two questions are:
Do we need special styling for bookmarked topic?
What should that styling look like on the topic list?
I think we need some sort of styling, or a bookmark glyph on bookmarked topics.
I recently noticed the phpBB team released 3.1, which I gather it's release was a long time coming. I am mostly familiar with the platform as an end user. I was wondering if anyone familiar with it had thoughts on the new feature set they are advertising.
Things that stood out to me are a responsive layout, notification system, ajax calls, and a new extension system. The new layout however, (unfortunately) looks pretty much the same, and I haven't seen any more minimalist themes since it is so new. Is this a platform worth checking out?
I like the responsive layout and notification system of Discourse, but I have no experience with the language/framework under the hood which makes me reluctant to use it, along with the more exotic server requirements.
Hello!! I'm new to discourse and host a site using digital ocean. My problem is I wanna edit some file like locales file easily. Any I have know sftp can access remote ssh file like ftp. But it can access that file in /www/ ( it means files that after type ./launcher ssh app) Is anyone know how to do that?
@sam Would you disable English slugfier for topic title totally in Korean language setting? (Better to disable for category URLs by default also, but cat URLs can be changed manually.)
For now, if I make a topic with Korean: "안녕하세요 여러분" → then it will be made with URL /t/topic/192. It's OK.
But if I make a topic with Korean + English: "Interstellar 주인공 이름이 뭐죠?" → then it will be made with URL /t/interstellar/193. It doesn't keep the original meaning well. Worse case, it possibly ruins its original meaning badly.
Also, I think it would be better to keep consistency. All the topics with /t/topic/###, not some /t/some-english/###.
Would you disable this feature? What do you think?
This used to work fine but I haven't tried to SSH in for some weeks.
I have tried rebuilding my container using
sudo ./launcher rebuild app
but this still prompts me for a root password
sudo ./launcher ssh app
root@0.0.0.0's password:
I'm using the latest discourse_docker from https://github.com/discourse/discourse_docker.git.
I have a feeling that the authorized_keys file in the app container isn't being refreshed when I run that rebuild command above. (Also, when I run that rebuild should it clean out my database or not?)
We interact with Discourse in different ways. I'm curious to know how common my particular workflow is compared to others.
Here's what I do when I land on meta.discourse.org:
Check latest notifications.
If a post of mine got liked I'll usually follow the notification link to be reminded what my post said.
If I've been replied to or mentioned there's a good chance I want to write a reply. If a long reply is required I might just hold off the Unread and New for later.
Next I'll attack the Unread column. And this is where I might deviate from the norm.
I'll open every unread post (that I'm interested in) in a background window, essentially lining them up for reading. Also a handy way of doing "background processing".
I'll proceed to read every new post, hotkey-closing the tabs as I'm finished with them.
Lastly I'll have a look through New to see if anything new has popped up.
Same background-tabs flow as above.
Note: I've set Consider topics new when: to created since you were here last`.
While oneboxing it again for example here it gets the correct status, but in the thread itself it has not updated.
Couldn't really word the title better, the status is always open as long as you aren't posting a closed issue (which you probably won't do at all though)
I was scanning through stuff on Meta, and realized how much I miss the incoming vs. outgoing link icons in the right column. Right now, especially with incoming links, you just get this random blue link floating out there, and have no idea what it's doing over there.
Our moderators have been complaining that extra notifications get sent out for very minor edits, merges and moves to posts. This is exacerbated by the way we started out using our forum which was to turn on email sending of all notifications for all of our 50+ staff using our forum. This means that, for example, when a post is moved to another topic an email is sent out to 50+ people because it is a new reply to that topic.
We know they will start getting too much email and are starting to encourage them to change their notification preferences, but in the meantime this is a real issue for us.
The feature I am looking for is some sort of "this is a minor change" tickbox like dokuwiki has or a "do not send notifications" tickbox that is only available when doing post moves or merges.
I don't know if there is any way to resolve this but would be interested in knowing what others have done beyond training. Basically what is happening is that gmail is remembering discourse email addresses, which then are provided as autocomplete options the next time users write an email destined for the forum. Their post then gets added to the existing topic instead of a new topic. It's happened a few times already.
Worse, it is also remembering discourse email address for users. So if you are not paying attention you can find yourself sending an email to discourse instead of to the person directly.
I understand the below topic is closed after lot of deliberation about using private messages to admin (moderator)
The major drawbacks in using PM to communicate with admin(moderator) / admin (moderator) group for new users are
Spams
Change in Trust Level System
No transparency to other moderators / admins about the conversation
No flexibility in control - it is all in or nothing kind of setting
But the actual problem is still there - it is important to make new users comfortable before they understand the community. There are always people who dont discover FAQ link or dont read the content in FAQ. They would love to have some user interaction before they do the right things. Anyone who is managing the community will understand this.
So I propose the following approach to address this problem.
Create a category called "newbie".
Assign "Create only" permission for TL0 users
Assign "Create, Reply and See" permission for Admins / Moderators
Create Only Permission
A user can only create a topic and
A user can see / reply to topics created by him
A user cannot see / reply to topics created by others
This is very similar to Lounge category created for TL3 & above. A community can create / delete lounge & newbie categories if required.
Advantages of this approach
A new user feel comfortable in knowing there is a place to ask any noob questions without people judgment
The workload of answering questions is shared among the admin / moderator groups or may be others we identify as community managers
All newbie questions are visible to all admins / moderators / community managers at one place. We can identify if there is any pattern and create new FAQs and banners accordingly.
No need to change the existing Trust level privileges or security controls. We can leverage the existing security infrastructure of categories.
No new UI / UX changes.
This is completely an optional step for a community. They can remove the category or change the minimum trust levels at any time.
We can leverage the tags, subcategories features to organize the newbie questions as well.
This small addition in category will also help in increasing the adoption of discourse in many other usecases like
helpdesk for customers in SAAS / tech support in any organization
talk to your CEO / ombudsman kind of scenarios for internal usage in orgs
for personalized training / q & a among introvert / health related audience.
I'm migrating from one server to another. The restore hangs at 3%, I've tried a few backups now.
The only major difference is this server is using an nginx reverse proxy, but best I can tell it's working properly.
upstream discourse {
#fail_timeout is optional; I throw it in to see errors quickly
server 127.0.0.1:4578 fail_timeout=5;
}
# configure the virtual host
server {
# replace with your domain name
server_name discuss.cojour.com;
location / {
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;
proxy_redirect off;
# pass to the upstream discourse server mentioned above
proxy_pass http://discourse;
}
}
Any clues on what I need to do to get this to work okay?
Is there any way when i use URL https://meta.discourse.org/login?redirect_url=www.something.com for user login and as soon as user login he will redirect to custom provide domain in redirect_url query string.
I want to add some custom Slug (lib/slug.rb) to my instance.It work fine. But after a rebuild, It won't survive. How can I do it? I find a interested Reposity on github https://github.com/lidel/discourse-locale-override
It appears when a thread contains a large amount of posts (I haven't narrowed it down to an exact amount yet) the "post jump" feature has a tendency to increment the desired post number by one.
Also note that there's no blue highlight animation when additional posts have to be loaded first.
I am in the process of setting up Discourse as the forum element of an existing ASP.Net MVC site. It needs to offer as seamless a user experience as possible. I have got the SSO working and started adding a custom header and footer to mimic the existing site. So far so good.
However the existing site has the Login/Logout options in its own header section. Ideally I'd like this to log the user out of both sites whilst hiding the standard Discourse Logout. Is this possible? I was hoping I would be able to log off the main site and then Discourse in a similar manner to the way the log on works. I saw a couple of people asking for this in the (Official SSO thread) but it wasn't implemented at that time.
What is the current status? Or is there another way to solve my problem?
