@knittingtoday wrote:

How do I troubleshoot when my blog post isn’t publishing to Discourse despite the checkbox being checked?

Posts: 4

Participants: 3

Read full topic

@martinduparc wrote:

I encountered a bug yesterday when trying to reply (via email) to a new message posted email notification.

Here is what I think happened:

• User A creates topic.
• User B posts reply.
• User A gets email notification about user B’s reply.
• User B deletes their reply (we were testing at that time)
• User A replies to User B’s message via email.
• Email fails to deliver (undefined method topic).

Discourse might get confused about the notification about a now deleted message.

Posts: 3

Participants: 2

Read full topic

@jj11909 wrote:

I can’t seem to find an option to notify administrators of unanswered posts. More so, how can I advise moderators that a post has gone X hours without a response?

Posts: 5

Participants: 2

Read full topic

@cdrobison wrote:

We are using Discourse internally to facilitate communication between developers, QA and project managers. We use categories to separate out discussions into the respective large projects or teams we have. We use tags to signify which JIRA ticket the topic/question is related to. It’s super useful, for us at least, to go to /tags/{tag_name} to see all the discussion happening on a particular issue. But, we’ve found that tags that don’t exist show a view “This page does not exist…” We think it would be a useful feature to show a “Be the first to post…” type view instead so that tags URL can be more portable to those who want to just focus on discussion in a particular tag.

Posts: 2

Participants: 2

Read full topic

@Sujan wrote:

I am active as a moderator in a tech, Javascript framework, focused discourse. Naturally, we don’t only have discussions about architecture and the deeper meaning of code syntax, but lots of very basic questions and topics. Lots of the posts also have with bad formatting, missing information etc.

The workflow for these topics as a moderator mainly is making the topic title and category somehow relevant to the actual question and asking for all the required information (version numbers, command executed, command output…).

After a bit of time you come back and have lots of replies to your initial replies that you then follow up to and do it all over again until you start discussing the actual problem, suggest solutions, wait for the result, again, etc. until finally a) your reply is ignored and the asked for information never comes or b) the user replies that it worked and he is happy now

(So basically normal support ticket or Github issue flow )

Do you have any ideas how to optimize such a moderator workflow?

---

Right now my routine looks a bit like this:

1. Handle Flags and Spam
2. Skim new topics for crass abuse and fix it, also replace some things we don’t want in titles (unrelevant version numbers)
3. Open “Unread” and open them all to reply
4. Back to big topic list and skim for specific problems I am an expert for, reply
5. GOTO 3

One of the optimizations already in place is that I use a bookmarklet to open 10 topics of any list in new tabs at the same time. As I go through all “Unread” anyway this makes sense.

Posts: 2

Participants: 2

Read full topic

@codechef wrote:

I have an existing Discourse community with existing users. I added custom user fields that I need to update from an external source. I created and tested a .rb script in a local development environment. I’d now like to run that script against the production instance. Production environment is a self-hosted docker install at Digital Ocean.

I now need help with the following two (N00b) tasks:

1. How do I copy the .rb file into the docker container from the host server?
2. How do I execute the .rb file within the docker container?

I plan to take a backup of the production Discourse just before executing the script incase ‘bad things happen’.

Alternatively, am I better to use backup/restore to execute the script locally, then restore that to production? Just not wild about the downtime required for this approach.

Thanks for the help!

Posts: 3

Participants: 2

Read full topic

@pfaffman wrote:

I’ve got a client who can’t change the security settings on a category because it’s “pre-seeded”. I see that #staff is pre-seeded, but they seem to have a staff category. And there is also an uncategorized.

I can’t figure out what he did to accomplish this.

Posts: 10

Participants: 3

Read full topic

@donlucas wrote:

Trying to add a member to a group and not finding a solution in the meta forums.
(using python’s requests module)

