@Marcos_Conceicao wrote:

I'm trying to create users via api, but returning error 500 and this log

NoMethodError (undefined method downcase' for nil:NilClass) /var/www/discourse/app/controllers/users_controller.rb:280:increate'

Posts: 1

Participants: 1

Read full topic

@MLModel wrote:

Does Discourse have any search capabilities beyond a single word? In particular, is there anyway to search for a phrase? Also, any + or – features? Restrict to topic title?

Posts: 2

Participants: 2

Read full topic

@techAPJ wrote:

I just pushed a commit that adds a button (visible only to admins) to admin wrench to make a topic public or private message.

Convert public topic to private message:

fdd6c95a-10aa-11e6-8959-b742d45b05bb.png510x778 31.2 KB

Small action post indicating that public topic is converted to private message:

15c66ca0-10ab-11e6-95c1-e2f3f492996a.png1554x130 4.73 KB

Convert private message to public topic:

2a1b9f8a-10ac-11e6-8d1e-ebc34501cc3c.png490x626 25.3 KB

Small action post indicating that private message is converted to public topic:

31519e08-10ac-11e6-896e-b965c68107ca.png1548x124 4.57 KB

Posts: 15

Participants: 7

Read full topic

@tobiaseigen wrote:

I just discovered a handful of log entries for emails that were not delivered to discourse. This is the error apparently returned to users:

Email can not be processed: Sorry, new users can only put 2 links in a post.

I just changed this setting to 9999 (or should I have left it blank?) to prevent this from happening in the future.

However, now I have all these emails going back a few months that never made it to discourse. Is there a recommended way to process the messages again?

Posts: 3

Participants: 2

Read full topic

@tobiaseigen wrote:

I have a group of 70+ trusted members who I'd like to give TL1 privileges and a title. I see it's possible to set it up to set the trust level and title for new members as they are added to the group, but this does not appear to affect existing group members. Is there a way to retroactively process these members?

I'd be grateful for any guidance.

Below is how the group is set up now.

Screen Shot 2016-05-03 at 2.33.32 PM.png1278x640 62.8 KB

Posts: 2

Participants: 2

Read full topic

@BaButtons wrote:

This might be a noob question, but is there somewhere where I can configure the domain that canonical URLs are built from? In my case, I have the forum hosted on forum.example.com but with a reverse proxy pointing to example.com/forum. However, my canonical URLs still start with forum.example.com, and I'd like to fix that.

Posts: 3

Participants: 2

Read full topic

@Dmitry_Krasnoperov wrote:

I've just put my favorite command

./launcher rebuild app

but it reply me with

ERROR: Docker version 1.7.1 not supported, please upgrade to at least 1.8.0, or recommended 1.8.0

how to make things happens as I'm editing my SMTP settings at the moment

Posts: 17

Participants: 10

Read full topic

@DeanMarkTaylor wrote:

You can probably ignore me...
... but just to say that this bothers me.

Note the flattening of the top and right of smaller logo.

This might be due to the logo size being non-square (350x349) being used in a square position.

Posts: 1

Participants: 1

Read full topic

@Cody_Deeran wrote:

Hey guys,

the keyboard short cuts for editing and reporting.

Posts: 5

Participants: 4

Read full topic

@jesselperry wrote:

I just noticed my Discourse sent out 2 emails to the same person, about the same reply. The first email was because it was a reply to the topic originator, as a user_posted email. Then 2 minutes later, a user_mentioned email was sent because in that same post, they were @ mentioned. This seems like a bug/not intended.

Is there something I should look into to see if this is just me?

Posts: 2

Participants: 2

Read full topic

@tarek wrote:

Continuing the discussion from OAuth2 Basic Support:

I will use this thread to document my steps and progress in integrating Discourse and Drupal via OAuth2.

At present, the status of my implementation is NOT WORKING. The error is that the callback appears to fail with a blank screen.

Installation on Discourse:
For installation on Discourse, do the following:

1. Install OAuth2 Basic plugin as per this thread. See Install a plugin for details on how to install a plugin

2. Configure OAuth2 plugin:

   • You should see an "OAuth2" section in "Login" in Settings when logged in as an administrative user.
   • Enable "Custom OAuth2 is enabled"
   • Set client ID as "discourse".
   • Create a client secret that is a random series of letters and numbers. You can use apg -a 0 -m 20 to generate one.
   • Set oauth2 authorize url: https://DRUPAL/oauth2/authorize where DRUPAL = your Drupal site's base URL
   • Set oauth2 token url: https://DRUPAL/oauth2/token
   • Set oauth2 user json url: https://DRUPAL/oauth2/user/profile
   • Leave other fields blank and save all fields.

When you hit 'login', you should now see a 'login with OAuth2' option.

Installation on Drupal

1. Install the following plugins:
   • OAuth2 Login Provider
   • OAuth2 Server
   • Services
   • REST Server

2. Add client at /oauth2-servers/manage/oauth2/clients

   • Call the client discourse
   • Enter the same client secret as above
   • Set Redirect URIs as http://DISCOURSE/auth/oauth2_basic/callback where DISCOURSE = your discourse forum's base URL

Status and Known Issues:
If you follow the steps above, you should see a "with OAuth2" badge on the login screen. Clicking on it should redirect you to your Drupal site for login that asks "Authorize discourse to use your account?" Clicking "Yes" results in:

a blank page with the following link: http://DISCOURSE/auth/oauth2_basic/callback?code=9n55b3b96abd08e31b80cd5ar08ad49eb38a6e40&state=2a0586dfa2d0bb492ed8761dc999fec5cf7a0e604adcgc92

If this page is reloaded, the following error is given:
Sorry, there was an error authorizing your account. Perhaps you did not approve authorization?

In DISCOURSE logs, the following error appears:
OpenURI::HTTPError (404 Not found : Could not find the controller.)
/usr/local/lib/ruby/2.0.0/open-uri.rb:353:in 'open_http'

In the DRUPAL system's apache logs, the following error appears:
DRUPAL x.x.x.x - - [04/May/2016:00:19:42 -0000] "GET /oauth2/user/profile HTTP/1.1" 404 4382 "-" "Ruby"

I will keep this posted as I get closer to a solution!

I have filed a related bug regarding the callback 404 with the hopes of some clarification from the module developers.

tarek : )

