@DavidGNavas wrote:

One of the top tech-blog sites in Spain, Hipertextual, have decided to close his posts to comments and subsitute them by a Slack channel

I tweeted to them to recommend Discourse, and one friend asks if Discourse inserts some cookies on the page in the WordPress site...
I think that the plugin only inserts the comments (and a link to go to the discussion), but did you know if it does insert something else?

Posts: 3

Participants: 2

Read full topic

@precessor wrote:

Whilst a series of scripts are provided for forum migration, and recommended as part of the FAQ, performing a migration still requires considerable expertise connecting to the remote database, and/or setting up a local development version of Discourse, or even installing mysql. I propose a simpler process for the end user:

• User uploads their other-forum db backup via the Discourse interface (so no remote db connection)
• User initiates import script, script auto-backups the Discourse, and then runs the import

If the import scripts would provide the option to just look on a local import directory, that would already be a great improvement for ease of use, even if the import scripts are not run via the Discourse UI.

Posts: 6

Participants: 6

Read full topic

@erlend_sh wrote:

Wouldn't it be great if even unregistered users could show some appreciation for your post in the form of our ever so lovely gesture? With the concept of "staged users" introduced by the now-shipped Private Email Support spec, this seems quite doable to me.

It would work similar to the prompt UserVoice presents when an unregistered user tries to vote on a feature:

How it'd work

1. Start showing the Like button even for unregistered users
2. An unregistered user clicking to Like will get a pop-up with two options:
   a. Register to Like
   b. Just enter email. User will not be subscribed to anything.

Posts: 6

Participants: 5

Read full topic

@Nuck wrote:

This is kind of a strange technical bug, but clickOutside() doesn't trigger if the widget you click (outside) has a click() hook.

Reproduction:

1. Open "Post Admin" menu
2. Click "Like" or "Link" button
3. "Post Admin" menu doesn't disappear

What I Expect:

1. Open "Post Admin" menu
2. Click "Like" or "Link" button
3. "Post Admin" menu disappears

I should add that this "expected" behavior is also the behavior when clicking noninteractive elements outside the menu.

The code is likely this early return in the WidgetClickHook, which will trigger for any widget with a click handler, preventing it from reaching the handling for clickOutside below. This should probably trigger clickOutside on any widgets which aren't the widget that you triggered click on or its ancestors, instead.

Posts: 3

Participants: 2

Read full topic

@Ankhamax wrote:

How do I change the name of a badge for the following two badges?

First Emoji

First Mention

I tried to search in the customize >> Text Content section. But I couldn't find it.

Posts: 1

Participants: 1

Read full topic

@louirobert wrote:

I'm on version 1.6.0.beta1. My default site language is set to Chinese zh_CN but I allow user to use their own language setting. It works well for other parts but the text from system_messages.usage_tips.text_body_template, which is still in English, for users who are using the default zh_CN. I tried to set the site language to zh_CN and didn't allow user's own setting on that, then it was right. Thus I guess it's a bug. Any ideas?

---

Update1:

I tried to set the site language to zh_CN and didn't allow user's own setting on that but it still doesn't work. Sorry I was wrong just before.

Update2:
I can repeat the issue on my production deployment but not in my local development environment. They're both v1.6.0.beta1.

Posts: 2

Participants: 2

Read full topic

@DeanMarkTaylor wrote:

Am I completely misunderstanding entirely what these values are for?

I've been using Data Explorer to review activity and noted that topic_users.last_visited_at didn't seem to be updating / showing topics I have recently visited.

Is topic_users.last_visited_at supposed to be updated on every visit to a topic?

Here is the Query I was using with Data Explorer.

-- [params]
-- int :user_id = 1

SELECT
    topic_id,
    last_visited_at,
    first_visited_at
from topic_users
WHERE
    user_id = :user_id
ORDER BY
    topic_users.last_visited_at DESC

When this is executed I see NULL's for topics I have visited and even some I have created:

Pasted image869x230 7.95 KB

Scrolling down further to get to some dates I see:

Pasted image881x212 10.4 KB

Where I have visited each of these topics today 2016-04-07, however it looks like only the first visit was stamped.

So are last_visited_at and first_visited_at updated correctly - or am I just misunderstanding entirely what these values are for?

Is there a timestamp that's updated when a user visits a topic?

