Quantcast
Channel: Discourse Meta - Latest topics
Viewing all 60721 articles
Browse latest View live

More nuanced group visibility (based on group membership)

$
0
0

@tophee wrote:

Continuing the discussion from Hidden Group Membership:

How about more than the current four visibility levels? Probably the most frequent use case for this would be to allow group members to apply for membership in sub-groups without having to make those sub-groups public. So let’s say you have a group for all members in an association, then those members (and only those) should be able to see various thematic working groups or what have you, either as a matter of transparency or in order to make it possible for them to join those group. Likewise, those in the board group would be able to see various sub-committee groups etc.

If I’m not mistaken, currently the only way to allow users to apply for membership in a group is to make the group public.

Posts: 2

Participants: 2

Read full topic


Minor glitch in discourse-setup

$
0
0

@tophee wrote:

I noticed that when you run ./discourse-setup again after an initial run, it seems to remember the values entered during the previous run (i.e. email addresses, smtp password etc). But it does not remember the SMTP user name, worse even, it remembers it wrongly.

It neither suggests the value that is actually in the app.yml nor does it resort to the default value (postmaster@discourse.example.com). Instead it seems to construct the suggested address by combining postmaster@ with the forum’s domain (I think).

If your mail domain and your forum domain are the same, there is no problem. But it’s not uncommon to use a specific mail domain for mailgun & co, e.g. mail.mydomain.com. The correct SMTP username in that case is postmaster@mail.mydomain.com (and that is what it says in the app.yml file. But the setup will use postmaster@mydomain.com if your forum is at mydomain.com. (Not sure if it will use postmaster@forum.mydomain.com if the forum is at forum.mydomain.com, but either way it would be wrong.)

Posts: 5

Participants: 3

Read full topic

Rpi 3 cluster / docker swarm / discourse

$
0
0

@acidope wrote:

I just see that we can make a rpi cluster with docker swarm.
Like it’s not possible to make my own selfhosted server with discourse and a single raspberry 3 because discourse need 2 Gb of RAM… is that possible to install discourse on this kind of config? For example with 2 or 4 rpi3?
Is that a function of a cluster?

Posts: 2

Participants: 2

Read full topic

Disk read high in Digital Ocean

[SOLVED] 443 address already in use? Letencrypt

$
0
0

@Oudamseth_Samin wrote:

It used to work before on port 80 with my other website. I don’t remember how I set it up exactly but now I follow guide to setup Let’s encrypt and it only make change to like 3 line and when I run ./launcher rebuild app, I got errors saying that the 443 is already in use???

From google result, they require to turn off that 443 but that 443 is already serve by my main website. Like I’ve mentioned, I used to get the port 80 errors before the let’s encrypt and I don’t remember what I’m doing to fix the problem with dicourse + my website.

Posts: 6

Participants: 3

Read full topic

Clarifications on use of &page

$
0
0

@Mark_Walkom wrote:

First time poster, so forgive me if I am doing this entirely wrong.

I was trying to pull down our users via https://discuss.elastic.co/admin/users/list/all.json?api_key=KEY&api_username=USER which is working fine. However I have two problems when dealing with pagination and I could do with some clarification.

  1. https://discuss.elastic.co/admin/users/list/all.json?api_key=KEY&api_username=USER&page=0 and https://discuss.elastic.co/admin/users/list/all.json?api_key=KEY&api_username=USER&page=1 seem to return the same thing.
  2. https://discuss.elastic.co/admin/users/list/all.json?api_key=KEY&api_username=USER&page=9999999 returns a HTTP 200, but no body, because the page count doesn’t go that high.

I don’t seem to see anything in the response body or headers to indicate what the first/next/last page is. And the docs only say it takes an integer (buts accepts negative ones too).

Appreciative of any guidance that can be offered :slight_smile:

Posts: 1

Participants: 1

Read full topic

Multiple translations for Spanish on Transifex

$
0
0

@Apecengo wrote:

I’ve noticed that there are multiple translations available on Transifex for the Spanish language, each one corresponding to a spanish-speaking country dialect of it (es_ES, es_AR, …), and another one more general (es).

However, when specifying the site locale on settings, I can’t select any country-specific variant, just “Spanish”.

How does it work? Is it possible to specify the country of the Spanish variant or is it automatic based on the broswer locale?

Posts: 2

Participants: 2

Read full topic

Edited default badge names not taking effect after page reload

$
0
0

@jonathon wrote:

I’m not sure if this is a bug or something I’ve missed, but…

Discourse info

Version v1.9.0.beta17 +101
Ubuntu 16.04 (64-bit)
Docker CE 17.12 (overlayfs2)
Bytemark Cloud VPS

What I did

  1. Navigated to /admin/customize/site_texts, then edited the following items:

    • badges.basic.name from “Basic” to “Forum Newbie”
    • badges.member.name from “Member” to “Forum Member”
    • badges.regular.name from “Regular” to “Forum Regular”
    • badges.leader.name from “Leader” to “Forum Leader”
  2. Navigated to /admin/badges, checked updated badge names:

    (screenshot removed due to new user limit on images per post…)

    Then selected each in turn to enable “Allow badge to be used as a title”

  3. Navigate to a users’ profile, edit their Title and select the re-named badge:

    After saving, the new title is initially displayed correctly, but after a page refresh (e.g. F5) it reverts to the original. Clicking again to edit their Title returns me to a blank selection box.

What I’ve tried to make it stick

  • Updated Discourse via /admin/upgrade
  • Stopped Docker, wiped /var/lib/docker/*, started Docker, rebuilt container from scratch (IIRC with the 20171224 base image):
    systemctl stop docker
    rm -fr /var/lib/docker/*
    systemctl start docker
    /var/discourse/launcher rebuild app
    

What I expect

Edited badge names to display as user Titles.

What actually happens

Edited badge names use their default values when used as a user Title.

Posts: 3

Participants: 2

Read full topic


Wizard will not send validation email more than once

$
0
0

@pfaffman wrote:

I had a topic about this once before, but I can’t find it. This is the second time this has happened in the last while, so I’m bringing it up again.

Synopsis: If a new admin user visits the Wizard and creates their admin account but their outgoing email is broken, there is little way for them to ever get logged in.

Steps to reproduce: Visit wizard, set up account and have validation email sent, but have that email not be delivered (e.g., because they hadn’t finished configuring Mailgun).

If you re-visit the site, the Wizard appears because they never validated the account. It would seem like they could try again to use the wizard to send the validation email, but you can’t, it does nothing, and provides not hint that it’s not doing what you think.

The only way to recover is to guess at some url (otherwise, you get only the wizard page), find your way to the login dialog, and then do the “forgot password” sequence.

The likelihood of having your email configuration broken when you first visit the site is fairly high, so it’s not hard to get caught in this trap.

I haven’t noticed this until recently, so I think that the wizard used to send multiple attempts. I’m installing on stable now to see if it’s my imagination.

Edit: I think that Discourse does not send the activation email on subsequent create-the-admin-account, but the “resend activation email” button is there, so people should know to click that.

Posts: 5

Participants: 3

Read full topic

Releasing related topics at the same time

$
0
0

@sjmscott wrote:

Here is a fake scenario that echoes what I’m trying to solve:

I want to write a topic called “Announcing Job Changes.” In this topic I want to link to a topic called Opportunity A and another topic called Opportunity B. I don’t want to post topic A and B before announcing the job changes.

The problem I’m trying to solve is 75% of my users are mailing list. If I post the announcement first, I won’t be able to link to the other posts.

Does anyone have any strategies?

  1. is there any way to set the release time of a topic?
  2. If I created topic A and B in a private category and then moved them to a public category, would the link be the same?

Posts: 2

Participants: 2

Read full topic

A Simple Way to Grant Badges en-masse?

$
0
0

@8BIT wrote:

I was thinking about making a badge for anyone who joined in 2017… is there a simple way to do this that i’m missing?

Posts: 2

Participants: 2

Read full topic

Duplicate http/https topics are randomly created

$
0
0

@spectrum wrote:

Hi there,
I recently transitioned my site from HTTP to HTTPS; all Discourse threads link to their original posts at http://sitename.com/posts/[post number], and with redirects in place it still works great for browsers.

However, we’re seeing some duplicate threads show up somewhat randomly, with original posts linking back to HTTPS links for posts on the homepage. As an example, for a thread created in ~2014 originating from http://sitename.com/posts/243, there’s now a new thread with no replies created, linking back to https://sitename.com/posts/243. I had written the discourseEmbedUrl as http://sitename.com to avoid the system mistakenly creating duplicate threads, but it still seems to do it randomly.

The code I’m using on the template page is here (with substitutions made):

      <script type="text/javascript">
        var discourseUrl = "https://discussion.sitename.com/",
            discourseEmbedUrl = "<?php print 'http://sitename.com/posts/'.$post->postId; ?>";

        (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>

The variables discourseUrl and discourseEmbedUrl differ in HTTP/HTTPS approach because I did not want Discourse to view a post as “new” and re-create it, because of simply being accessed over HTTPS instead of over HTTP. Since browsers get redirected from HTTP to HTTPS, it’s worked thus far except for having random duplicates.

Has anyone else had this issue before? I had thought specifying http://sitename.com instead of https://sitename.com would be clear enough to avoid this issue so Discourse would see there is already a thread created for the post in question, but something seems to be going wrong still.

Is there a different approach I should take so that there aren’t random duplicate threads created?

Posts: 4

Participants: 2

Read full topic

[Paid] CSS specialist

$
0
0

@ked wrote:

What would you like done? I am looking to hire someone who is highly capable with CSS and can specifically apply these skills within my Discourse installation.

When do you need it done? I have work I’d currently like to do, and I am sure there will be work on an hourly and/or project basis in the future.

What is your budget, in $ USD that you can offer for this task? Pay rate will be based on CSS skills, timeliness, responsiveness, and communication skill. We are professionals looking to work with qualified parties, and are happy to pay market pricing for this work.

I will appreciate responses by PM with information on your qualifications and availability. You will hear back from us quickly.

Posts: 1

Participants: 1

Read full topic

Characters Required

Discourse team efficiency

$
0
0

@meglio wrote:

I just went through Discourse Version 1.9 and realized the amount of work being done by a small team of 20 people is enourmus. This of course not even counting the hosting platform you’re running and hundreds of clients you’re supporting.

You guys definitely have an invisible PBD (productivity boost device) shipped to every teammate, and you add ES (efficiency sauce) to every dish you share when you meet.

I think this is an area other teams can learn a lot from you. I know, it all comes from years of experience and is not just a “dos and donts” list; going through reading lists of co-founders will help to understand how it all works. Still, if you can publish a series of blog posts about your PBD and ES ingredients, a lot of people will have something to print out and put on their wallls in front of their desks.

Please share your experience of team-work :heart_eyes:

Posts: 5

Participants: 5

Read full topic


Setup private category for candidate interview process

$
0
0

@jerdog wrote:

I have seen this thread (How to Use Discourse as a Private Support/Ticket System) and it’s not quite in line with the question. So here’s some background:

I am interviewing candidates to join my team at work as essentially Community Engineers (customer-facing, developer-minded engineers to assist the community, but that’s not important here), and we do a technical exercise as part of the process. Typically we would send them some task to do and then send it back to us. However…

Since they’ll be working in our community Discourse all the time, I was thinking about making an exercise which was pretty real to life. The goal would be to have a private category that only they can see and no one else can. We would then copy in sample questions/threads and have them deal with them accordingly.

What I have done is:

  • Created a separate group that auto joins trust level 1
  • Created a specific user for them to login as and locked that level at 1
  • Created a special category that only they can see/reply

I can’t remove that group from being able to see the other categories though - that’s where this whole experiment seems to die. Any ideas?

Posts: 4

Participants: 3

Read full topic

Rate Limit on Single Topic

$
0
0

@frizman21 wrote:

I’m getting a rate limit error on a GET for a single topic through the API. We use discourse in an API-only way, with a Rails app proxying calls and querying data. All the traffic is therefore coming from a single IP. Is there a setting to up this limit? I’m using

Posts: 3

Participants: 3

Read full topic

Admin member count is off on groups page

$
0
0

Discourse docker canot setup

$
0
0

@James_Tan wrote:

after filling up all the information required by discourse-setup, gets this:

Sorry, these containers/app.yml settings aren’t valid – can’t continue!
If you have unusual requirements, edit containers/app.yml and then:
./launcher bootstrap app

Posts: 3

Participants: 3

Read full topic

Docker swarm / compose support

Viewing all 60721 articles
Browse latest View live




Latest Images