Posts: 2

Participants: 2

Read full topic

@snakeninny wrote:

Hi,

Thanks for your amazing work on Discourse but I'm having some problems randomly:

Screen Shot 2016-05-04 at 12.30.35 PM.png764x156 13.6 KB

There doesn't seem to be any error details for me to debug so I have to seek for help at here. Thanks!

BTW, the site is http://iosre.com

snakeninny

Posts: 2

Participants: 2

Read full topic

@luisfpinto wrote:

Hello, I have installed discourse with docker and I have been looking for the routes.rb file to change the endpoint to email processing as It is said here https://meta.discourse.org/t/simple-plugin-that-offers-an-http-post-endpoint-to-mailgun-or-any-other-mail-service/37001/2

However, I can not find the directory where is that file. Can you please help me to manage this problem?

Thank you in advance

Posts: 3

Participants: 2

Read full topic

@calmh wrote:

Discourse uses ImageMagic here and there, IIRC - for processing uploaded avatar images among other things? Is it vulnerable to CVE-2016–3714 ("ImageTragick") or has that been handled?

Posts: 8

Participants: 4

Read full topic

@darix wrote:

Continuing the discussion from ImageMagick CVE-2016–3714:

currently it is part of the docker image for people not using docker it would be easier to pick up from the base repository.

Posts: 9

Participants: 4

Read full topic

@Nataraj wrote:

Hi ,

How to display an End User License Arrangement to the newly registered users i.e need to make the users agree our EULA after they login for the first time .

Posts: 1

Participants: 1

Read full topic

@louirobert wrote:

To delete a topic, Discourse makes a request like:

DELETE http://example.com/t/123

However my CDN doesn't support DELETE method, but only GET, HEAD, POST, and OPTIONS. I remember that Rails can make a POST request instead of DELETE by adding a "_method" request variable. So how can I config Discourse to do that?

BTW, my CDN is a kind of "smart" CDN that I just tell it my domain name and do some config on DNS without settings on Discourse part and it will speed my site by caching small files like images and css automatically. So in a word, all client requests, including the DELETE one, go through the CDN server first. Then the CDN server decides to return cached files directly or to go further to my original server next.

Posts: 1

Participants: 1

Read full topic

@pjv wrote:

I'm moving my forum from one host to another. I have a fresh instance of discourse (docker) set up on the new host and I can log in and admin etc.

I've moved the most recent backup from the current forum to the new host and when I try to restore the backup I get the following:

[2016-05-04 16:42:41]   Current version: 20160427202222
[2016-05-04 16:42:42]   Restored version: 20160405172827
...
[2016-05-04 16:42:54] Migrating the database...
[2016-05-04 16:42:54] EXCEPTION:

No migration with version number 20160427202222


