There seems to be two options for multiple Discoure installs, multiple containers or one - what are the pros and cons of each, and perhaps, which do you think makes more sense for my needs (see below)?
My server is set up so that each site on it is in its own folder in the /home directory, e.g.:
/home/site1
/home/site2
/home/site3
etc
So I would prefer to install each Discourse forum in the same way:
I am familiarizing myself with Discourse. One thing I have noticed is that the community seems to prefer the approach Discourse + Static Pages vs. Discourse + CMS/dinamic. I was wondering, what if I want users to be able to write articles/reports/posts? Sure, they could create a new topic, but I am talking about medium like articles here, with the possibility to have full width images and, overall, a nicer design for an article. Also, I would like users to be able to add media to those pages (files, gps tracks, etc.) and photo galleries.
Now, so far I could come up with 2 ways of doing this:
Separate dynamic website
Discourse plugin that allows users with a certain score to create static articles
Which one of the 2 options is advisable? And if it's the second option, could you give me some high level directions on how to structure such a Discourse plugin?
I recently updated to the Discourse 1.4.0.beta10. It seems that the "logout redirect" setting is longer working as I'm not getting redirected after logging out (which is needed for our SSO login system).
Is this intended and did something change regarding this feature or is this a bug?
Search the Meta forum (specifically Features and Extensibility) with a few different terms.
Can’t find any mention of your idea? Okay then, just one more thing before you share it:
Not all features are suitable for core.
With that in mind, you are good to go!
Type up your idea and add it to the Features section
Need some guidance on how to write a great feature request? Naturally, there's a Stack Exchange article for that:
Rewrite specific to Discourse Meta still pending.
Want to ensure your feature gets made?
If you’re not able to develop a feature yourself, there are still a couple other ways you can influence the likeliness of a feature being made:
Become a discourse.org customer
Paying customers of Discourse.org get - and rightly so - some preferential treatment when it comes to feature requests.
Offer paid work on the Marketplace
If there's a plugin you need made that's critical to your business, you could advertise a paid assignment on the Marketplace be sure to post as many details as you can including screenshots and budget.
Hey guys, I'm migrating an old discourse installation to a new one (in a new server), but I need to have a brand new installation with the existing users.
Is it possible to do this through the available tools? I couldn't find the option but I'd be glad to hear about any tricks or hacks to get the job done.
"If a thread is started in the lounge section, it's auto locked after 2 days of the last post. But threads MOVED to the lounge are not auto locked after 2 days."
We recently migrated our Discourse setup to a new VPS and we did so by utilizing the backup/restore feature, all inside Docker environments.
We migrated our data backup from a v1.4.0.beta10 installation to the same version on the new container.
Seemed fine. We then discovered a new category for uncategorized posts, which wasn't there prior to the move. But it could be turned off.
The problem though is that it's now impossible to create new topics. Whenever user enter a category followed by a "+New Topic" button click, the categories list to choose from is empty.
There is a great opportunity to improve the Poll oneboxing. It would be ideal if it oneboxed the entire poll so people could easily vote and see results.
My users really like the poll feature and use it often - and it has some really good information in it sometimes that we'd like to share with many other users via linking/referrals - but the current oneboxing really doesn't do it justice, or make it easy.
Please add the entire poll format to the onebox so it has the voting options. (I'm assumign this is possible without too much trouble).
Hi, in our community we require a certain format for titles posted in a certain category. However, sometimes when a user attempts to make a topic or edit a topic's title, the title appears in lowercase letters. For example, a date for an event on our forum would be written like this:
Day of the month, time in Zulu, Month, Year
Which would be written like this:
DDTTTTZMMYY
And would ultimately show up like this:
072140ZSEP15
(September 7th, 2015, 2140 Zulu). Occasionally when someone attempts to write a title like this, it would show up like this:
072140zsep15
And the user is unable to make the letters uppercase again, even after multiple attempts of editing the title.
Just went about setting up Facebook oAuth and got the following message -- wondering if this is something I can change, or is this a source code issue?
You are using a display type of 'page' in a small browser window or popup. For a better user experience, show this dialog with our JavaScript SDK without specifying an explicit display type. The SDK will choose the best display type for each environment. Alternatively, use display type 'popup' if you have special requirements precluding you from using the SDK. This message is only visible to developers of your application.
I have a forum where a single category would benefit from a topic template - the "support" category, as may be typical. This is the most used category, so it's the default when anyone hits the "new topic" button so they get the topic template in question.
The problem is that if they change their post category, the (now irrelevant) topic template doesn't go away (i.e. change to the blank template that is the setting for that other category). Likewise if you change to another category that does have a topic template, you are still left with the old topic template.
I get that the current behavior is "only set the template if the post was blank" to avoid stomping on user changes. That makes sense. *However, it seems the better behavior may be "set the template if the post is blank *or matches the template of the category I'm deselecting"?
Or possibly, have a simple "dirty" flag for the post that is initially false. When the user makes any edit (keypress) in the editor, set it to true. When changing the post category, replace the contents with the topic template if the dirty flag is false.