Our community building and discussion forum uses a pretty slick integration with Discourse the worlds largest opensource forum software. This sync enables us to use Discourse to handling the community building, communications, admin functions, and backend of the most of the platform.
Settings in our Github
Docuss Project Github
Plugin
In our Discourse settings you’ll find a plugin called: dcs-discourse-plugin. This is where the default category is set among other functions
Connecting Docuss to Specific Pages
Discourse Categories for Each Page
The category posts are created in on each page can be edited here:
File Format
Admin Controls
When composing or editing a post an admin can press ‘Alt+A’ at the same time to reveal and edit the category the post will be placed, and to see and edit the hidden tags Docuss puts in to allow it to find threads.
Known Docuss Bugs and Bug Fixes
You need to select a category before posting:
Docuss automatically selects a category from the category names on our platform. If it can’t find a category then it won’t select one accurately.
The category names at line 173 here have to exactly match a category name in our platform (the url string is unimportant, just the name). If you want more information you can see this issue being explored and resolved here
Url links open inside of our platform when not intended:
If the link is internal this behaviour looks as if our platform is open inside itself and you’ll see a double menu at the top of the page. If the link is external you’ll see the internet page users wanted to visit when clicking, but loaded inside public happinessmovement.com, so our platforms main menu appears as a frame around it.
The solution is to add this code: <CardLink href={item.url} target="_top"> to the link. You should find a working example on line 30 here
40 posts were split to a new topic: Archive: Discussion on Docus
Hello everyone, sorry for the absence I got a job recently as IT support, I have some free time and I’m able to program so I been setting up the local environment again. There is a few things I don’t have clear yet.
- Do I need to connect the meteor and discourse app if I’m gonna be working on the back-end? if so how do I do it? I tried running the script for discourse on the meteor app but I think I’m still missing something because I can only see the home page and as soon as I click something like the local forum it doesn’t work
- As soon as I add the docuss plugin and enable it on my localhost it stops rendering the page completely. The “Adding Urls” link on this page is not working, is that relevant to this? I saw there is a setting on the Docuss plugin that lets you add a JSON with Urls, perhaps that’s what I’m missing?
Thank you in advance 
1 Like
@gastonsk Congrats on your job.
If you’re working on the backend you’ll probably want local host running so you can try things out, but its not necessary if you don’t want it.
We’ve got Teleport set up so you can access the servers. Right now its only set up on the deploy-btm branch, but one task we have now is to set Teleport up on master and deploy-phm so the backend team have access to everything.
-
The local side is a little broken with the update to the latest version of MeteorJS although you should be able to see the map. Can you share a screenshot of what you see when you click it. @zhna123 mentioned there was an issue with links right now, i think that might be what you are seeing.
-
Can you expand this as i’m not sure what’s going on. Taking a guess, you need to tell Docuss which pages to operate on. Did you follow this guide for discourse and Docuss: Setting up Discourse for Local Development (Local Host)
also connecting Docuss to specific pages here: Components - Docuss
The Master branch you downloaded should already have those pages set up.