I often use private messages on my discourse board. It annoys me that there is no "New Private Message" button on my "Messages" (/users/rumpelsepp/private-messages) page. If I want to send a message to several users I always have to do it like this:
Go to the profile of one user.
Click Private Message.
Add the others.
I would be happy to be able to do it like this (similar to creating a new topic on the latest page):
My forum is new, and I am getting some instances of spam content not being identified quickly enough so it is being distributed by email in the forum of notifications. This is annoying, obviously. Is there a way to know when digests will be sent, and if it's possible to prevent sending until spam is removed?
I think the text in the github boxes should be truncated. It does not look beautiful when linking to a commit with a long description, see this example:
After a bit of fiddling around with the data container i finally got it running. Unfortunately i'm stuck with the web container in my multisite installation.
Here's the error i get:
FAILED
--------------------
RuntimeError: cd /var/www/discourse && sudo -E -u discourse bundle exec rake multisite:migrate failed with return #<Process::Status: pid 164 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:105:in `spawn'
exec failed with the params "cd /var/www/discourse && sudo -E -u discourse bundle exec rake multisite:migrate"
$longnumber
FAILED TO BOOTSTRAP
I have deployed discourse as a bitnami stack on an Ubuntu 14.04 LTS VM. I originally played around with this on a development machine that had another apache server listening on port 80 and 443. When I configured this bitnami stack I used alternative ports (8080 and 8443). We played around and liked it.
I have now deployed the forum to a new dedictated VM where ports 80 and 443 are open to me. As a result, the new bitnami stack was configured to use those ports. I then exported by database and uploads from the original stack and imported them into the new stack.
Some users on our forum would like the option to force an amount of context in the notification emails.
I suggest this is implemented as a user-configurable option with a site default (shipped as 0).
The current situation as I understand it is that context is included if the user hasn't received that post in an email yet. Therefore, if they receive every email (mailing list mode), they'll never get context. This can be confusing if they delete emails after they've read them, because there's nothing to refer back to if the new post references something in that previous post.
This is also related to the Reply by email requires reply at top feature request, if users include quotes to provide some context, then the email processing breaks.
The option would force Discourse to include the previous # of posts made in the topic.
Hi, everyone! After running the (very easy-to-use) upgrade via the Admin panel, the CPU usage for the forums spiked and never went down. It killed the droplet a few times overnight, so I had to manually restart it.
I did create a backup before the upgrade, so I'm OK with going back to an earlier state, but that isn't a good long-term solution
What may be causing this? Would it be related to @krilnon's emoji plug-in? (I did disable and enable it to via the Admin panel's Plugins section to see if it was related, but it didn't affect the high CPU usage at all.)
Hello, everybody! I'm planning on replacing disqus comments with a discourse embed instead. As part of this, the script requires us to specify a discourseEmbedUrl that should be the URL of the page the comments will live on:
<script>
var foo = 100;
var discourseUrl = "http://forum.kirupa.com/",
discourseEmbedUrl = window.location.href;
(function() {
var d = document.createElement('script'); d.type = 'text/javascript'; d.async = true;
d.src = discourseUrl + 'javascripts/embed.js';
(document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(d);
})();
</script>
From my limited testing, it seems like this discourseEmbedUrl value is what associates a forum entry as well. If this URL value were to ever change, the association with the corresponding discourse topic is lost. A new topic needs to be created instead.
Is there a way for me to make the association more generic and not be associated with the page URL? For example, it would be great to specify a GUID that will be unique for each page.
I am thinking about a future where I might rewrite my URLs to be different, change domain names, etc. If this isn't particularly appealing as a feature, is there an alternate mechanism by which I can re-map the association between pages on the site and the forum topics?
Is there possibly a difference in the handling of JSON and formencoded data by the REST API?
If I create a topic it works with Content-Type: application/x-www-formencoded:
POST /posts HTTP/1.1
Content-Type: application/x-www-form-urlencoded
api_key=8d3ca248f3e30e5985a11344568b4ec52a599533f46878bea96f5c5d868abd4f&api_username=spero&raw=http://www.youtube.com/watch?v=05zrCwLDkVQ&title=What's Good About Compassion&is_warning=false&category=33&archetype=regular
but not for JSON, returning 403 Forbidden BAD CSRF which makes me think the api key and username are not being pulled from the JSON data the same way they are from the form encoded above. Or did I screw up something in the JSON? Changing the URL to end in .json has no impact.
POST /posts HTTP/1.1
Content-Type: application/json
{ "api_key":"8d3ca248f3e30e5985a11344568b4ec52a599533f46878bea96f5c5d868abd4f", "api_username":"spero", "raw":"http://www.youtube.com/watch?v=05zrCwLDkVQ", "title":"What's Good About Compassion", "is_warning":"false", "category":"33", "archetype":"regular" }
My guess is that as soon as I hit enter whatever silly mistake I made jumps off the page.
Actually it's a Chinese search issue. As I followed @sam 's suggestion in the post bellow.However , it didn't work . And I checked my discourse database encoding .It still shows SQL_ASCII . If I change it to UTF-8,the Chinese search may work. So How can I change the database encoding?
Is this something which can be done? I'm not sure that I want to turn it off for everyone, as I personally think the date in the subject line is a good thing, but there seems to be a use case for allowing something like this on a per-user basis.
I have a particular member that isn't receiving the digest despite being registered for the daily version. He hasn't visited the forum for over a day, he receives other email notifications fine, and other members receive the digest just fine.
I've tried triggering the job that sends out the digest, which didn't send anything out to him.
Any suggestions where to start troubleshooting or to understand why he isn't having one sent out? Mandrill doesn't show any digests sent to him at all, but it does show digests sent to other members, including a member that was "last seen" more recently.
Does it take into account whether the member has posted to the forum and reset the "not seen for [x]" timer? The other member who was "last seen" more recently hasn't posted for 4 days, whether this other member has within the last 24hrs.
Does anyone like an idea of having a publicly editable list of stop words so that entries can be added only (removed by staff only). Probably a good idea for plugin?
Current stop words list is useless especially when you have to put there ~1k words.
Also, I'd like to be able to just copy-paste a comma-separate list of such stop-words instead of pressing Enter after entering every word in the settings panel.
then I need to upgarde Discourse to export my datas ?