[2016-05-04 16:42:54] /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/migration.rb:952:in `migrate'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/migration.rb:823:in `up'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/migration.rb:807:in `migrate'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/tasks/database_tasks.rb:137:in `migrate'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/railties/databases.rake:44:in `block (2 levels) in <top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.5.0/lib/rake/task.rb:240:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.5.0/lib/rake/task.rb:240:in `block in execute'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.5.0/lib/rake/task.rb:235:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.5.0/lib/rake/task.rb:235:in `execute'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.5.0/lib/rake/task.rb:179:in `block in invoke_with_call_chain'
/usr/local/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.5.0/lib/rake/task.rb:172:in `invoke_with_call_chain'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.5.0/lib/rake/task.rb:165:in `invoke'
/var/www/discourse/lib/backup_restore/restorer.rb:259:in `migrate_database'
/var/www/discourse/lib/backup_restore/restorer.rb:51:in `run'
/var/www/discourse/lib/backup_restore/backup_restore.rb:161:in `block in start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:158:in `fork'
/var/www/discourse/lib/backup_restore/backup_restore.rb:158:in `start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:17:in `restore!'
/var/www/discourse/app/controllers/admin/backups_controller.rb:80:in `restore'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/abstract_controller/base.rb:198:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/rendering.rb:10:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:117:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:117:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:505:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:505:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:778:in `_run_process_action_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/notifications.rb:164:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/notifications.rb:164:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/abstract_controller/base.rb:137:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.2.6/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.9.2/lib/mini_profiler/profiling_methods.rb:102:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal.rb:237:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb:74:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb:74:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb:43:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/mapper.rb:49:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/journey/router.rb:43:in `block in serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/journey/router.rb:30:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/journey/router.rb:30:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb:817:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/builder.rb:63:in `call'
/var/www/discourse/config/initializers/008-rack-cors.rb:15:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/conditionalget.rb:38:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/head.rb:13:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:129:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/flash.rb:260:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:225:in `context'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/cookies.rb:560:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:653:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:88:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:778:in `_run_call_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-1.2.2/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.6/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.6/lib/rails/rack/logger.rb:22:in `call'
/var/www/discourse/config/initializers/100-quiet_logger.rb:10:in `call_with_quiet_assets'
/var/www/discourse/config/initializers/100-silence_logger.rb:26:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/methodoverride.rb:22:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/runtime.rb:18:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/sendfile.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.9.2/lib/mini_profiler/profiler.rb:281:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-2.0.0.beta.5/lib/message_bus/rack/middleware.rb:60:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:73:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.6/lib/rails/engine.rb:518:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.6/lib/rails/application.rb:165:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.6/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.6/lib/rails/railtie.rb:194:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/urlmap.rb:66:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/lib/unicorn/http_server.rb:562:in `process_client'
/var/www/discourse/lib/scheduler/defer.rb:85:in `process_client'
/var/www/discourse/lib/middleware/unicorn_oobgc.rb:95:in `process_client'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/lib/unicorn/http_server.rb:658:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/lib/unicorn/http_server.rb:508:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/lib/unicorn/http_server.rb:132:in `start'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/bin/unicorn:126:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:22:in `load'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:22:in `<main>'
[2016-05-04 16:42:54] Trying to rollback...
[2016-05-04 16:42:54] Rolling back...
[2016-05-04 16:42:55] Notifying 'sysadmin' of the end of the restore...
[2016-05-04 16:42:55] Cleaning stuff up...
[2016-05-04 16:42:55] Removing tmp '/var/www/discourse/tmp/restores/default/2016-05-04-164234' directory...
[2016-05-04 16:42:55] Unpausing sidekiq...
[2016-05-04 16:42:55] Disabling readonly mode...
[2016-05-04 16:42:55] Marking restore as finished...
[2016-05-04 16:42:55] Finished!

I have read these two similar topics but found no solution for me:

The version of discourse that I am trying to restore from: 1.5.1. The version I am trying to restore to: 1.5.1. Immediately prior to the restore I did ./launcher rebuild app on the target.

I have three added plugins in app.yml for both source and target:
- git clone https://github.com/discourse/docker_manager.git
- git clone https://github.com/discourse/discourse-data-explorer.git
- git clone https://github.com/discourse/discourse-akismet.git

If the problem has to do with plugin migrations, how can I get past it?

Posts: 6

Participants: 3

Read full topic

@cpradio wrote:

Okay, so I'm a bit confused. When I visit http://bbs.boingboing.net/about, I notice they have 10 admins listed. Now I'm sure there are more that have admin access, but they are not shown on the about page, such as @codinghorror.

Unfortunately, the same isn't true for our instance. Or any of the test instances I've installed. I know you can hide names using CSS, but BoingBoing isn't doing that, the data isn't returned in the json, so somehow they are stripping it out before it gets serialized and sent to the client.

So how does one tell the about page to not show those users? What setting(s) am I missing?

I've found the following topics, but none of them explain how the JSON output is missing said users.

https://meta.discourse.org/t/can-i-hide-an-admin/34504
https://meta.discourse.org/t/show-real-names-on-about-page-and-enable-hiding-of-users/25135

Granted, maybe my assumption at BoingBoing is incorrect and @codinghorror isn't an admin but that doesn't explain http://bbs.boingboing.net/groups/admins/members

Posts: 7

Participants: 3

Read full topic

@DeanMarkTaylor wrote:

It's possible to raise a "500 Internal Server Error" by bookmarking / removing the bookmark from a post.

Whilst:

• it doesn't happen all the time
• it might have been a momentary issue
• I have experienced similar on a local instance in the past.

I wanted to report this in case there is something that can be found in the error logs.

#bug is not the best category for this - but closest match.

In the screenshot the following sequence caused the error:

Steps

1. Open topic
2. Navigate to post via keyboard k
3. Within 4 seconds
   • Bookmark b
   • Unbookmark b
   • Bookmark b
   • Unbookmark b

Actual Result

Pasted image1733x1024 151 KB

Posts: 6

Participants: 3

Read full topic