My colleges could publish our posts without any problems to Discourse.
If I'm going to write my posts on Wordpress and publish them on Discourse, I've always got this error:
Warning: First parameter must either be an object or the name of an existing class in
/webdata/wordpress/wp-content/plugins/wp-discourse-0.6.6/lib/discourse.php on line 507
Warning: Cannot modify header information - headers already sent by (output started at
/webdata/wordpress/wp-content/plugins/wp-discourse-0.6.6/lib/discourse.php:507) in
/webdata/wordpress/wp-admin/post.php on line 197
Warning: Cannot modify header information - headers already sent by (output started at
/webdata/wordpress/wp-content/plugins/wp-discourse-0.6.6/lib/discourse.php:507) in
/webdata/wordpress/wp-includes/pluggable.php on line 1228
The posts of my colleges will be shown on our Discourse instance. Not my ones. (I'm admin)
New to Discourse and would like to develop a plugin.
I would like to create a plugin that can do autocomplete search in the input area which will query a json end point of a website I own and display the results and user is able to select using keyboard (like mention or emoji feature)
Can I know if this is feasible via plugin and any code that I can use as reference?
Hello guys, I'm having a bilingual forum, and I'd like for language users to see a category title in their language. So far, the only solution coming to my mind is to set 2 instances of discourse and have each one have a language, but I believe there is a smarter way, isn't it ?
There are many open bugs on meta related to incorrect email reply parsing and I have been looking into them since past few days.
Almost everytime the fix is to correct/modify something in GitHub's email_reply_parser library.
The GitHub's email_reply_parser library is now abandoned. The last commit was over a year ago, and there are many open issues / pull requests.
I propose that we include the email_reply_parser in core Discourse email library so that we can customize it as per our requirements, without depending on GitHub's library.
I have laid the groundwork for this, and in process fixed these bugs:
Here is the PR for the same:
Looking forward to hear @team's feedback/suggestions.
I have also enabled error logging. There are no relevant errors on the log.
On the specific category pages, I created a different email account for each page. I made all of the accounts forward to the main account, cellprofiler.dev@gmail.com
I have been trying to install Discourse on my VPS (1GB RAM), I have a swapfile and all, however when I get to the part where you have to run ./loader bootstrap app, it errors out, the error looks something like this:
chown: changing ownership of ‘/var/www/discourse/.bundle’: Disk quota exceeded
I, [2015-12-09T20:14:48.373258 #36] INFO -- :
I, [2015-12-09T20:14:48.400951 #36] INFO -- : Terminating async processes
I, [2015-12-09T20:14:48.401066 #36] INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/9.3/bin/postmaster -D /etc/postgresql/9.3/main pid: 65
I, [2015-12-09T20:14:48.409038 #36] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 193
2015-12-09 20:14:48 UTC [65-2] LOG: received fast shutdown request
2015-12-09 20:14:48 UTC [65-3] LOG: aborting any active transactions
2015-12-09 20:14:48 UTC [72-2] LOG: autovacuum launcher shutting down
193:signal-handler (1449692088) Received SIGTERM scheduling shutdown...
193:M 09 Dec 20:14:48.454 # User requested shutdown...
193:M 09 Dec 20:14:48.454 * Saving the final RDB snapshot before exiting.
193:M 09 Dec 20:14:48.469 * DB saved on disk
193:M 09 Dec 20:14:48.469 # Redis is now ready to exit, bye bye...
2015-12-09 20:14:48 UTC [69-1] LOG: shutting down
2015-12-09 20:14:48 UTC [69-2] LOG: database system is shut down
FAILED
--------------------
RuntimeError: cd /var/www/discourse && chown -R discourse /var/www/discourse failed with return #<Process::Status: pid 292 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:105:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"web", "cmd"=>["gem update bundler", "chown -R discourse $home"]}
97c624fd7ac6347cf9c58dc184729f7071786f0519be673108ca568b43f37b4f
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one
Can you guys please help with this?
Thanks
EDIT: There are NO disk quotas in place. The server is also NOT out of disk space (see below).
I am using Discourse as a platform for teaching my university courses. I am interested in using Discourse's stats as a measure of "class participation."
How is read-time calculated? I keep a discourse window open all day. I trust that doesn't convince Discourse that I'm "reading" (and of course it can't know whether I really am, but I can't tell whether students in a f2f class are listening, either). Just what counts as "reading?" How easy is it for students to game the system? (The proper answer is "Use the Source, Luke," but I don't know where to start looking. Telling me which file to look in could be a good part of an answer).
I'd also welcome discourse about whether people think these are reasonable measures of "participation" and the degree to which they can be gamed. For example, it's easy to give likes, even for things that you don't read, but maybe the fact that likes are limited to X per day is enough to counter that.
I was just curious as to what would be suggested with respect to optimal pixel and file sizes for badge icons (or even file type). We have custom ones we would like to upload and do not want them weighing us down.
Mobile keyboards tend to add spaces when auto-completing words. We don't strip trailing spaces from email addresses on the login screen. I've had users trying to log in on mobile run into this, it returns "no account matches xyz@mail.com", for an account that does exist.
They are stripped from the invite form already. We should strip them on login too.
Tough to replicate this on try due to lack of moderator privileges, but I have noticed that when editing a topic to change its category, it appears as a "new" topic again. Not sure if this is related to a user preference setting to track all topics in the category it was moved to, but if I have already read the topic, and simply changed the category, it should not be considered a new topic.
Another thing to note is that it does not appear as though the individual posts are considered "unread," as the small blue circles do not reappear. From a tracking/watching perspective I feel that changing a category should trigger the same response as a user editing their post or a tag being changed (just bump it to the top of latest).
When a site is configured to only allow login from email addresses with a particular domain, the sign up screen done properly prevent creating accounts with an email address from another domain.
See the current flow here.
1. Site setting is configured to only allow email from your domain:
When a site is configured to only allow login from email addresses with a particular domain, and a user attempts to invite someone to a topic with an email outside of that domain, the failure message could be more informative:
1. Site setting is configured to only allow email from your domain:
Hi everyone Recently, I have installed Discource on Digital Ocean VPS via Discourse Docker. Now, I want move source code and database to new server. This server I build from scratch mean as I self install Ruby, PosgresSQL, Redis,.... Please help me move to new server Thanks!
Before I go any further, These codes do not belong to me, I just merged both the codes, add changes Color codes thats about it. So the real credit goes to @rewphus and {unknown}(I am forgetting where i got the basic dark theme from, please do let me know who it is)
This is to kick start your forum if you want a dark theme, if you want a light theme please visit the link below for original codes by folks who made this. So you don't have to go to the trouble of searching every corner possible. I will also explain the icons used in forums and the dimensions used with best of my knowledge.
Discourse: $25,000. Discourse is online discussion forum software, used by several Mozilla communities. Their award will be used to make email a first-class interaction mechanism for Discourse, allowing Discourse instances to replace and improve upon mailing lists.
In late October Mozilla announced something called the Mozilla Open Source Support Program. Their selection criteria seemed favourable towards Discourse, so we decided to take a shot at it.
I am reminded regularly of how deeply Mozillians identify open source and free software as a critical element of an open Internet and healthy, trustworthy online experiences. I am excited to build a program that helps us bring concrete support to this worldview. You are the key to making this program great – to identifying great projects, to helping figure out what engagement from Mozilla would make a meaningful difference and to deepening Mozilla’s connections with our open source and free software compatriots.
Today, we are pleased to announce that the MOSS program has awarded Discourse a grant of $25’000!
OK, strange question here. With the upcoming improvements to group messaging, I am wondering if there is/will be a built in system for messaging just the moderators (not all staff). To go with that, does the admin/moderator system fit the rectangle square analogy (All admins are moderators, but all moderators are not necessarily admins.) With that, if a user is an admin, but not a moderator, do they lose access to anything?
The potential use case is when your site uses moderators and admins for different purposes. In my case, all admins are employees of the company, where the moderators are volunteers. Right now, when a user spots a topic in the wrong category or duplicated, they type a random assortment of moderators into their post to ask for it to be recategorized, or merged. It would be really nice if they could type something like @moderators and notify all moderators, without bothering the admins.