Posts: 3

Participants: 2

Read full topic

@fantasticfears wrote:

Existing click tracker is meant to track clicks in a topic. However, plugin authors can't use the library to track clicks anyhow.

In a broader scenario, the link in a topic may shows in the topic list item because plugin authors may found it's useful. Moreover, open as tab is done by this library.

This scenario is required by link plugin: https://github.com/danskdynamit/discourse-links-category : a plugin which allows you to post a link as topic.

PR

PR allows click tracker to accept optional parameters for the case that it doesn't find closet <article>.

Click tracker rewrites a url or sends an xhr to server for tracking clicks. Server requires post_id or topic_id at least. And TopicLinkClick checks the link appears on the topic, otherwise it won't redirect users anyhow.

In the client side, TopicView captures related click event (well, mouseup) if exists a class in the html elements.

Plugin authors still need to capture most relevant events carefully on other views and pass the event to tracker. With the pull request, it will be possible to do so.

Posts: 1

Participants: 1

Read full topic

@gearoid wrote:

Is there a way I can grant some of my users the ability to see forum user's email addresses without assigning other permissions of the moderator or admin ?

Posts: 2

Participants: 2

Read full topic

@Lena wrote:

Hi everyone,

How can I make sure that no one can edit categories or sub-categories?
Thanks for your help

Posts: 8

Participants: 3

Read full topic

@Ankhamax wrote:

I did a backup of my site before I installed the plugin "Topic List Previews" however the installation was unsuccessful and I can't even access my site. Is there anyway that I can restore my site from the backup that I created earlier from terminal app as I can't access the site?

I uploaded clean app.yml file, which is verified as VALID YML file.

It keeps saying FAILED when I tried to rebuilt app with the following command

cd /var/docker
./launcher rebuild app

