@mkucharz wrote:
I'm working on tight integration between Slack and Discourse. For now I want to extend slack notification plugin with functionality of sending special notification after mention. Can someone suggest me the right way of getting this info in a plugin? For now, I see that I can search for it in the content of the post, but maybe this is not the optimal way?
Best,
Posts: 1
Participants: 1
@Andrea_Soster wrote:
Dears,
the mbox importer is broken, these are the errors I'm getting:
discourse@ubuntu-app:/var/www/discourse/script/import_scripts$ ruby mbox.rb loading existing groups... loading existing users... loading existing categories... loading existing posts... loading existing topics... creating indices 187 / 188 ( 99.5%) importing users 24 / 24 (100.0%) creating forum topics /var/www/discourse/lib/email/receiver.rb:26:in `initialize': wrong number of arguments (2 for 1) (ArgumentError) from mbox.rb:151:in `new' from mbox.rb:151:in `block (2 levels) in create_forum_topics' from /var/www/discourse/script/import_scripts/base.rb:421:in `block in create_posts' from /var/www/discourse/script/import_scripts/base.rb:420:in `each' from /var/www/discourse/script/import_scripts/base.rb:420:in `create_posts' from mbox.rb:149:in `block in create_forum_topics' from /var/www/discourse/script/import_scripts/base.rb:702:in `block in batches' from /var/www/discourse/script/import_scripts/base.rb:701:in `loop' from /var/www/discourse/script/import_scripts/base.rb:701:in `batches' from mbox.rb:143:in `create_forum_topics' from mbox.rb:17:in `execute' from /var/www/discourse/script/import_scripts/base.rb:45:in `perform' from mbox.rb:212:in `<main>'and:
discourse@ubuntu-app:/var/www/discourse/script/import_scripts$ ruby mbox.rb loading existing groups... loading existing users... loading existing categories... loading existing posts... loading existing topics... importing users Skipping 24 already imported users creating forum topics /var/www/discourse/lib/email/receiver.rb:98:in `select_body': wrong number of arguments (1 for 0) (ArgumentError) from mbox.rb:155:in `block (2 levels) in create_forum_topics' from /var/www/discourse/script/import_scripts/base.rb:421:in `block in create_posts' from /var/www/discourse/script/import_scripts/base.rb:420:in `each' from /var/www/discourse/script/import_scripts/base.rb:420:in `create_posts' from mbox.rb:149:in `block in create_forum_topics' from /var/www/discourse/script/import_scripts/base.rb:702:in `block in batches' from /var/www/discourse/script/import_scripts/base.rb:701:in `loop' from /var/www/discourse/script/import_scripts/base.rb:701:in `batches' from mbox.rb:143:in `create_forum_topics' from mbox.rb:17:in `execute' from /var/www/discourse/script/import_scripts/base.rb:45:in `perform' from mbox.rb:212:in `<main>'I think that this commit broke it, and the fix is quite easy.
Please see the attached patch: mbox.rb.diff.txt (1.4 KB)
Posts: 2
Participants: 2
@Thomas_Louis wrote:
So for the first time in about three setups, I'm having trouble setting up mandrill with discourse, and when people click "login" it takes them to an error page. Really not sure what's going wrong, but I'd be more than happy to paypal someone a few bucks to help me solve it!
talk.thesportscollective.co !
Posts: 2
Participants: 2
@djcyry wrote:
Hello ,
I have a Asus Zenfone 5 inch and the design of my discourse is not responsive at all :Is not like here on meta :
No css modifications , all default .
Posts: 6
Participants: 3
@Steve_Ng wrote:
Hi, I wanted to add additionally functionality through a plugin.
I added a topic controller at plugins/xx/assets/javascripts/discourse/controllers/topic.js.es6
and I have
import TopicController from 'discourse/controllers/topic'; export default TopicController.reopen({ actions: { own_actions:function() { debugger; }; } });when I tried to call the action from my topic.hbs template, it says action own_action is not found. is theer anything I would have to do to initialize this controller?
Posts: 2
Participants: 2
@CamilleRoux wrote:
Hi,
What are the cheapest ways to host a Discourse currently? (for small communities)
Posts: 2
Participants: 2
@terraboss wrote:
Since the latest updates, we've noticed that our default site language has changed from German to English. The global site setting "default locale" isn't available any more.
How can change the site language again?
Thanks,
M
Posts: 9
Participants: 4
@downey wrote:
Reproduce:
- Get an admin notification ("quaternary" color I believe) that there is a new notification for queued posts.
- Click the hamburger menu and choose "Needs Approval".
- Review/clear the needs approval list, and/or Click Refresh.
Expected results:
- The notification goes away.
Actual results:
- The notification never goes away until completely reloading the entire page in the browser.
Posts: 1
Participants: 1
@joebuhlig wrote:
I'm trying to learn Ember as I build for Discourse so forgive me if this is simple. I'm attempting to add a route underneath the userActivity resource. If I understand correctly, I should be able to do something along these lines:
export default { resource: 'user.userActivity', map() { this.route('votes'); } };But that doesn't do it. I've read through these two topics:
Posts: 1
Participants: 1
@downey wrote:
Reproduce:
- Reply to a topic and use '
' in the body of the post.
Expected results:
- The '
' symbol appears in the post where desired.
Actual results - editor window:
Actual results - editor preview:
Actual results - rendered post:
Posts: 8
Participants: 5
@harto wrote:
We have an SSO setup that tries to create users with usernames matching their canonical (external) account. I recently noticed that this fails for usernames with a trailing underscore.
What's the recommended solution for this? Should we be normalizing usernames in our SSO endpoint? Or is there some way for Discourse to normalize the given username? Thanks.
Posts: 7
Participants: 3
@tgxworld wrote:
Continuing the discussion from Support for Let's Encrypt:
TL;DR
1. Add
web.ssl.template.ymlandweb.letsencrypt.ssl.template.ymlto undertemplatestemplates: - "templates/web.template.yml" - "templates/web.ssl.template.yml" - "templates/web.letsencrypt.ssl.template.yml"2. Expose port 443
expose: - "80:80" - "443:443"3. Run the following commands
./launcher rebuild <container name>- Profit
![:moneybag:]( ":moneybag:")
How does it work?
The template uses https://github.com/Neilpang/le which is
Simplest shell script for LetsEncrypt free Certificate client
Simple and Powerful, you only need 3 minutes to learn.
Pure written in bash, no dependencies to python , acme-tiny or LetsEncrypt official client. Just one script, to issue, renew your certificates automatically.
Probably it's the smallest&easiest&smartest shell script to automatically issue&renew the free certificates from LetsEncrypt.
web.letsencrypt.ssl.template.ymladds a startup script to your container that
- Issues a Let's Encrypt cert using the standalone mode. It boots a standalone server that listens on port
80but this happens beforenginxis up so port 80 is free.- Installs the cert into the right directory that
nginxexpects. At the same time, it adds a cron job that runs a daily cert renewal check. Nothing happens if cert has not expired.- Switches the script to use the webroot plugin with
/var/www/discourse/publicas the directory. This will allow us to usenginxas the server that handles domain validation. Zero downtime during cert renewal!Debugging
Testing a cert issue
./launcher enter app STAGE=1 FORCE=1 LE_WORKING_DIR=/shared/letsencrypt /shared/letsencrypt/le.sh issue no myawesomedomain.com no 4096
Posts: 7
Participants: 4
@terraboss wrote:
Today, I was looking for new way to manage help desk inquires.
Most of todays solutions are available as SaaS plans. Other open source projects (osTicket) feeling pretty lame... 1990-2000 like ...
It would be much better to get something that feels responsive as Discourse does. But the integration between Discourse and the help desk has to be much better.
That's why, I came to the point, http://helpy.io could possiply fit to our workflow.
Some questions to other community admins:
- Are you using some kind of standalone self-hosted help desk?
- Did you find some way to connect Discourse with it? (users, faqs,...)
For Discourse core team and other contributers:
- Which help desk approach could you reccomand me in combination with Discourse?
- What about some additional attributes like pending status, internal notes, text templates, etc. ... for a new help desk plugin?
Best
Posts: 3
Participants: 3
@Chris_Tsai wrote:
Translation:
Since Chinese locale is being used, why is such a long min topic title length required
Posts: 4
Participants: 4
@Chris_Tsai wrote:
When I first come to discourse, it shows all categories.
If I only interesting about the feature category and want the default page shows this category, is there any way for me to set?
Posts: 1
Participants: 1
@IamCharlesHan wrote:
SSO does not open new window. Is this the default behavior? If so, how do I make it so that Login button opens up a new window?
Posts: 4
Participants: 2
@AZDD wrote:
Hi,
I upgraded to the latest version of Discourse tonight. When I click the login button, the button doesn't appear to function. Also, when clicking Create Category, it appears to try to lightbox but nothing displays in the lightbox. At first I thought this could be custom CSS conflicting with the code, but I disabled any custom CSS. Same issue exists. Any ideas?
Thanks,
Posts: 4
Participants: 2
@hisnameisjimmy wrote:
I'd like to install Discourse on my server, which already has a live Wordpress website running on Apache. Further, I'd like to run it out of a folder, utilizing SSL. I'm currently running the site on a Digital Ocean 2gb Ubuntu 14.04 droplet.
Ideally:
Wordpress on Apache: https://www.website.com
Discourse: https://www.website.com/communityThere are a few guides here on how to do pieces of this:
https://www.digitalocean.com/community/tutorials/how-to-install-discourse-on-ubuntu-14-04
https://www.digitalocean.com/community/questions/need-help-with-installing-discourse-and-wordpress
This seems interesting, but I've seen warnings against using anything other than an Nginx proxy by Sam:
http://www.matrudev.com/post/discourse-wordpress-same-server/I'm struggling to bring this all together into a cohesive setup. If I am running discourse out of a folder, can I reference the same cert I'm using for the main website (guessing no)? What's the best way to reference these with an Nginx proxy config? Do I still reference community.website.com in the Nginx config if I have the folder setup going in my app.yml (assuming yes since DISCOURSE_HOSTNAME still has to be the subdomain, at least from what I understand).
I'd love it if someone smarter than me could bridge the gaps between all these other guides and create something canonical.
Posts: 4
Participants: 2
@fantasticfears wrote:
I am developing a paid plugin (don't know whether it's ok to public) where I need to set a category specific setting. Therefore, I compare several possible ways and proposal my suggestion.
With existing convenient custom_fields, it's intuitive to put category-specific settings in the
CategoryCustomField. discourse-solved takes this approach. Solved plugin uses the setting to permit action in server, while I am also interested in knowing the category settings in the client when user opens the category chooser or composer.Settings in Category's
custom_fieldsCategory has 3 serializers. 2 of them:
BasicCategorySerializerDiscourse preloads categories by
BasicCategorySerializerwith initial HTML.If discourse serializes
custom_fieldsbyBasicCategorySerializer, we'll know setting details without asking the server again. The drawback is custom_fields may be huge.
CategorySerializerRight now, discourse serializes
custom_fieldsfor category byCategorySerializer. In client site, we may askCategory.reloadByIdto get more data about category includingcustom_fields. For the record, it's invoked byeditCategory(category)in routes/application.js when you click Edit category button.A client plugin have to get category details before access category specific details. The client can change states after getting the result. The drawback could be many GET requests and asynchronous.
Plugin who is interested in category-specific setting
A client plugin may query when:
- When user changes category in category chooser.
- Delay
- GET requests based on changing category.
- When category chooser is loaded, clients load all category settings.
- Lots of GET requests.
Proposal
Here it's all three ways to enable category specific settings in my mind. While I may be terribly wrong, it's good to hear some feedbacks
![:sunny:]( ":sunny:")
- Moving category custom_fields to BasicCategorySerializer from CategorySerializer. I suppose initial payload size is critical. It's not a good idea.
- Creates an custom_fields endpoint to allow batch querying.
- Uses some site settings or cache?
Posts: 3
Participants: 2
' in the body of the post.
