No member-accessible list of a user's group memebership



  • Since my the report was deemed too unimportant to warrant even living over on meta.d (it was deleted without comment,) reproducing here, since it is still relevant because what little UI there was has been removed:

    I notice that group membership has disappeared from cards and the header on profile pages - is there a page listing which groups a member is in?

    I know the /groups/$GROUPNAME url exists, but I'm after member-accessible "which groups is this member in", not "which members are in this group"



  • @PJH said:

    the report was deemed too unimportant to warrant even living over on meta.d (it was deleted without comment,)

    *sigh* JDGI



  • The commit's even broken, he left a hanging {{/if}}.

    Clearly did not test.



  • @PJH said:

    is there a page listing which groups a member is in?

    /users/{username}.json...


  • BINNED

    @riking said:

    The commit's even broken, he left a hanging {{/if}}.

    Clearly did not test.

    And Handlebars parse that? mustache.js screams bloody murder at that and refuses to budge until you fix it.



  • @Onyx said:

    And Handlebars parsed that?

    @riking said:

    Clearly did not test.


  • BINNED

    Ah, ok, it magled a partial then I'd assume. Because I get zero output when using mustache and have a non-matching tag, not just something that gets malformed.



  • @Maciejasjmj said:

    /users/{username}.json...

    Uh huh. Easily readable, accessible and discoverable for members...

    I was more after a sensible replacement for what used to be on both the user cards and the user's profile page.... :)



  • @PJH said:

    Easily readable, accessible and discoverable for members.

    Exactly what I was thinking, too, especially the readability.



  • @HardwareGeek said:

    Exactly what I was thinking, too, especially the readability.

    Well.. it's so long...



  • Formatted, it's not so bad, but when I ask Chrome for that, it displays it without any formatting, which is just a tad harder to read.


  • BINNED

    @PJH said:

    Uh huh. Easily readable, accessible and discoverable for members...

    Yup. It's fun. Where do you think I got the post count and badge count for the userscript I made?

    Also, post count is action_type = 5. Because... LOGIC!



  • Use chklaanhfefbnpoihckbnefhakgolnmc.



  • STATUS: FIXED, REGRESSION

    eviltrout [10:52 AM]
    I'm crazy but we used to show groups on user profiles didn't we
    yes we did! knew I wasn't crazy

    kris [10:52 AM]
    oh yeah, I forgot that I added them back to the usercard (which are gone now) and not the full profiles

    eviltrout [10:53 AM]
    yeah Jeff wanted them off the card I think, but on the profile

    eviltrout [10:53 AM]
    adding em back



  • Well, since you're here @riking, and I now have a DC instance up and running with Docker and @sam's docker_manager, what's the favoured development environment this week?

    ###docker_manager

    I'm fairly certain working in the docker container isn't a good idea if you're going to run anything involving the equivalent of launcher bootstrap (rebuild e.g.)

    I'd also assume updating discourse via docker_manger wouldn't be too healthy on any local changes made to /var/www/discourse in the container.

    ###vagrant
    The Vagrant doc doesn't appear to have been touched for 7 months, indicating it's out of date. (Most fo the vagrant threads seem to be of a similar vintage if the search results are anything to go by.)



  • I was working with Ruby directly installed on my laptop, but that's broken now for some weird reason. MiniProfiler is complaining that it's being loaded twice. Vagrant is hellishly slow on linux. But you're on Windows, right? So you'll need to use Vagrant.

    What you'll want to do is mount a share from the VM to your computer and edit the files that way. It's faster like that.



  • @riking said:

    Vagrant is hellishly slow on linux. But you're on Windows, right?

    No. Linux.



  • Okay, here's my setup right now, on Ubuntu 14.10 using systemd (install the systemd-sysv package to switch):

    1. rbenv installed with ruby-2.1.3 built from source

    2. gem, bundler, pry installed in rbenv (make sure to rbenv rehash after installing gem)

    3. redis-server and postgresql-9.4 postgresql-9.4-contrib packages

    4. systemctl mask postgresql@9.4-main.service - disable the package-shipped systemd unit file

    5. /etc/systemd/system/postgresql.service:

      [Unit]
      Description=PostgreSQL 9.4 database server
      After=network.target
      
      [Service]
      Type=forking
      TimeoutSec=120
      User=postgres
      Group=postgres
      
      Environment=PGROOT=/var/lib/postgres
      
      SyslogIdentifier=postgres
      PIDFile=/var/lib/postgres/data/postmaster.pid
      
      ExecStartPre=/usr/local/bin/postgresql-check-db-dir ${PGROOT}/data
      ExecStart= /usr/lib/postgresql/9.4/bin/pg_ctl -s -D ${PGROOT}/data start -w -t 120
      ExecReload=/usr/lib/postgresql/9.4/bin/pg_ctl -s -D ${PGROOT}/data reload
      ExecStop=  /usr/lib/postgresql/9.4/bin/pg_ctl -s -D ${PGROOT}/data stop -m fast
      
      # Due to PostgreSQL's use of shared memory, OOM killer is often overzealous in
      # killing Postgres, so adjust it downward
      OOMScoreAdjust=-200
      
      [Install]
      WantedBy=multi-user.target
      
    6. https://projects.archlinux.org/svntogit/packages.git/tree/trunk/postgresql-check-db-dir?h=packages/postgresql installed at /usr/local/bin/postgresql-check-db-dir

    7. systemctl disable postgresql redis-server - want to start these manually when I need to work with Discourse

    8. update.sh file in ~/projects/discourse, run whenever I pull master:

      #!/bin/bash
      bundle install
      pkexec systemctl start postgresql redis-server
      bundle exec rake db:migrate
      RAILS_ENV=test bundle exec rake db:migrate
      
    9. pkexec policy to allow that command without password


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.