requests.put('https://my.discourse.com/groups/the_group/members.json', data='{"usernames": "newForumUser", "api_key": "theGeneratedAPIKeyForUserNamedanAdmin", "api_username": "anAdmin"}', headers={"Content-Type":"application/json"}

I get a 403 Forbidden response from the server. The api_username is a site admin. If I try the command using curl:

curl -X POST "https://my.discourse.com/groups/the_group/members.json" -H "Content-Type: multipart/form-data;" -F "api_key=theGeneratedAPIKeyForUserNamedanAdmin" -F "api_username=anAdmin" -F "usernames=newForumUser"

the html returned is Oops! That page doesn’t exist or is private.

I must be missing something obvious from http://docs.discourse.org?

Posts: 9

Participants: 3

Read full topic

@mdxdave wrote:

I’ve tried to update from Version v1.9.0.beta4 +300 to 1.9.0.beta5 by pulling the latest changes (git pull) and try to rebuild the app (./launcher rebuild app), but the migration failed with the following message:

Any fix?

I, [2017-08-11T05:43:33.644343 #15]  INFO -- : > cd /var/www/discourse && su dis                                                                 course -c 'bundle exec rake db:migrate'
2017-08-11 05:43:38.795 UTC [399] discourse@discourse ERROR:  duplicate key valu                                                                 e violates unique constraint "schema_migration_details_pkey"
2017-08-11 05:43:38.795 UTC [399] discourse@discourse DETAIL:  Key (id)=(629) al                                                                 ready exists.
2017-08-11 05:43:38.795 UTC [399] discourse@discourse STATEMENT:        INSERT I                                                                 NTO schema_migration_details(
                version,
                hostname,
                name,
                git_version,
                duration,
                direction,
                rails_version,
                created_at
              ) values (
                20170609115401,
                '3f1727b6fec9
        ',
                'AddExtensionToTopicLinks',
                'f2539a86d06b29b2b85eb734fdc9571959c17b1b',
                40,
                'up',
                '4.2.9',
                '2017-08-11 05:43:38.794188'
              )

rake aborted!
StandardError: An error has occurred, this and all later migrations canceled:

PG::UniqueViolation: ERROR:  duplicate key value violates unique constraint "sch                                                                 ema_migration_details_pkey"
DETAIL:  Key (id)=(629) already exists.
:       INSERT INTO schema_migration_details(
        version,
        hostname,
        name,
        git_version,
        duration,
        direction,
        rails_version,
        created_at
      ) values (
        20170609115401,
        '3f1727b6fec9
',
        'AddExtensionToTopicLinks',
        'f2539a86d06b29b2b85eb734fdc9571959c17b1b',
        40,
        'up',
        '4.2.9',
        '2017-08-11 05:43:38.794188'
      )
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.5/lib/p                                                                 atches/db/pg.rb:90:in `async_exec'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.5/lib/p                                                                 atches/db/pg.rb:90:in `async_exec'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/postgresql/database_statements.rb:155:in `block in exe                                                                 cute'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/abstract_adapter.rb:484:in `block in log'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_                                                                 support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/abstract_adapter.rb:478:in `log'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/postgresql/database_statements.rb:154:in `execute'
/var/www/discourse/lib/freedom_patches/schema_migration_details.rb:44:in `exec_m                                                                 igration'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:592:in `block (2 levels) in migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:591:in `block in migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/abstract/connection_pool.rb:292:in `with_connection'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:590:in `migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:768:in `migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:1023:in `block in execute_migration_in_transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:1069:in `block in ddl_transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/abstract/database_statements.rb:213:in `block in trans                                                                 action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/abstract/transaction.rb:184:in `within_new_transaction                                                                 '
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/abstract/database_statements.rb:213:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/transactions.rb:220:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:1069:in `ddl_transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:1022:in `execute_migration_in_transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:984:in `block in migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:980:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:980:in `migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:823:in `up'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:801:in `migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/tasks/database_tasks.rb:139:in `migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/railties/databases.rake:44:in `block (2 levels) in <top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rake-12.0.0/exe/rake:27:in `<to                                                                 p (required)>'
/usr/local/bin/bundle:22:in `load'
/usr/local/bin/bundle:22:in `<main>'
ActiveRecord::RecordNotUnique: PG::UniqueViolation: ERROR:  duplicate key value                                                                  violates unique constraint "schema_migration_details_pkey"
DETAIL:  Key (id)=(629) already exists.
:       INSERT INTO schema_migration_details(
        version,
        hostname,
        name,
        git_version,
        duration,
        direction,
        rails_version,
        created_at
      ) values (
        20170609115401,
        '3f1727b6fec9
',
        'AddExtensionToTopicLinks',
        'f2539a86d06b29b2b85eb734fdc9571959c17b1b',
        40,
        'up',
        '4.2.9',
        '2017-08-11 05:43:38.794188'
      )
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.5/lib/p                                                                 atches/db/pg.rb:90:in `async_exec'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.5/lib/p                                                                 atches/db/pg.rb:90:in `async_exec'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/postgresql/database_statements.rb:155:in `block in exe                                                                 cute'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/abstract_adapter.rb:484:in `block in log'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_                                                                 support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/abstract_adapter.rb:478:in `log'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/postgresql/database_statements.rb:154:in `execute'
/var/www/discourse/lib/freedom_patches/schema_migration_details.rb:44:in `exec_m                                                                 igration'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:592:in `block (2 levels) in migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:591:in `block in migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/abstract/connection_pool.rb:292:in `with_connection'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:590:in `migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:768:in `migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:1023:in `block in execute_migration_in_transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:1069:in `block in ddl_transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/abstract/database_statements.rb:213:in `block in trans                                                                 action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/abstract/transaction.rb:184:in `within_new_transaction                                                                 '
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/abstract/database_statements.rb:213:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/transactions.rb:220:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:1069:in `ddl_transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:1022:in `execute_migration_in_transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:984:in `block in migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:980:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:980:in `migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:823:in `up'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:801:in `migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/tasks/database_tasks.rb:139:in `migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/railties/databases.rake:44:in `block (2 levels) in <top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rake-12.0.0/exe/rake:27:in `<to                                                                 p (required)>'
/usr/local/bin/bundle:22:in `load'
/usr/local/bin/bundle:22:in `<main>'
PG::UniqueViolation: ERROR:  duplicate key value violates unique constraint "sch                                                                 ema_migration_details_pkey"
DETAIL:  Key (id)=(629) already exists.
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.5/lib/p                                                                 atches/db/pg.rb:90:in `async_exec'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.5/lib/p                                                                 atches/db/pg.rb:90:in `async_exec'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/postgresql/database_statements.rb:155:in `block in exe                                                                 cute'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/abstract_adapter.rb:484:in `block in log'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_                                                                 support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/abstract_adapter.rb:478:in `log'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/postgresql/database_statements.rb:154:in `execute'
/var/www/discourse/lib/freedom_patches/schema_migration_details.rb:44:in `exec_m                                                                 igration'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:592:in `block (2 levels) in migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:591:in `block in migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/abstract/connection_pool.rb:292:in `with_connection'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:590:in `migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:768:in `migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:1023:in `block in execute_migration_in_transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:1069:in `block in ddl_transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/abstract/database_statements.rb:213:in `block in trans                                                                 action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/abstract/transaction.rb:184:in `within_new_transaction                                                                 '
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/connection_adapters/abstract/database_statements.rb:213:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/transactions.rb:220:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:1069:in `ddl_transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:1022:in `execute_migration_in_transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:984:in `block in migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:980:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:980:in `migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:823:in `up'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/migration.rb:801:in `migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/tasks/database_tasks.rb:139:in `migrate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_r                                                                 ecord/railties/databases.rake:44:in `block (2 levels) in <top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rake-12.0.0/exe/rake:27:in `<to                                                                 p (required)>'
/usr/local/bin/bundle:22:in `load'
/usr/local/bin/bundle:22:in `<main>'
Tasks: TOP => db:migrate
(See full trace by running task with --trace)
I, [2017-08-11T05:43:38.833122 #15]  INFO -- : == 20170609115401 AddExtensionToT                                                                 opicLinks: migrating =========================
-- add_column(:topic_links, :extension, :string, {:limit=>10})
   -> 0.0006s
-- add_index(:topic_links, :extension)
   -> 0.0395s

I, [2017-08-11T05:43:38.833423 #15]  INFO -- : Terminating async processes
I, [2017-08-11T05:43:38.833489 #15]  INFO -- : Sending INT to HOME=/var/lib/post                                                                 gresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgr                                                                 es:ssl-cert /usr/lib/postgresql/9.5/bin/postmaster -D /etc/postgresql/9.5/main p                                                                 id: 44
I, [2017-08-11T05:43:38.833548 #15]  INFO -- : Sending TERM to exec chpst -u red                                                                 is -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 157
2017-08-11 05:43:38.833 UTC [44] LOG:  received fast shutdown request
2017-08-11 05:43:38.833 UTC [44] LOG:  aborting any active transactions
157:signal-handler (1502430218) Received SIGTERM scheduling shutdown...
2017-08-11 05:43:38.835 UTC [51] LOG:  autovacuum launcher shutting down
2017-08-11 05:43:38.836 UTC [48] LOG:  shutting down
157:M 11 Aug 05:43:38.860 # User requested shutdown...
157:M 11 Aug 05:43:38.860 * Saving the final RDB snapshot before exiting.
157:M 11 Aug 05:43:38.930 * DB saved on disk
157:M 11 Aug 05:43:38.930 # Redis is now ready to exit, bye bye...
2017-08-11 05:43:39.331 UTC [48] LOG:  database system is shut down


FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:m                                                                 igrate' failed with return #<Process::Status: pid 381 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su d                                                                 iscourse -c 'bundle install --deployment --verbose --without test --without deve                                                                 lopment'", "su discourse -c 'bundle exec rake db:migrate'", "su discourse -c 'bu                                                                 ndle exec rake assets:precompile'"]}
3f1727b6fec9e30bde95e2a47c13e710204c52f8a934e8181455be57985faa3a
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages,                                                                  there may be more than one

Posts: 6

Participants: 2

Read full topic

@MattCHM wrote:

We had PrimeTime WP Discourse SSO plugin in place on our Wordpress install to handle the SSO to our Discourse forum and that was working apart from redirecting the user back to the Wordpress site on logout. To fix this I tried updating to WP-Discourse 1.43. The Wordpress site is the SSO Provider.

Since that whenever I try to access Discourse the page gets stuck in a redirect loop. At first it gets stuck at
https://www.mydomain.com/?sso=bm9uY2U9NDk3NzQ5MmY4M2Q2MmVjNjRjOTM...&sig=2ec83b391a3cecd44d9123563a237d7f881...
(… being the rest of the string)

Refreshing the page again will get to:
https://forum.mydomain.com/session/sso_login?sso=bm9uY2U9NDk3NzQ5MmY4M2Q2MmVjN...&sig=2ec83b391a3cecd44d9123563a237d7f88132d0d...
But we get the message Login Error. Account login timed out, please try logging in again.

I’ve tried deactivating WP-Discourse and reactivating PrimeTime WP Discourse SSO without any success. We are using the MemberPress plugin on Wordpress which does have a custom login page, but this problem occurs even when that is deactivated. We haven’t changed any of the Discourse settings other than getting an API key. Now I can’t login there to make changes. Disabling SSO on Discourse as per instructions here:
WP Discourse plugin installation and setup
Seems to disable the SSO requirement but the login form presented on Discourse has no fields.

Screen Shot 2017-08-11 at 4.45.47 PM.jpg892x380 5.65 KB

Hope someone can offer some advice.

Posts: 1

Participants: 1

Read full topic

@Bas wrote:

After installing an unrelated plugin and rebuilding, the Discourse login page completely broke (i.e. blank page).

This was caused by a javascript error in _plugin-third-pary-(...).js, see screenshot below.

The offending line was in styleguide-route-map; disabling the styleguide plugin fixed the error.

That’s all I have, wish I could be of more help

Screenshot:

Screen Shot 2017-08-11 at 14.38.17.png2748x1452 572 KB

List of my current plugins:

        cmd:
          - mkdir -p plugins
          - git clone https://github.com/discourse/docker_manager.git
          - git clone https://github.com/vinkas0/discourse-navigation.git
          - git clone https://github.com/vinkas0/discourse-branding.git
          - git clone https://github.com/discourse/discourse-solved.git
          - git clone https://github.com/discourse/discourse-data-explorer.git
#          - git clone https://github.com/discourse/discourse-styleguide.git
          - git clone https://github.com/pmusaraj/discourse-sidebar-blocks.git
          - git clone https://github.com/discourse/discourse-staff-notes.git
#          - git clone https://github.com/scossar/discourse-blog-post.git
          - git clone https://github.com/binaryage/discourse-hipchat-plugin.git
#          - git clone https://github.com/mlamarque/algoliasearch-discourse.git

Posts: 4

Participants: 2

Read full topic

@Sujan wrote:

These are my two “Canned Replies” I use trying to get people to format their code as “Preformatted text” when they post code snippets, error messages or command line output. I use these a lot:

1. If I already changed their post via my moderator powers:

I changed your post to format your code or error message correctly. Please use the </> button above the post input field to format your code or error message or wrap it in ``` (“code fences”) manually. This will make sure your text is readable and if it recognizes the programming language it also automatically adds code syntax highlighting. Thanks.

2. If I want them to change it themselves (7th post with unformatted code, obviously unreadable and they should have noticed by themselves):

Please edit your post, it is not very readable at the moment.
Use the </> button above the input field to format your code, command line output or error message (select the text first, then click the button or wrap it in ``` manually). Check the preview if it looks better. This will make sure your text is readable and if it recognizes the programming language it also automatically adds code syntax highlighting. Thanks.

Any ideas or suggestions for improvements?

Posts: 1

Participants: 1

Read full topic

@ChrisBeach wrote:

Version: v1.9.0.beta5 +119 (latest as of 11th Aug)

Steps to reproduce:

1. Spanner > “Set Topic Timer”
2. “Close Temporarily”
3. “When” > “Pick Date and Time”
4. Select time a minute into the future (I have tried with longer times)
5. Wait a minute

Expected

Topic reopens, with an action message automatically posted to say the topic has re-opened

Actual

Topic remains closed:

Screen Shot 2017-08-11 at 15.28.40.png1546x124 9.07 KB

Posts: 1

Participants: 1

Read full topic

@awb715 wrote:

Has anyone redesigned the user profile pages? I would like to use discourse and make it a blend of a forum AND social network.

Posts: 3

Participants: 2

Read full topic

@barreeeiroo wrote:

I’m trying to rebuild Discourse with ./launcher rebuild app but I get the following error:

FAILED
--------------------
Pups::ExecError: cd /var/www/discourse/plugins && git clone https://github.com/discourse/docker_manager.git failed with return #<Process::Status: pid 260 exit 128>
Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn'
exec failed with the params {"cd"=>"/var/www/discourse/plugins", "cmd"=>["git clone https://github.com/discourse/docker_manager.git", "git clone https://github.com/discourse/docker_manager.git", "git clone https://github.com/davidtaylorhq/discourse-whos-online.git", "git clone https://github.com/discourse/discourse-translator.git", "git clone https://github.com/discourse/discourse-solved.git", "git clone https://github.com/discourse/discourse-cakeday.git", "git clone https://github.com/discourse/discourse-assign.git", "git clone https://github.com/xfalcox/discourse-signatures.git", "git clone https://github.com/discourse/discourse-push-notifications.git", "git clone https://github.com/discourse/discourse-staff-notes.git", "git clone https://github.com/vinkas0/discourse-branding.git", "git clone https://github.com/discourse/discourse-presence.git", "git clone https://github.com/discourse/discourse-voting.git", "git clone https://github.com/Ebsy/discourse-nationalflags.git", "git clone https://github.com/discourse/discourse-adplugin.git", "git clone https://github.com/sekhat/discourse-yuml.git", "git clone https://github.com/davidtaylorhq/discourse-telegram-notifications.git", "git clone https://github.com/discourse/discourse-chat-integration.git"]}
9989d6efc0cc514dcd63e4ce0141b175b4094abca671622878b2faf176a1d403
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one

Any idea of what can it be causing?

Posts: 6

Participants: 2

Read full topic

@ron_jeremy wrote:

Hey Discourse Team,

What are the chances you could implement a security feature that requires one to re-enter their password to enter the Admin panel?

• Good idea
• Ni hablar, senior

0 voters

Show results

Posts: 1

Participants: 1

Read full topic

@RBoy wrote:

Of late after an upgrade I’ve seen a whole bunch of errors in the logs like

ActionDispatch::RemoteIp::IpSpoofAttackError (IP spoofing attack?! HTTP_CLIENT_IP=“74.103.19.54” HTTP_X_FORWARDED_FOR=“138.164.23.59, 46.166.148.34”)
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/remote_ip.rb:125:in `calculate_ip’

I couldn’t find anything on the discussion forum so I googled it and found this:

Am wondering if cellphone users are being impacted by this Rails IP check and if there’s some way to turn it off for discourse?

Posts: 1

Participants: 1

Read full topic

@Massimo_Redaelli wrote:

I have a small program that daily does some work on the groups of my Discourse installation, and to do that it starts by fetching all the groups using the json API:

GET https://disc.uaar.it/admin/groups.json?api_key=xxxx&api_username=xxx

Suddenly a few days ago this call stopped working. Now I get a 200 response code (the login is OK, and there is no error in the logs), but the response is empty and its content type is text/plain.

I’m running v1.9.0.beta5 +8, but I cannot check if this happened at the same time as an upgrade, because the system admin is on vacation

Any thoughs?

Posts: 2

Participants: 2

Read full topic

@Fsantiago wrote:

Centos 7
Self hosted discourse run thru docker
Current version
I have 127.0.0.1 as my first DNS followed by public ones; I run pdns-recursor for my loopback entry.

Attempting to run git pull on discourse works fine.

Then run rebuild app and receive this:

cd /pups && git pull && /pups/bin/pups --stdin
fatal: unable to access 'https://github.com/SamSaffron/pups.git/': Could not resolve host: github.com
518cdc4fe87305081463e693d5cffd0a2477ff2e986b2f75fd6c65ca28dbda5e
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one

Is it in fact my dns setup?

Posts: 1

Participants: 1

Read full topic

@Stranik wrote:

Hello!

There is a small offer. But I think it will be useful to many. Because Saw a lot of topics here.

File widgets/post.js.es6

There just add:

An additional class will appear, which any administrator can use as you like.

Demo

Posts: 3

Participants: 2

Read full topic