Ensuring discourse docker is up to date
Fetching origin
Discourse Docker is up-to-date
Stopping old container
+ /usr/bin/docker stop -t 10 app
app
cd /pups && git pull && /pups/bin/pups --stdin
Already up-to-date.
I, [2016-04-07T13:12:59.638922 #37]  INFO -- : Loading --stdin
I, [2016-04-07T13:12:59.657799 #37]  INFO -- : > mkdir -p /shared/postgres_run
I, [2016-04-07T13:12:59.662457 #37]  INFO -- :
I, [2016-04-07T13:12:59.664087 #37]  INFO -- : > chown postgres:postgres /shared/postgres_run
I, [2016-04-07T13:12:59.670683 #37]  INFO -- :
I, [2016-04-07T13:12:59.672528 #37]  INFO -- : > chmod 775 /shared/postgres_run
I, [2016-04-07T13:12:59.681308 #37]  INFO -- :
I, [2016-04-07T13:12:59.683887 #37]  INFO -- : > rm -fr /var/run/postgresql
I, [2016-04-07T13:12:59.690690 #37]  INFO -- :
I, [2016-04-07T13:12:59.693529 #37]  INFO -- : > ln -s /shared/postgres_run /var/run/postgresql
I, [2016-04-07T13:12:59.700144 #37]  INFO -- :
I, [2016-04-07T13:12:59.702802 #37]  INFO -- : > socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1
2016/04/07 13:12:59 socat[45] E connect(4, AF=1 "/shared/postgres_run/.s.PGSQL.5432", 36): No such file or directory
I, [2016-04-07T13:12:59.714697 #37]  INFO -- :
I, [2016-04-07T13:12:59.716867 #37]  INFO -- : > rm -fr /shared/postgres_run/.s*
I, [2016-04-07T13:12:59.723967 #37]  INFO -- :
I, [2016-04-07T13:12:59.726387 #37]  INFO -- : > rm -fr /shared/postgres_run/*.pid
I, [2016-04-07T13:12:59.732756 #37]  INFO -- :
I, [2016-04-07T13:12:59.735259 #37]  INFO -- : > mkdir -p /shared/postgres_run/9.3-main.pg_stat_tmp
I, [2016-04-07T13:12:59.741575 #37]  INFO -- :
I, [2016-04-07T13:12:59.744293 #37]  INFO -- : > chown postgres:postgres /shared/postgres_run/9.3-main.pg_stat_tmp
I, [2016-04-07T13:12:59.750943 #37]  INFO -- :
I, [2016-04-07T13:12:59.761476 #37]  INFO -- : File > /etc/service/postgres/run  chmod: +x
I, [2016-04-07T13:12:59.769827 #37]  INFO -- : File > /etc/runit/3.d/99-postgres  chmod: +x
I, [2016-04-07T13:12:59.778836 #37]  INFO -- : File > /root/upgrade_postgres  chmod: +x
I, [2016-04-07T13:12:59.782416 #37]  INFO -- : > chown -R root /var/lib/postgresql/9.3/main
I, [2016-04-07T13:13:00.326847 #37]  INFO -- :
I, [2016-04-07T13:13:00.327310 #37]  INFO -- : > [ ! -e /shared/postgres_data ] && install -d -m 0755 -o postgres -g postgres /shared/postgres_data && sudo -E -u postgres /usr/lib/postgresql/9.3/bin/initdb -D /shared/postgres_data || exit 0
I, [2016-04-07T13:13:00.330970 #37]  INFO -- :
I, [2016-04-07T13:13:00.331749 #37]  INFO -- : > chown -R postgres:postgres /shared/postgres_data
I, [2016-04-07T13:13:00.361666 #37]  INFO -- :
I, [2016-04-07T13:13:00.362695 #37]  INFO -- : > chown -R postgres:postgres /var/run/postgresql
I, [2016-04-07T13:13:00.367174 #37]  INFO -- :
I, [2016-04-07T13:13:00.368717 #37]  INFO -- : > /root/upgrade_postgres
I, [2016-04-07T13:13:00.377007 #37]  INFO -- :
I, [2016-04-07T13:13:00.378738 #37]  INFO -- : > rm /root/upgrade_postgres
I, [2016-04-07T13:13:00.382257 #37]  INFO -- :
I, [2016-04-07T13:13:00.384302 #37]  INFO -- : Replacing data_directory = '/var/lib/postgresql/9.3/main' with data_directory = '/shared/postgres_data' in /etc/postgresql/9.3/main/postgresql.conf
I, [2016-04-07T13:13:00.386481 #37]  INFO -- : Replacing (?-mix:#?listen_addresses *=.*) with listen_addresses = '*' in /etc/postgresql/9.3/main/postgresql.conf
I, [2016-04-07T13:13:00.387968 #37]  INFO -- : Replacing (?-mix:#?synchronous_commit *=.*) with synchronous_commit = $db_synchronous_commit in /etc/postgresql/9.3/main/postgresql.conf
I, [2016-04-07T13:13:00.389931 #37]  INFO -- : Replacing (?-mix:#?shared_buffers *=.*) with shared_buffers = $db_shared_buffers in /etc/postgresql/9.3/main/postgresql.conf
I, [2016-04-07T13:13:00.392016 #37]  INFO -- : Replacing (?-mix:#?work_mem *=.*) with work_mem = $db_work_mem in /etc/postgresql/9.3/main/postgresql.conf
I, [2016-04-07T13:13:00.394363 #37]  INFO -- : Replacing (?-mix:#?default_text_search_config *=.*) with default_text_search_config = '$db_default_text_search_config' in /etc/postgresql/9.3/main/postgresql.conf
I, [2016-04-07T13:13:00.397727 #37]  INFO -- : > install -d -m 0755 -o postgres -g postgres /shared/postgres_backup
I, [2016-04-07T13:13:00.403875 #37]  INFO -- :
I, [2016-04-07T13:13:00.405215 #37]  INFO -- : Replacing (?-mix:#?max_wal_senders *=.*) with max_wal_senders = $db_max_wal_senders in /etc/postgresql/9.3/main/postgresql.conf
I, [2016-04-07T13:13:00.407397 #37]  INFO -- : Replacing (?-mix:#?wal_level *=.*) with wal_level = $db_wal_level in /etc/postgresql/9.3/main/postgresql.conf
I, [2016-04-07T13:13:00.409789 #37]  INFO -- : Replacing (?-mix:#?checkpoint_segments *=.*) with checkpoint_segments = $db_checkpoint_segments in /etc/postgresql/9.3/main/postgresql.conf
I, [2016-04-07T13:13:00.411867 #37]  INFO -- : Replacing (?-mix:#?logging_collector *=.*) with logging_collector = $db_logging_collector in /etc/postgresql/9.3/main/postgresql.conf
I, [2016-04-07T13:13:00.414036 #37]  INFO -- : Replacing (?-mix:#?log_min_duration_statement *=.*) with log_min_duration_statement = $db_log_min_duration_statement in /etc/postgresql/9.3/main/postgresql.conf
I, [2016-04-07T13:13:00.419999 #37]  INFO -- : Replacing (?-mix:^#local +replication +postgres +peer$) with local replication postgres  peer in /etc/postgresql/9.3/main/pg_hba.conf
I, [2016-04-07T13:13:00.421992 #37]  INFO -- : Replacing (?-mix:^host.*all.*all.*127.*$) with host all all 0.0.0.0/0 md5 in /etc/postgresql/9.3/main/pg_hba.conf
I, [2016-04-07T13:13:00.423953 #37]  INFO -- : > HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/9.3/bin/postmaster -D /etc/postgresql/9.3/main
I, [2016-04-07T13:13:00.452980 #37]  INFO -- : > sleep 5
2016-04-07 13:13:00 UTC [69-1] LOG:  database system was shut down at 2016-04-07 12:56:59 UTC
2016-04-07 13:13:00 UTC [69-2] LOG:  MultiXact member wraparound protections are now enabled
2016-04-07 13:13:00 UTC [66-1] LOG:  database system is ready to accept connections
2016-04-07 13:13:00 UTC [73-1] LOG:  autovacuum launcher started
I, [2016-04-07T13:13:05.463961 #37]  INFO -- :
I, [2016-04-07T13:13:05.465053 #37]  INFO -- : > su postgres -c 'createdb discourse' || true
2016-04-07 13:13:05 UTC [78-1] postgres@postgres ERROR:  database "discourse" already exists
2016-04-07 13:13:05 UTC [78-2] postgres@postgres STATEMENT:  CREATE DATABASE discourse;

createdb: database creation failed: ERROR:  database "discourse" already exists
I, [2016-04-07T13:13:05.553175 #37]  INFO -- :
I, [2016-04-07T13:13:05.554051 #37]  INFO -- : > su postgres -c 'psql discourse -c "create user discourse;"' || true
2016-04-07 13:13:05 UTC [89-1] postgres@discourse ERROR:  role "discourse" already exists
2016-04-07 13:13:05 UTC [89-2] postgres@discourse STATEMENT:  create user discourse;
ERROR:  role "discourse" already exists
I, [2016-04-07T13:13:05.620490 #37]  INFO -- :
I, [2016-04-07T13:13:05.621525 #37]  INFO -- : > su postgres -c 'psql discourse -c "grant all privileges on database discourse to discourse;"' || true
I, [2016-04-07T13:13:05.689727 #37]  INFO -- : GRANT

I, [2016-04-07T13:13:05.690759 #37]  INFO -- : > su postgres -c 'psql discourse -c "alter schema public owner to discourse;"'
I, [2016-04-07T13:13:05.751776 #37]  INFO -- : ALTER SCHEMA

I, [2016-04-07T13:13:05.752741 #37]  INFO -- : > su postgres -c 'psql template1 -c "create extension if not exists hstore;"'
NOTICE:  extension "hstore" already exists, skipping
I, [2016-04-07T13:13:05.827553 #37]  INFO -- : CREATE EXTENSION

I, [2016-04-07T13:13:05.828642 #37]  INFO -- : > su postgres -c 'psql template1 -c "create extension if not exists pg_trgm;"'
NOTICE:  extension "pg_trgm" already exists, skipping
I, [2016-04-07T13:13:05.897043 #37]  INFO -- : CREATE EXTENSION

I, [2016-04-07T13:13:05.898402 #37]  INFO -- : > su postgres -c 'psql discourse -c "create extension if not exists hstore;"'
NOTICE:  extension "hstore" already exists, skipping
I, [2016-04-07T13:13:05.971137 #37]  INFO -- : CREATE EXTENSION

I, [2016-04-07T13:13:05.971980 #37]  INFO -- : > su postgres -c 'psql discourse -c "create extension if not exists pg_trgm;"'
NOTICE:  extension "pg_trgm" already exists, skipping
I, [2016-04-07T13:13:06.032009 #37]  INFO -- : CREATE EXTENSION

I, [2016-04-07T13:13:06.033483 #37]  INFO -- : > sudo -u postgres psql discourse
I, [2016-04-07T13:13:06.036669 #37]  INFO -- : update pg_database set encoding = pg_char_to_encoding('UTF8') where datname = 'discourse' AND encoding = pg_char_to_encoding('SQL_ASCII');

I, [2016-04-07T13:13:06.125869 #37]  INFO -- : File > /var/lib/postgresql/take-database-backup  chmod: +x
I, [2016-04-07T13:13:06.131517 #37]  INFO -- : File > /var/spool/cron/crontabs/postgres  chmod:
I, [2016-04-07T13:13:06.132832 #37]  INFO -- : > echo postgres installed!
I, [2016-04-07T13:13:06.135861 #37]  INFO -- : postgres installed!

I, [2016-04-07T13:13:06.143046 #37]  INFO -- : File > /etc/service/redis/run  chmod: +x
I, [2016-04-07T13:13:06.147207 #37]  INFO -- : File > /etc/runit/3.d/10-redis  chmod: +x
I, [2016-04-07T13:13:06.148022 #37]  INFO -- : Replacing daemonize yes with  in /etc/redis/redis.conf
I, [2016-04-07T13:13:06.149225 #37]  INFO -- : Replacing (?-mix:^pidfile.*$) with  in /etc/redis/redis.conf
I, [2016-04-07T13:13:06.150465 #37]  INFO -- : > install -d -m 0755 -o redis -g redis /shared/redis_data
I, [2016-04-07T13:13:06.153201 #37]  INFO -- :
I, [2016-04-07T13:13:06.153860 #37]  INFO -- : Replacing (?-mix:^logfile.*$) with logfile "" in /etc/redis/redis.conf
I, [2016-04-07T13:13:06.155232 #37]  INFO -- : Replacing (?-mix:^dir .*$) with dir /shared/redis_data in /etc/redis/redis.conf
I, [2016-04-07T13:13:06.156578 #37]  INFO -- : > echo redis installed
I, [2016-04-07T13:13:06.158645 #37]  INFO -- : redis installed

I, [2016-04-07T13:13:06.159522 #37]  INFO -- : > /usr/local/bin/ruby -e 'if ENV["DISCOURSE_SMTP_ADDRESS"] == "smtp.example.com"; puts "Aborting! Mail is not configured!"; exit 1; end'
I, [2016-04-07T13:13:06.222739 #37]  INFO -- :
I, [2016-04-07T13:13:06.223604 #37]  INFO -- : > /usr/local/bin/ruby -e 'if ENV["DISCOURSE_HOSTNAME"] == "discourse.example.com"; puts "Aborting! Domain is not configured!"; exit 1; end'
I, [2016-04-07T13:13:06.291279 #37]  INFO -- :
I, [2016-04-07T13:13:06.297151 #37]  INFO -- : File > /etc/runit/1.d/copy-env  chmod: +x
I, [2016-04-07T13:13:06.301808 #37]  INFO -- : File > /etc/runit/1.d/ensure-web-nginx-read  chmod: +x
I, [2016-04-07T13:13:06.306289 #37]  INFO -- : File > /etc/service/unicorn/run  chmod: +x
I, [2016-04-07T13:13:06.310982 #37]  INFO -- : File > /etc/service/nginx/run  chmod: +x
I, [2016-04-07T13:13:06.315465 #37]  INFO -- : File > /etc/runit/3.d/01-nginx  chmod: +x
I, [2016-04-07T13:13:06.320023 #37]  INFO -- : File > /etc/runit/3.d/02-unicorn  chmod: +x
I, [2016-04-07T13:13:06.320479 #37]  INFO -- : Replacing # postgres with sv start postgres || exit 1 in /etc/service/unicorn/run
I, [2016-04-07T13:13:06.321758 #37]  INFO -- : > exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf
I, [2016-04-07T13:13:06.328126 #37]  INFO -- : > cd /var/www/discourse && git reset --hard
194:M 07 Apr 13:13:06.338 * Redis 3.0.6 (00000000/0) 64 bit, standalone mode, port 6379, pid 194 ready to start.
194:M 07 Apr 13:13:06.338 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
194:M 07 Apr 13:13:06.338 # Server started, Redis version 3.0.6
194:M 07 Apr 13:13:06.338 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
194:M 07 Apr 13:13:06.339 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
194:M 07 Apr 13:13:06.422 * DB loaded from disk: 0.083 seconds
194:M 07 Apr 13:13:06.423 * The server is now ready to accept connections on port 6379
I, [2016-04-07T13:13:07.515459 #37]  INFO -- : HEAD is now at 13e1bf8 Merge pull request #4023 from dandv/patch-1

I, [2016-04-07T13:13:07.515650 #37]  INFO -- : > cd /var/www/discourse && git clean -f
I, [2016-04-07T13:13:07.545681 #37]  INFO -- :
I, [2016-04-07T13:13:07.546174 #37]  INFO -- : > cd /var/www/discourse && git remote set-branches --add origin master
I, [2016-04-07T13:13:07.553736 #37]  INFO -- :
I, [2016-04-07T13:13:07.553925 #37]  INFO -- : > cd /var/www/discourse && git pull
From https://github.com/discourse/discourse
   13e1bf8..3d4cdd7  master     -> origin/master
 * [new branch]      add_host_to_nginx_log -> origin/add_host_to_nginx_log
   35d6e64..d61fcbb  beta       -> origin/beta
 * [new branch]      flexheader -> origin/flexheader
 * [new branch]      like-badges -> origin/like-badges
   9f56d61..aa91e4c  stable     -> origin/stable
 * [new branch]      tableheader -> origin/tableheader
   13e1bf8..2ecff60  tests-passed -> origin/tests-passed
   e848ea5..03068e3  vdom       -> origin/vdom
 * [new tag]         v1.5.0     -> v1.5.0
 * [new tag]         v1.4.6     -> v1.4.6
 * [new tag]         v1.4.7     -> v1.4.7
 * [new tag]         v1.5.0.beta11 -> v1.5.0.beta11
 * [new tag]         v1.5.0.beta12 -> v1.5.0.beta12
 * [new tag]         v1.5.0.beta13 -> v1.5.0.beta13
 * [new tag]         v1.5.0.beta13b -> v1.5.0.beta13b
 * [new tag]         v1.5.0.beta14 -> v1.5.0.beta14
 * [new tag]         v1.6.0.beta1 -> v1.6.0.beta1
I, [2016-04-07T13:13:24.960236 #37]  INFO -- : Updating 13e1bf8..3d4cdd7
Fast-forward
 1669 files changed, 39318 insertions(+), 33997 deletions(-)

I, [2016-04-07T13:13:24.961182 #37]  INFO -- : > cd /var/www/discourse && git fetch origin tests-passed
From https://github.com/discourse/discourse
 * branch            tests-passed -> FETCH_HEAD
I, [2016-04-07T13:13:28.699175 #37]  INFO -- :
I, [2016-04-07T13:13:28.700500 #37]  INFO -- : > cd /var/www/discourse && git checkout tests-passed
Switched to a new branch 'tests-passed'
I, [2016-04-07T13:13:29.010282 #37]  INFO -- : Branch tests-passed set up to track remote branch tests-passed from origin.

I, [2016-04-07T13:13:29.010459 #37]  INFO -- : > cd /var/www/discourse && mkdir -p tmp/pids
I, [2016-04-07T13:13:29.013684 #37]  INFO -- :
I, [2016-04-07T13:13:29.013928 #37]  INFO -- : > cd /var/www/discourse && mkdir -p tmp/sockets
I, [2016-04-07T13:13:29.016610 #37]  INFO -- :
I, [2016-04-07T13:13:29.016763 #37]  INFO -- : > cd /var/www/discourse && touch tmp/.gitkeep
I, [2016-04-07T13:13:29.020106 #37]  INFO -- :
I, [2016-04-07T13:13:29.020547 #37]  INFO -- : > cd /var/www/discourse && mkdir -p                    /shared/log/rails
I, [2016-04-07T13:13:29.023488 #37]  INFO -- :
I, [2016-04-07T13:13:29.023648 #37]  INFO -- : > cd /var/www/discourse && bash -c "touch -a           /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr}.log"
I, [2016-04-07T13:13:29.028027 #37]  INFO -- :
I, [2016-04-07T13:13:29.028484 #37]  INFO -- : > cd /var/www/discourse && bash -c "ln    -s           /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr}.log /var/www/discourse/log"
I, [2016-04-07T13:13:29.032781 #37]  INFO -- :
I, [2016-04-07T13:13:29.032977 #37]  INFO -- : > cd /var/www/discourse && bash -c "mkdir -p           /shared/{uploads,backups}"
I, [2016-04-07T13:13:29.037350 #37]  INFO -- :
I, [2016-04-07T13:13:29.037557 #37]  INFO -- : > cd /var/www/discourse && bash -c "ln    -s           /shared/{uploads,backups} /var/www/discourse/public"
I, [2016-04-07T13:13:29.044369 #37]  INFO -- :
I, [2016-04-07T13:13:29.044547 #37]  INFO -- : > cd /var/www/discourse && chown -R discourse:www-data /shared/log/rails /shared/uploads /shared/backups
I, [2016-04-07T13:13:29.050409 #37]  INFO -- :
I, [2016-04-07T13:13:29.050917 #37]  INFO -- : Replacing # redis with sv start redis || exit 1 in /etc/service/unicorn/run
I, [2016-04-07T13:13:29.052795 #37]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/docker_manager.git
Cloning into 'docker_manager'...
I, [2016-04-07T13:13:37.957704 #37]  INFO -- :
I, [2016-04-07T13:13:37.960429 #37]  INFO -- : > cp /var/www/discourse/config/nginx.sample.conf /etc/nginx/conf.d/discourse.conf
I, [2016-04-07T13:13:37.968777 #37]  INFO -- :
I, [2016-04-07T13:13:37.969837 #37]  INFO -- : > rm /etc/nginx/sites-enabled/default
I, [2016-04-07T13:13:37.973925 #37]  INFO -- :
I, [2016-04-07T13:13:37.974658 #37]  INFO -- : > mkdir -p /var/nginx/cache
I, [2016-04-07T13:13:37.978178 #37]  INFO -- :
I, [2016-04-07T13:13:37.979228 #37]  INFO -- : Replacing pid /run/nginx.pid; with daemon off; in /etc/nginx/nginx.conf
I, [2016-04-07T13:13:37.980407 #37]  INFO -- : Replacing (?m-ix:upstream[^\}]+\}) with upstream discourse { server 127.0.0.1:3000; } in /etc/nginx/conf.d/discourse.conf
I, [2016-04-07T13:13:37.981526 #37]  INFO -- : Replacing (?-mix:server_name.+$) with server_name _ ; in /etc/nginx/conf.d/discourse.conf
I, [2016-04-07T13:13:37.982550 #37]  INFO -- : Replacing (?-mix:client_max_body_size.+$) with client_max_body_size $upload_size ; in /etc/nginx/conf.d/discourse.conf
I, [2016-04-07T13:13:37.983886 #37]  INFO -- : > echo "done configuring web"
I, [2016-04-07T13:13:37.986329 #37]  INFO -- : done configuring web

I, [2016-04-07T13:13:37.988007 #37]  INFO -- : > cd /var/www/discourse && gem update bundler
ERROR:  While executing gem ... (Gem::RemoteFetcher::UnknownHostError)
    no such name (https://api.rubygems.org/specs.4.8.gz)
I, [2016-04-07T13:13:43.394943 #37]  INFO -- : Updating installed gems

I, [2016-04-07T13:13:43.396171 #37]  INFO -- : Terminating async processes
I, [2016-04-07T13:13:43.396329 #37]  INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/9.3/bin/postmaster -D /etc/postgresql/9.3/main pid: 66
2016-04-07 13:13:43 UTC [66-2] LOG:  received fast shutdown request
2016-04-07 13:13:43 UTC [66-3] LOG:  aborting any active transactions
2016-04-07 13:13:43 UTC [73-2] LOG:  autovacuum launcher shutting down
2016-04-07 13:13:43 UTC [70-1] LOG:  shutting down
I, [2016-04-07T13:13:43.402942 #37]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 194
194:signal-handler (1460034823) Received SIGTERM scheduling shutdown...
2016-04-07 13:13:43 UTC [70-2] LOG:  database system is shut down
194:M 07 Apr 13:13:43.475 # User requested shutdown...
194:M 07 Apr 13:13:43.476 * Saving the final RDB snapshot before exiting.
194:M 07 Apr 13:13:43.605 * DB saved on disk
194:M 07 Apr 13:13:43.605 # Redis is now ready to exit, bye bye...


FAILED
--------------------
RuntimeError: cd /var/www/discourse && gem update bundler failed with return #<Process::Status: pid 284 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:105:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"web", "cmd"=>["gem update bundler", "chown -R discourse $home"]}
50a6d1ca4e22de3ddbc46d24e025c6731c074f94b70474701f717e8fb9818725
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one

Any help is greatly appreciated.

Posts: 6

Participants: 2

Read full topic

@Robert_Weissgraeber wrote:

Hi,

I'm using the hosted discourse installation, and have configured the google oauth2 settings.

The callback url called from google is setup correctly, but then gives the user a 502 on discourse.

Regards,
Robert

Posts: 2

Participants: 2

Read full topic

@lulzsecd wrote:

When I upload image such as set avatar, cover image, when 100%, nothing happen and I can't upload image, please help me resolve

Posts: 2

Participants: 2

Read full topic

@Bluedevil wrote:

I'm setting up a new forum and one thing I've found odd so far is that pinning and closing topics both count as replies.

While I understand that closing a topic is a kind of response to a topic, it is not a reply like typing a response is and generates a false sense of activity.

Is there a way for this to be disabled (so such mod actions don't count)?

Posts: 2

Participants: 2

Read full topic

@iva wrote:

Continuing the discussion from Setup incoming emails :

Has anyone measured the effect of the "reply via email" feature on user engagement, when it is enabled in a previously web-only community?

On the one hand, it can be expected to increase -- since "reply via email" offers another, often easier means to contribute to a discussion. On the other hand, I wouldn't be totally surprised if there was a negative effect, too -- because of fewer visits to the site and, consequently, fewer opportunities to discover other interesting topics to contribute to.

So, I'm interested if anyone has been through enabling the "reply via email" on a previously web-only forum, and what were the results. Thank you.

Posts: 1

Participants: 1

Read full topic

@iva wrote:

Continuing the discussion from Notify on every like should be the default:

Any thoughts about adding this feature? I have a previous experience with it in a bbPress-based forum, and it boosted the engagement when we enabled it. Now we've migrated to Discourse and would like to see it here too.

We could possibly add it ourselves and then submit a PR, or perhaps someone is already working on this?

Posts: 2

Participants: 2

Read full topic

@michaeld wrote:

It's still possible to lock yourself out of the forum by checking the disable_emails setting and then misconfiguring SSO or disabling logins, since /users/admin-login doesn't send emails either.

It would be handy if /users/admin-login would ignore the disable_emails setting

Posts: 2

Participants: 2

Read full topic

@Kyle_C wrote:

I installed Discourse per the instructions on github on a box with Ubuntu 15.04. Everything executed successfully however I did not purchase a domain name so I put my IP in the hostname field. Even after getting a success message when running "/.launcher start app" the IP refuses my connection. I'm worndering if it is okay for me to have used my IP as the hostname or if it must be different? I am perfectly happy with navigating to an IP rather than domain name.

Posts: 1

Participants: 1

Read full topic

@stevenpslade wrote:

I have been exploring the UserProfileViews model and the User controller hoping to find out exactly how this feature works. I get the basics of how it's sending the current user's id and the profile's user id to the DB but what triggers saying, "Hey, this user is on this profile!"

Is it as simple as, this user just went to user/anotheruser/activity? If so, where is this reflected in the code?

Posts: 2

Participants: 2

Read full topic

@stevenpslade wrote:

I am trying to change the default view of profile from /activity to /summary.

The route sending users to profile is /users/:username/ which is most commonly used for the avatar drop-down link to the profile and also the user badge card when click on a user avatar anywhere in Discourse.

For the the user badge card, it is a this.transitionTo('userActivity'); in app/javascript/discourse/routes/user-index.js.es6. As a hack I was going to change the transitionTo to /users/my/summary/.

However, it seems as though this change does not effect the avatar drop-down nav route (which is still users/:username but for some reason still redirects to /users/:username/activity/.

Thoughts on a better way to do this or how to change all routes of /users/:username/ to redirect to /summary?

Posts: 1

Participants: 1

Read full topic