@Steven wrote:

The gear button made an apparition in the composer since yesterday (I think it's related to the new poll builder), but nothing happens when we click on it (at least for users ranks <Leader).

It's a bit frustrating to have a button that cannot be use. Wouldn't it be better to hide it for users that can't use it?

PS : I wasn't sure if it was a bug or an ux discussion. Posted it on ux, it can be moved if necessary

Posts: 11

Participants: 5

Read full topic

@marcospreviato wrote:

Hi, this is my first post sharing a resource to help this wonderful community.

I want to help them create simple forms a tooltip for your forum making it modern and clean, ok lets do it!

First what is tooltip? A tooltip is often used to specify extra information about something when the user moves the mouse pointer over an element.

Something like this:

First add in your css style:

.posts .topic-body {
overflow: visible;
padding-top: 0px;
padding-left: auto;
padding-right: auto;
box-sizing: border-box;
width: calc(100% - 66px);
background-color: #fff !important;
z-index: auto;

After add this:

`/* Tooltip Text */
.tooltip .tooltiptext {
visibility: hidden;
background-color: black;
color: #fff;
width: 350px;
height: auto;
text-align: center;
padding: 5px 0;
border-radius: 6px;
z-index: 4;

/* Position the tooltip text - see examples below! */
position: absolute;
z-index: 4;

}

/* Show the tooltip text when you mouse over the tooltip container */
.tooltip:hover .tooltiptext {
visibility: visible;
}`

Example 1:

<div class="tooltip">This is a example
<span class="tooltiptext">this is a example of tooltip
<img src='//discourselk.s3.amazonaws.com/original/2X/0/0122629c69a65f1dfb54da13120909c542253960.jpg'</img></span>
</div>

This example relates to the image posted above with the image that says love discourse (yes i love)

Example 2:

<div class="tooltip">This is a example
<span class="tooltiptext">A tooltip is often used to specify extra information about something when the user moves the mouse pointer over an element
</span>
</div>

This example relates to the image posted above with text about tooltip

Now let's make this wonder work!
In your posts includes the following element:

<div class="tooltip">TEXT OF TOOLTIP
<span class="tooltiptext">Description of Tooltip</span>
</div>

Ok if you want to change where the tooltip will appear, just change the key ".tooltip .tooltiptext" and use the following codes:

Right Tooltip

.tooltip .tooltiptext {
top: -5px;
left: 105%;
}

Left Tooltip

.tooltip .tooltiptext {
top: -5px;
right: 105%;
}

Top Tooltip

.tooltip .tooltiptext {
width: 120px;
bottom: 100%;
left: 50%;
margin-left: -60px; /* Use half of the width (120/2 = 60), to center the tooltip */
}

Bottom Tooltip

.tooltip .tooltiptext {
width: 120px;
top: 100%;
left: 50%;
margin-left: -60px; /* Use half of the width (120/2 = 60), to center the tooltip */
}

NOTICE:

I know that for many this information is very simple, but after suffering with my site vidadedoteiro.com, I confess that CSS was never something that I know a lot, but I decided to share with you to help those like me who have suffered from something so simple.

Anyway I apologize if my English is not the best, but I made this topic with love.

Thanks!

Posts: 3

Participants: 3

Read full topic

@wityr wrote:

Use case is private email support portal. We have a private category that a handful of users can access. The general public can send emails to info@foo.bar and they are posted in our public emails category. When one of the discourse users replies, it gets posted in the topic, and the member of the public (now a staged user) gets the reply in an email. This all works well.

As of about a month ago (I just noticed this now and don't know exactly when it started) when that staged user replies to the topic they started their email is rejected:

Email can not be processed: Something has gone wrong. Perhaps this topic was closed or deleted while you were looking at it?

This is happening even though the topic is certainly not closed or deleted. Recently updated to 1.6.0.beta8 and the problem persists.

Posts: 2

Participants: 2

Read full topic

@fearlessfrog wrote:

Our free disk space went down by about a gig overnight, or rather the backup image size jumped up.

We're trying to figure out where it went, as we think a user may be uploading files to themselves via PM or something?

Where are good places to start looking in Discourse for this type of info, i.e. where the upload allocation went per user?

Posts: 4

Participants: 3

Read full topic

@fearlessfrog wrote:

So we're experimenting on using S3 for uploads. S3 is quite slow for, well anything really, so wanted to put a CDN like Cloudfront in-front of it. The setting :s3_cdn_url seems to be ideal for that. Using it is not quite what I expected though, so wanted help to check my understanding.

I can understand that it doesn't change older posts without rebaking, but since enabling we see this on new posts:

Pasted image1131x228 30.8 KB

So, the actual optimized/thumb is shown in straight Slow S3, but the full inside the lightbox is Cloudfront? Is that right, as it would seem that CloudFront could be used in-front of S3 all the time for images?

I guess the other way to go would be to map a custom DNS entry to the S3 bucket and let something like Cloudflare alias it? Anyone have experience with this?

EDIT: Hmm, can't use s3 virtual hosting domains with Discourse as it doesn't like the periods in the bucket name then. It makes setting up like this not possible:

http://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html

..which then stops simple DNS Cloudflare (as in not even using Cloudfront) improvements, as we can't have a files.ourforum.com like mapping? Seems a bit of shame or maybe I am missing something?

EDIT2: Wildcard certs fault, ignore the edit bit if that helps.

Posts: 3

Participants: 2

Read full topic

@sam wrote:

I am just rolling out an improved unsubscribe workflow per:

This is included in:

You can now unsubscribe from anything even if you are logged out!

• All unsubscription now happens via a centralized unsubscribe page

• This page always works, even if you are logged out. yes @riking I still force you to log out if you are logged in to the wrong account, by design

• The new page allows you to easily unwatch or mute a topic

• The new page allows you to easily unwatch a category and the huge amount of topics you may be watching in the category

Some examples:

If you have mailing list mode enabled, unsubscribe will take you to:

Pasted image835x377 14.5 KB

If you are watching a topic you will get:

Pasted image751x350 12.3 KB

If you are watching a category you will get:

Pasted image772x419 14.9 KB

This change significantly decreases the friction for opting out, the option "Don't send me any mail from sitename" is always there.

Posts: 1

Participants: 1

Read full topic

@Ericsworld wrote:

Forums are obviously very difficult to start up due to their inherent nature of requiring an active user base from the onset to ensure its own success.

I'm trying to start a niche automotive community with Discourse. It's only been about 5 days, but I can feel that things are constantly being balanced on a thin wire during these initial days.

What's the best way of rallying members and building the base, short of directly spamming everyone you know on Facebook (I've already done that, to an extent). Are there any other ways to advertise?

As far as content goes, I've been putting in work to keep the posts going and constantly try to generate interesting threads.

Posts: 4

Participants: 4

Read full topic

@Ericsworld wrote:

I'm currently on the 2GB RAM droplet with DO for my Discourse droplet. I'd like to actually drop this down to 1GB and will go through DO's steps on doing so.

Are there any configuration changes I need to make on Discourse's end or will it all automatically negotiated? I remember in earlier release there are "buffer" configs according to your droplet specs, not sure if those need to be changed at all anymore.

Posts: 3

Participants: 3

Read full topic

@Davidliu wrote:

Currently I have found two things not working.
- If there are some users and topics are already on the discourse, the script is not checking them within the script
- category's are not coming right now.
Is there any one who have some expereinced on this?

Posts: 1

Participants: 1

Read full topic

@fefrei wrote:

I'm operating two Discourse instances with login required, both running on the beta channel, both are up-to-date.

In one of these instances, local links to posts no longer onebox (they don't produce a broken onebox, they just do not onebox at all). No log entries are produced.

Does anyone have an idea what could be causing this?

Posts: 11

Participants: 3

Read full topic

@rcfox wrote:

About a year and a half ago, I was working on a Discourse instance for the company that I worked for, and in the process developed a couple of plugins that others have come to appreciate. Unfortunately, I'm no longer administering Discourse myself, so I have little interest in maintaining these plugins.

1. Webhooks - https://github.com/rcfox/Discourse-Webhooks
   I've received 18 stars on GitHub and several messages of thanks for this. I'm not sure if it still works, but no one has complained to me about it.
   Update: I guess this plugin will soon be obsolete, so nevermind it.

2. LinkedIn Sharing Button - https://github.com/rcfox/Discourse-LinkedIn-Sharing-Button
   I received an issue today that this has stopped working. It looks like there's a new plugin API and I no longer have access to the Sharing object? (Now it looks like I'd have to go and generate HTML+handlers myself for this button? That seems like a giant step back from calling Sharing.addSource.)

I'd hate for this functionality to just die, so if anyone wants to take over these projects, I'd be happy to have my repositories redirect people towards yours.

Posts: 4

Participants: 4

Read full topic

@angus wrote:

There are a few 'how to start' guides for working with Discourse already and a wealth of useful info on meta, but I thought it might help to give an insight to the mental processes of starting from little, if any, prior coding experience to building substantial Discourse plugins.

Discourse is written by experienced developers and has a large codebase. This can feel intimidating. This intimidation factor can be a significant barrier for novice developers. This is a kind of 'psychological primer' to building stuff for Discourse.

I'm not an expert at coding. I only taught myself how to code last year by playing around with Discourse. I'm partly putting this here because this is the basic approach I use to answer any questions I (or others) have when working with Discourse and it will be useful to link to.

1. Know the basics

Despite it's size, the Discourse codebase is easy to navigate if you know some basics. This is a testament to the quality of the work that has gone into it.

You have to start with understanding roughly how things work. That makes building new things a lot easier.

Specifically you need to understand:

1. The basics of how widgets, virtual dom and the new plugin api works. Read these two topics: Virtual Dom; Plugin API and read the documentation in the Virtual Dom github repo.

   Time: about 30 minutes to 1 hour.

2. The basics of how templates, views, controllers, models and routes work in Ember.js. You can cover this by reading the Ember.js guide.

   Time: about 30 minutes.

3. The basic structure of the application so you know where to look for stuff:

   • The 'client' is mostly in the app/assets folder. The javascript is divided into nice descriptive folders here.
   • The 'server' is mostly in the other folders in app. It is also in the lib folder.

   Time: 10 mins.

4. The basics of how to build a plugin. Just read the 6-part guide to building plugins and you're done.

   Time: 30 mins

5. The basics of how ruby on rails works (optional). There are hundreds of RoR guides and how-tos out there. Actually the only 'text' on ruby I've read is Why's Poignant Guide, which is very readable and quite funny.

   Time: about 1 hour.

6. How the Discourse server interacts with the Discourse client. Simply put all server / client interactions happen through ajax requests. Invariably, the answer to any question like "How do I get this data?" is that you retrieve it form the server via ajax. Do a search for Discourse.ajax in the github repository and you will see lots of examples.

   Time: 10 mins.

This background reading and absorption should take a couple of hours. You could do it one Saturday morning in your PJs.

2. Start with what you know (and can see).

Question: How do I get the information about a user on their summary page? (e.g. https://meta.discourse.org/users/angus/summary)

Answer: The best way to find what you're looking for is to start from what you know.

We know that the information we want is available at /users/[username]/summary. So how does that page get the information? Well let's start by having a look at the template or whatever is actually rendering the information. That is the next level down from "I am seeing the information on the screen".

In this case, the the user summary has a template. We know from our reading that all the templates are in this folder. Look through the folder for things that look relevant. There's a folder named 'User'. This data is about a user, so let's look in there. In that folder, there's a template called 'Summary'. That's a word that's used in the path where we know the info is. Cool, looks like we found it.

Hm, looks like the information that's being rendered is coming from a model.

We know from our reading that in Ember.js the model is loaded by a route file (see this part of the guide). We know from our reading that the route file for /user/[username]/summary is in assets/javascripts/discourse/routes/. Looking through that folder, the file user-summary looks like it's relevant.

Thankfully, it's nice and simple. It's using the method summary from the User model. So let's have a look at the User model method summary:

Turns out that this is exactly what we're after. This is a ajax request from the client to the server. We know that this is how the client gets all its info from the server.

So we already have our answer. We can do exactly the same thing in a plugin. Start by copying that ajax request and then modify it to suit your needs. This leads us to the next point.

3. Copy and use the Discourse code.

Discourse is an open source project. It's a very well written open source project. So if Discourse already does something, or does something similar to what you want to do, start by copying or using what Discourse does.

For example, I started writing my Quick Messages plugin by literally copying swathes of code from the composer controller and the code that, prior to the widgetized header, displayed the header menu items. You can see that perhaps the most important method in the whole plugin, the method that saves a new post, is just a modified version of the same method in Discourse.

If Discourse actually does exactly what you want to do, but just in a different context, then there's no need to re-invent the wheel. In most cases it is possible to use the existing Discourse solution in a different context. This is easy to do with ECMAScript 6 modules. For example, the Topic Previews Plugin imports a bunch of existing Discourse helpers that solve various issues it needs overcome.

Another trick I like to use is to start by actually modifying the Discourse code itself, before trying to work with it in the context of a plugin. You want to add another icon to the header? Start by trying to add another item to the header directly in the Discourse codebase on your local machine. Find the code that renders the current items, then just try to add some additional items by directly modifying that code. Once you've managed to do that, then try to apply that approach within your plugin. This approach removes additional sources of errors that can arise when working in the context of a plugin. If things are going wrong in your plugin it may be because you're not using the plugin api correctly, or it may be because you're not using the virtual dom correctly. Sometimes it helps to start by reducing the scope of the source of your errors.

4. Keep it simple and open

As the Discourse codebase is large, you can sometimes get lost in it. Sometimes it can feel like your search for a solution is leading you down a rabbit-hole of complexity.

Always remember that in 99% of cases the answer to your current problem will be simple. It's a matter of finding the simple solution. One way to find that solution is to use the community, either by posting on meta or by opening up your code to use and scrutiny. There's a good discussion of how this open approach works in Eric Raymond's The Cathedral and the Bazaar:

“Given enough eyeballs, all bugs are shallow.” I dub this: “Linus’s Law”. My original formulation was that every problem “will be transparent to somebody”. Linus demurred that the person who understands and fixes the problem is not necessarily or even usually the person who first characterizes it. “Somebody finds the problem,” he says, “and somebody else understands it. And I’ll go on record as saying that finding it is the bigger challenge.” ... In the bazaar ... you assume that bugs are generally shallow phenomena—or, at least, that they turn shallow pretty quickly when exposed to a thousand eager co-developers

On an individual scale, this means that you should stay focused on what you know and what you want to achieve. Don't get lost in trying to understand the inner workings of everything. In most cases, the basic background knowledge listed at the beginning of this post are enough to achieve what you want to do.

If you get stuck, either use the community, or simply persevere. 99% of problems are a matter of time and patience, not some deep technical understanding.

I hope that helps somebody.

Posts: 3

Participants: 3

Read full topic

@BlackSheep wrote:

The keyboard shortcuts to manage the level of atention to a topic are not working for me, neither in firefox nor chrome.

It is very comfortable to hit m+r when i am not interested any more in the topic i am reading, but it is not working for me.

Other shortcuts that are not working for me are

m+t to track the topic
m+r to watch the topic
m+wto normalize the level of atention
m+m to mute the topic

Posts: 3

Participants: 2

Read full topic

@fefrei wrote:

I think I am misunderstanding the site setting staff user custom fields.

I have multiple custom user field set up like this:

Only one of them is contained in the site setting staff user custom fields. Still, staff members see the value of all these custom fields in /admin/users.

Is this correct? How can I keep the values of some user fields secret from my staff members?

Posts: 1

Participants: 1

Read full topic

@fefrei wrote:

I'm using incoming mail support for group messaging with staged users.

This works fine if the address the message is coming from is new. However, I am re-purposing a Discourse installation for a yearly event, and some old users are stuck with an inactive accounts they can no longer log in to.

When such a user sends a mail to Discourse, they are rejected with Email::Receiver::InactiveUserError.
What's the best method to prevent this issue? Would replacing the mail address of the inactive accounts work?

Posts: 2

Participants: 2

Read full topic

@watchmanmonitor wrote:

I posted on a topic, it was removed, but my icon still shows in the topic list.

screenshot_1680.png813x78 9.06 KB

I'd expect my icon to be removed.

Posts: 2

Participants: 2

Read full topic

@cappslock wrote:

I'm using the API of Discourse with a custom UI. I'm attempting to integrate this behind an orchestration layer that already authenticates users. I'd like to be able to more or less bypass authentication on the Discourse side of things.

We use JWT tokens, and it seems that ideally I could just pass these along to Discourse and tell it to trust them. I see that there's some JWT related projects in the discourse GitHub organization, but there's no documentation or usage examples, Google hasn't been helpful, I haven't found any relevant threads in meta, and I don't really speak Ruby

Is there a way I could leverage our existing authentication by just passing these tokens through to Discourse?

Failing that, as an API user, how can I create topics and posts on behalf of other, authenticated users?

Posts: 6

Participants: 2

Read full topic

@benni wrote:

hey guys
I wanna create a nice little website + community board just like "www.discourse.org"
I have the PowerWeb Basic bundle from strato that means: domains, webspace and email accounts
at first I used the install-cloud documentation to get discourse on the server
but then I realised that the server is running SunOS
is it possible to install discourse on SunOS?

I also have a v-server from strato with ubuntu 14.04
can I install discourse on the ubuntu-server with the domain and emails from the SunOS server?
the install documention confuses me :s
would be really nice if you could help me

Posts: 1

Participants: 1

Read full topic

@fefrei wrote:

After rebuilding my site a few minutes ago, Discourse no longer loads.

I get this error in the JavaScript console:

Pasted image1920x585 78.5 KB

I'm down to these plugins, and the error is still there:

      - git clone https://github.com/discourse/docker_manager.git
      - git clone https://github.com/discourse/discourse-spoiler-alert.git
      - git clone https://github.com/discourse/discourse-data-explorer.git
      - git clone https://github.com/discourse/discourse-staff-notes

Disabling all site customizations did not help, too.

I'm out of ideas, and my Discourse instance is down

---

I should add that I am running on the (latest) beta commit.

Posts: 9

Participants: 4

Read full topic

@fearlessfrog wrote:

We had a recent need to find where our uploads size was increasing quickly, so this feature request breaks down into two ideas:

(1) A way to see per user the file upload capacity used, i.e. a per user total uploads in mb.

(2) A trust-based or per-user upload quota limit that would either warn staff/admin that a quota was exceeded or prevent further uploading until the quota was increased.

Our support experience I am basing this request for feature discussion is here:

Posts: 6

Participants: 4

Read full topic