Hi, I'm completely new to Discourse, Rails and Ember, so please excuse my basic question
I want to add some additional blocks of information gathered from external sources to the discourse website. I have the logic done already as a jquery block, using an existing jquery plugin. I've found an adsense plugin and it is adding a banner div above the content very well and seems to have a logic responsible for reloading the content on "page change" in Discourse. Exactly what I need.
But I'm stuck on something absolutely basic. How do I add an existing jquery plugin (inside my plugin folder) as a script inside the head section? I can't find any information on getting the path of a resource from plugin folder and the function to add this path into head section.
Are there any resources I could use in learning about discourse plugins?
I have a discuorse forum, or rather I am staff of one and I have a Twitter account I no longer use as my login method. Is there a way to change the Twitter account, or merge the account with another, maybe local account?
After updating (which also told me to update my docker container, since I was on 1.0 until now), my instance won't come back up. ./launcher logs tells me: nginx: [emerg] duplicate location "/backups/" in /etc/nginx/conf.d/discourse.conf:79 <message repeats ad infinitum>
Unfortunately, a commit seems to have sneaked in twice while merging:
nginx doesn't like that. Is there any way to get that fixed on the stable branch? Thanks in advance!
I'm looking for clarification on how to configure permissions for a custom group. In our scenario we want everyone with a looker.com email address to be assigned moderator permissions.
I am able to create a custom group as described above that is automatically attached to all looker.com addresses. However, I don't see a method for creating permissions for the new custom group.
Hello, I'm Traditional Chinese user. When I upgrade the version of discourse in developer env to 1.2, I found some translations are missing. But I could found the original text in client.en.yml or server.en.yml. And I try to switch discourse to English version to see the original text, I got these:
I've noticed many times that when connecting on Discourse via a mobile device suffering from a intermittent/bad internet connection, the user may post the same content twice. For the user, it's as if he or she had posted only once, given that the console only closes once, thus displaying only one acknowledgement client-side.
Probably no-one is encountering this problem since the default "unique posts mins" and "rate limit create post" settings should prevent it from happening most of the time. I've set mine to 0 and 1 sec, respectively, for reasons I will not explain. However, I'm not even sure that setting this to a higher value will be enough if for instance the user modifies his/her post in-between "post failures", and waits enough seconds to repost after some unpredictable timeout. Bottom-line, I'm not sure how and why this actually happens and little do I know about the current implementation, but I would like to know if anyone else has encountered this issue. I'm actually not comfortable with the idea that tuning a parameter is the only way to fix this problem.
If somebody else has encountered this problem with the default settings it would be nice to have a feature to prevent this happening that would be based on some unique client-side id generated for each post/topic that the user creates, thus not requiring rate-limiting workarounds. I realize my settings are quite rare, but I also think that a difference should be made between rate-limiting features and a double-post prevention feature. Nonetheless I also understand that such a feature might be hard to pull off properly, without too many side-effects, and might not be worth the effort.
But this seems not to be affecting migrated old topics, as they are still open. How can I achieve this? (want to close all topics which are older than 720 hours=30 days)
hard disk 10240 MiB (2289 MiB used) Number of processors 1 ROM 256 MiB condition running processor Speed 2400 MHz OS template ubuntu-14.04-x86_64-minimal
Recently while reading a long topic on Discourse with many posts, I came across the "Summarize this Topic" button. I initially thought that this button would allow me to write a summary of the topic which others could read. I was pleasantly surprised to discover that the button instead allowed me to view a condensed version of the discussion with some posts hidden.
That got me thinking though: what if Discourse allowed users to create community-editable summaries of long, popular threads? This would be useful in all sorts of situations, such as:
Product support questions: add answer / progress in finding answer
Long discussions on feature proposals: document community consensus, and the current point the discussion is at
Any sort of long-running discussion where it's difficult for a new participant to understand the discussion without reading everything
The existing "summarize this topic" button is helpful in those situations to some degree, but it still requires a lot of reading and can't sum things up nearly as well as a human might be able to.
To be clear, I'm not advocating for replacing the "Summarize this Topic" button; this suggestion is for an additional feature, not a replacement.
What do you think? Good idea? Or not worth the effort?
