@codmakr wrote:

Today i have again multiple 500 error. In my logs i only find this two Messages:

ActionView::Template::Error (Discourse::InvalidAccess) /var/www/discourse/lib/auth/default_current_user_provider.rb:56:in `rescue in current_user'

Log ActionView Template Error


/var/www/discourse/lib/auth/default_current_user_provider.rb:56:in `rescue in current_user' /var/www/discourse/lib/auth/default_current_user_provider.rb:53:in `current_user' /var/www/discourse/lib/current_user.rb:30:in `current_user' /var/www/discourse/app/helpers/application_helper.rb:69:in `html_classes' /var/www/discourse/app/views/layouts/application.html.erb:2:in `_app_views_layouts_application_html_erb__1310886151707264257_70161281874620' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/template.rb:145:in `block in render' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/notifications.rb:166:in `instrument' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/template.rb:333:in `instrument' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/template.rb:143:in `render' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/lib/mini_profiler/profiling_methods.rb:76:in `block in profile_method' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/renderer/template_renderer.rb:66:in `render_with_layout' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/renderer/template_renderer.rb:52:in `render_template' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/renderer/template_renderer.rb:14:in `render' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/renderer/renderer.rb:46:in `render_template' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/renderer/renderer.rb:27:in `render' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/rendering.rb:100:in `_render_template' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/streaming.rb:217:in `_render_template' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/rendering.rb:83:in `render_to_body' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rendering.rb:32:in `render_to_body' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/renderers.rb:37:in `render_to_body' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/abstract_controller/rendering.rb:43:in `render_to_string' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rendering.rb:21:in `render_to_string' /var/www/discourse/app/controllers/application_controller.rb:525:in `build_not_found_page' /var/www/discourse/app/controllers/application_controller.rb:139:in `rescue_discourse_actions' /var/www/discourse/app/controllers/application_controller.rb:122:in `block in <class:ApplicationController>' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/rescuable.rb:112:in `instance_exec' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/rescuable.rb:112:in `block in handler_for_rescue' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/rescuable.rb:80:in `rescue_with_handler' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rescue.rb:15:in `rescue_with_handler' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rescue.rb:32:in `rescue in process_action' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rescue.rb:29:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/notifications.rb:164:in `block in instrument' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/notifications/instrumenter.rb:20:in `instrument' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/notifications.rb:164:in `instrument' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/instrumentation.rb:30:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/params_wrapper.rb:250:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/railties/controller_runtime.rb:18:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/abstract_controller/base.rb:137:in `process' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/rendering.rb:30:in `process' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/lib/mini_profiler/profiling_methods.rb:76:in `block in profile_method' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal.rb:196:in `dispatch' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal.rb:237:in `block in action' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/routing/route_set.rb:74:in `dispatch' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/routing/route_set.rb:43:in `serve' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/journey/router.rb:43:in `block in serve' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/journey/router.rb:30:in `each' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/journey/router.rb:30:in `serve' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/routing/route_set.rb:817:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/builder.rb:63:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/conditionalget.rb:38:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.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.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/params_parser.rb:27:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/flash.rb:260:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:225:in `context' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:220:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/cookies.rb:560:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/query_cache.rb:36:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:653:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:88:in `__run_callbacks__' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:778:in `_run_call_callbacks' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:81:in `run_callbacks' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/callbacks.rb:27:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/remote_ip.rb:78:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/logster-1.2.5/lib/logster/middleware/reporter.rb:31:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/rack/logger.rb:38:in `call_app' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/rack/logger.rb:22:in `call' /var/www/discourse/config/initializers/100-quiet_logger.rb:13:in `call_with_quiet_assets' /var/www/discourse/config/initializers/100-silence_logger.rb:26:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/request_id.rb:21:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/methodoverride.rb:22:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/runtime.rb:18:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/sendfile.rb:113:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/lib/mini_profiler/profiler.rb:171:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus/rack/middleware.rb:62:in `call' /var/www/discourse/lib/middleware/request_tracker.rb:73:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/engine.rb:518:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/application.rb:165:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/railtie.rb:194:in `public_send' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/railtie.rb:194:in `method_missing' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/urlmap.rb:66:in `block in call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `each' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.1.0/lib/unicorn/http_server.rb:562:in `process_client' /var/www/discourse/lib/scheduler/defer.rb:85:in `process_client' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.1.0/lib/unicorn/http_server.rb:658:in `worker_loop' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.1.0/lib/unicorn/http_server.rb:508:in `spawn_missing_workers' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.1.0/lib/unicorn/http_server.rb:132:in `start' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.1.0/bin/unicorn:126:in `<top (required)>' /var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:23:in `load' /var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:23:in `<main>'


Maybe someone can help me in this case.

Posts: 2

Participants: 1

Read full topic

@mrded wrote:

I'm trying to create a Permalink with forums/general-discussion url pointing to a Category.

Then I try to access it - it gives me an error:

AbstractController::ActionNotFound at /forums/general-discussion
The action 'show' could not be found for ForumsController

The problem is with routers:

Discourse::Application.routes.draw do
  ...
  resources :forums
  ...
end

it processes all /forums/* requests.

I made a pull request here https://github.com/discourse/discourse/pull/4517

Posts: 7

Participants: 2

Read full topic

@pfaffman wrote:

Continuing the discussion from Not able to create a permalink with forums/* address:

IPB has topic links like:

https://host/{slug}-{topic-id}t/

That's done.

There are also post links like

 https://host/{slug}-{TOPIC-ID}t/?do=findComment&comment={post-id}

and

https://host/{slug}-{TOPIC-ID}t/#comment-{post-id}

Last I checked, it didn't seem possible to make permalinks like the latter. I haven't tried the former, but I'm thinking that won't work either. My current solution is to use Nginx rewrite rules to just remove the comment stuff so that those links will just fall back to the topic (rather than the post).

Am I missing something?

Posts: 1

Participants: 1

Read full topic

@gkln wrote:

Hi,

We manage a video games community and users can set in their profile the username they use on various platform. I would like to build an external web page that summarizes which users play on which platform and under what name.

I know there is an API endpoint to get information about a user:

GET /users/:username.json

But we have to know his username and the custom fields in the response are just ids, for example:

"user_fields":{"6":"toto","8":"titi","7":""}

Is there a way for an external service to query custom fields with their title for all users?

Thanks!

Posts: 1

Participants: 1

Read full topic

@ljpp wrote:

It's almost Halloween, so one of our moderators made this little easter egg (or halloween pumpkin) for our community. Just find a fitting image file and copy this to your Customization/CSS area.

Ours is live for a few days at Tappara.co

.spinner {
  -webkit-animation: pulse 700ms infinite linear;
  -moz-animation: pulse 700ms infinite linear;
  -ms-animation: pulse 700ms infinite linear;
  animation: pulse 700ms infinite linear;
  width: 120px;
  height: 120px;
  background-image: url("https://your-pumpkin-goes-here.png");
  border: none;
  margin: 50px auto;
}
@-webkit-keyframes pulse {
  from {
    -webkit-transform: scale3d(0.6, 0.6, 0.6);
  }
  50% {
    -webkit-transform: scale3d(1.0, 1.0, 1.0);
  }
  to {
    -webkit-transform: scale3d(0.6, 0.6, 0.6);
  }
}
@-moz-keyframes pulse {
  from {
    -moz-transform: scale3d(0.6, 0.6, 0.6);
  }
  50% {
    -moz-transform: scale3d(1.0, 1.0, 1.0);
  }
  to {
    -moz-transform: scale3d(0.6, 0.6, 0.6);
  }
}
@-o-keyframes pulse {
  from {
    -o-transform: scale3d(0.6, 0.6, 0.6);
  }
  50% {
    -o-transform: scale3d(1.0, 1.0, 1.0);
  }
  to {
    -o-transform: scale3d(0.6, 0.6, 0.6);
  }
}
@-ms-keyframes pulse {
  from {
    -ms-transform: scale3d(0.6, 0.6, 0.6);
  }
  50% {
    -ms-transform: scale3d(1.0, 1.0, 1.0);
  }
  to {
    -ms-transform: scale3d(0.6, 0.6, 0.6);
  }
}
@keyframes pulse {
  from {
    transform: scale3d(0.6, 0.6, 0.6);
  }
  50% {
    transform: scale3d(1.0, 1.0, 1.0);
  }
  to {
    transform: scale3d(0.6, 0.6, 0.6);
  }
}

Posts: 1

Participants: 1

Read full topic

@Remah wrote:

When I use the keyboard shortcuts K and J to move the selection in the topic below, the J key jumps from the first reply to the suggested topic list at the bottom of the page.

I used J to go to the end of the topic then to the end of the suggested topic list. I then used K to go back up to the top of the topic. Once I had done that J no longer moves from the first post to the next post, it now moves to the first suggested topic on the list at the end of the topic. If I close the topic window and return to it, I have to follow the same steps to reproduce the problem. It is consistent in the topic I've linked to using both Chrome and Firefox (both 64-bit versions).

I'm not sure why this rather esoteric problem occurs. It didn't reproduce in a couple of other topics I looked at including another how to. I do wonder if it is something to do with more J keypresses than were needed to get to the start or end of the items.

Posts: 2

Participants: 2

Read full topic

@jdlh wrote:

Continuing the discussion from Human Readable interface language selection:

We could debate whether it is "pointless busywork", or "valuable but gruelling", to translate the names of each locale Discourse supports, both into the form used in that locale, and into the form used in any other locale which Discourse supports.

Personally, I think it's valuable. I think that if Discourse is running in a German locale, and a user wants to switch it to a Chinese Traditional locale, then a menu entry "Chinesisch (中文)" is much more helpful than a menu entry "zh".

It certainly would be a lot of work to translate the name of each locale into its form used in each other locale. That's an n-squared translation matrix. Fortunately, someone has done that work.

The Common Locale Data Repository (CLDR) includes many such translations and formatting strings. This includes a fairly well-populated nxn matrix of locale names translated to locales, for n in the dozens, if not hundreds, of locales. See, for example, the A-D segment of this data at http://www.unicode.org/cldr/charts/30/by_type/locale_display_names.languages__a-d_.html . (That's where I got my example of the locale name "Chinese" in German and in Chinese.)

The CLDR data is available for use free of charge. The CLDR is now a project of the Unicode Consortium. Using this data in Discourse would probably require writing an extraction/conversion tool to map from the CLDR data format to a format Discourse uses. We could choose to use the CLDR directly, or via a library such as the Internationalization Class for Unicode (ICU). The CLDR data gets updated twice a year, so Discourse should plan on updating its copy from time to time also. Once Discourse has access to the CLDR data, then people could consider using other CLDR data in other parts of Discourse.

So, legible language names in the Discourse locale selection menu are not ready for a pull request. But the work to implement such a feature is a tooling and integration task, not a translation task.

FYI.
Cheers,
--Jim DeLaHunt

Posts: 3

Participants: 3

Read full topic

@tipyn wrote:

I tried following: https://meta.discourse.org/t/allowing-ssl-https-for-your-discourse-docker-setup/13847 (I had to manually create the ssl directories as they didn't exist)

I did this on two identical servers, both failed after rebuilding the app, so I reverted changes on both, one went back up again but the other one stayed broken with the following error:

nginx: [emerg] BIO_new_file("/shared/ssl/ssl.crt") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/shared/ssl/ssl.crt','r') error:2006D080:BIO routines:BIO_new_file:no such file)`

This is my app.yml file:

  ## Set db_shared_buffers to a max of 25% of the total memory.
  ## this is the all-in-one, standalone Discourse Docker container template
  ##
  ## After making changes to this file, you MUST rebuild
  ## /var/discourse/launcher rebuild app
 ##
 ## BE *VERY* CAREFUL WHEN EDITING!
 ## YAML FILES ARE SUPER SUPER SENSITIVE TO MISTAKES IN WHITESPACE OR ALIGNMENT!
 ## visit  to validate this file as needed

 templates:
  - "templates/postgres.template.yml"
  - "templates/redis.template.yml"
  - "templates/web.template.yml"
## Uncomment these two lines if you wish to add Lets Encrypt (https)
  #- "templates/web.ssl.template.yml"
  #- "templates/web.letsencrypt.ssl.template.yml"

## which TCP/IP ports should this container expose?
## If you want Discourse to share a port with another webserver like Apache or nginx,
## see  for details
expose:
  - "80:80"   # http
  - "443:443" # https
params:
  db_default_text_search_config: "pg_catalog.english"

  ## Set db_shared_buffers to a max of 25% of the total memory.
  ## will be set automatically by bootstrap based on detected RAM, or you can override
  db_shared_buffers: "768MB"

  ## can improve sorting performance, but adds memory usage per-connection
  #db_work_mem: "40MB"

  ## Which Git revision should this container use? (default: tests-passed)
  #version: tests-passed

env:
  LANG: en_US.UTF-8
  # DISCOURSE_DEFAULT_LOCALE: en

  ## How many concurrent web requests are supported? Depends on memory and CPU cores.
  ## will be set automatically by bootstrap based on detected CPUs, or you can override
  UNICORN_WORKERS: 2

  ## TODO: The domain name this Discourse instance will respond to
  DISCOURSE_HOSTNAME: discuss.linaro.cloud

  ## Uncomment if you want the container to be started with the same
  ## hostname (-h option) as specified above (default "$hostname-$config")
  #DOCKER_USE_HOSTNAME: true

  ## TODO: List of comma delimited emails that will be made admin and developer
  ## on initial signup example 'user1@example.com,user2@example.com'
  DISCOURSE_DEVELOPER_EMAILS: {DELETED FOR PRIVACY}

  ## TODO: The SMTP mail server used to validate new accounts and send notifications
  DISCOURSE_SMTP_ADDRESS: {DELETED FOR PRIVACY}
  DISCOURSE_SMTP_PORT: 25
  DISCOURSE_SMTP_USER_NAME: {DELETED FR PRIVACY}
  DISCOURSE_SMTP_PASSWORD: {DELETED FOR PRIVACY}
  #DISCOURSE_SMTP_ENABLE_START_TLS: true           # (optional, default true)

  ## If you added the Lets Encrypt template, uncomment below to get a free SSL certificate
  #LETSENCRYPT_ACCOUNT_EMAIL: me@example.com

  ## The CDN address for this Discourse instance (configured to pull)
  ## see  for details
  #DISCOURSE_CDN_URL:

## The Docker container is stateless; all data is stored in /shared
volumes:
  - volume:
  host: /var/discourse/shared/standalone
  guest: /shared
  - volume:
  host: /var/discourse/shared/standalone/log/var-log
  guest: /var/log

## Plugins go here
## see  for details
hooks:
  after_code:
- exec:
    cd: $home/plugins
    cmd:
      - git clone https://github.com/discourse/docker_manager.git

## Any custom commands to run after building
run:
  - exec: echo "Beginning of custom commands"
  ## If you want to set the 'From' email address for your first registration, uncomment and change:
  ## After getting the first signup email, re-comment the line. It only needs to run once.
  #- exec: rails r "SiteSetting.notification_email='info@unconfigured.discourse.org'"
  - exec: echo "End of custom commands"

Posts: 1

Participants: 1

Read full topic

@tgxworld wrote:

So @Nick and I have been working on a Discourse Narrative Bot which walks a new user through the features that Discourse provides out of the box. While the plugin is still in development stages and kind of rough at the moment, we'll like to get early feedback and ideas from the community so that we can build a better bot.

Right now, the bot has been enabled on https://try.discourse.org/ so you just have to sign up for a new account to start testing and let us know your thoughts

Known Issues

• The certificate you get at the end is still semi broken
• It is kind of weird that the bot asks you to mention him in his welcome topic and then later teaches you about mentions
• I think most of the walkthrough should be done in a PM instead of a new topic since it is mostly a personal experience anyway.
• Think about how to handle large amount of topics being created since it'll pollute a category when many users are interacting with the bot at the same time.

TODOS

• Random @discobot mention replies
• Timeout replies
• Likes tutorial, should be a simple one
• Search tutorial

Posts: 2

Participants: 2

Read full topic

@LastDance wrote:

I saw a post about this way back in 2014,

but since it wasnt in a category, and i was interested in it becoming a thing,i decided it would be better to put in a request here as opposed to bumping an old topic.

As stated in the topic above, would it be possible for someone to create a plugin that can:

• Make category and thread titles that are visible to all users (including logged out users, Google, etc.)

  • Make it so when attempting to view the thread posts, users are be required to
    sign in and check a box that confirms that they're over a certain age
    (e.g. 18 years)

• Allow logged in users who have opted-in to adult-only conversation can view and participate in the category normally, without having to verify their age again.

Currently I am using a group/permission system to deal with this problem, however it generally makes that category and conversation grow slowly because even with a pinned topic in the meta category, most people dont notice its existence.

I understand that the Discourse team is unlikely to want to take the time to implement this, so this topic is largely for charitable plugin designers.

Thanks in advance!

Posts: 1

Participants: 1

Read full topic

@needhelp wrote:

Hi All

Does anyone know the CSS code to do the following?

1) see screen shot below, I put in a RED rectangle box, I would like to hide the topic summary

2) see screen shot below, the area in RED circle, is it possible to have the categories list vertically one on top of the other as opposed to side by side in 2 columns?

Any suggestion or advice would be appreciated. Thanks

Posts: 4

Participants: 3

Read full topic

@jomaxro wrote:

Summary: Over at Stonehearth we previously created tags like crafting and crafting_suggestion. Doing some cleanup, crafting was removed from all topics. Now we cannot recreate the tag.

Steps to reproduce:

1. Add a tag to a topic
2. Add a different tag to a topic that has two words separated by an underscore and one word being the above created tag.
3. Remove the tag from #1 from all topics "deleting" the tag.
4. Attempt to add the tag back to a topic.

Expected Results:

Tag is added to topic.

Actual Results:

Tag does not appear as an option

Notes:

This is likely an issue even if step 1 is skipped, but I haven't tested it.

Attachments:

Pasted image722x93 7.57 KB

Pasted image893x336 9.42 KB

Version Number:

Discourse 1.7.0.beta5 (discourse.stonehearth.net)

System Information:

Windows 10 Education, Chrome Stable 54

Posts: 3

Participants: 3

Read full topic

@jomaxro wrote:

Continuing the discussion from Bulk Actions: "Add Tags" in addition to "Change Tags":

Today I was doing some cleanup of older topics, and this included work on tags. After recategorizing topics I wanted to remove all tags on topics, but there isn't a bulk action to do this. I ended up using the change topics action. As it is a destructive action (not append) I changed the tag to a temporary tag, which I then could delete from the /tags UI. Adding a "remove all tags" action would be appreciated.

Posts: 1

Participants: 1

Read full topic

@Zoe_Thomas wrote:

Hello! When I try to add a category or profile photo I get a transparent grey screen that I need to refresh to escape from. Please can you advise and also if I need to change code could you tell me where to go to do this.

*Should add that it is an SSO forum

Posts: 3

Participants: 2

Read full topic

@Nick_Putman wrote:

I am using SendGrid to process emails sent out by discourse, and I can see in my activity stream on SendGrid that certain email addresses are being blocked. The information in SendGrid of a blocked email is as follows:

REASON552 Spam Message Rejected

I have sent out some test emails from discourse to online spam testing services and the results suggest that these blocks may be very likely to do with Razor2 checks (see results of three separate tests below).

I am wondering if anyone else is seeing this issue, and whether there is anything I can do about it?

---

SpamScoreChecker - Your SpamAssassin Score is: 4.6/5

• 1.7 RAZOR2_CHECK Listed in Razor2 (http://razor.sf.net/)
  • 0.4 RAZOR2_CF_RANGE_51_100 Razor2 gives confidence level above 50% [cf:
  • 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid

Mail Tester - 5.7/10

-2.43
RAZOR2_CF_RANGE_E8_51_100
Razor2 gives engine 8 confidence level above 50%
-1.729
RAZOR2_CHECK
Listed in Razor2 (http://razor.sf.net/)

ISnotSPAM

SpamAssassin check details:

SpamAssassin 3.4.1 (2015-04-28)

Result: ham (non-spam) (03.8points, 10.0 required)

3.5 BAYES_99 BODY: Bayes spam probability is 99 to 100%

Posts: 1

Participants: 1

Read full topic

@jomaxro wrote:

Summary:

Oddly specific bug, as I can only get it to happen with 3 specific filters. When a topic is filtered by category, subcategory, and set to no tags it only displays 30 results, even if there are more than 30 topics that match the filters.

Steps to reproduce:

1. Select category from drop down
2. Select subcategory from second drop down
3. Select no tags from tag filter
4. Count topics...

Expected Results:

All topics that match filter appear

Actual Results:

Only 30 topics appear despite more than 30 topics matching filter.

Notes:

Unknown if this is related, or a separate bug - if you select all the topics listed and change the category or add a tag, the page reloads with an "unfiltered latest" view, and the page needs to be refreshed to show the next set of results.

Link:

One example of where this is happening: https://discourse.stonehearth.net/tags/c/support/other-reports/none

Version Number:

Discourse 1.7.0.beta5 (discourse.stonehearth.net)

System Information:

Windows 10 Education, Chrome Stable 54

Posts: 1

Participants: 1

Read full topic

@Aman_Jagga wrote:

Is there any available working image gallery discourse plugin similar to this

This plugin is nice but it's paid.I am looking for a free plugin

My requirement is very simple, multiple images should open in a gallery

Posts: 4

Participants: 3

Read full topic

@Paul_Vincent wrote:

I've managed to migrate my users/forums from our Drupal-based site into a Development environment on OSX. I now want to either:

1. Upload the Backup into my Production instance on Digital Ocean and restore from the UI or,
2. Perform the same migration on the Production box, bearing in mind the site hasn't gone live yet and I have backups.

My issue with No 1 is that although the backup file has uploaded, it's been split into about 20 files within a tmp directory due to the size of it, and isn't showing up in the UI. Is there a special way of restoring from a set of files, or should I just FTP the full file into the Backups folder?

With No 2, I know that's not the ideal method, but I've run the migration fine on several occasions in Dev mode, but cannot work out how to do this in a production environment anyway; how is this done? I'm a Ruby Newbie, so this business of switching modes might be a simple matter I'm just not aware of.

Many thanks in advance,
Paul

Posts: 2

Participants: 2

Read full topic

@needhelp wrote:

I am sorry if this is not the correct category but I couldn't find a category where people can showcase their discourse forum.

I would like to get fresh ideas how people customize their forum home page especially in the header area where people feature their website's logo and their website's header navigation menu,

The forum is only a portion of my website so I would like to see what people do to integrate or present their website's nav menu in the forum header.

Right now I only see the option to upload my site's logo, but not sure where to go to customize a nav menu in the forum header.

Any feedback or advice would be appreciated.

Thanks

Posts: 3

Participants: 2

Read full topic

@brenna1 wrote:

To continue the conversation started by @sujato a couple of months ago, we are beginning to see the importance of establishing features that allow for gender non-conforming people to feel safe on our forum.

One of the initial ideas that I had in entering this conversation, is to provide the option for people to list their preferred gender pronouns in their profile so that other people can know how they should refer to them. This is a very simple way to create a safe space by not relying on assumptions of gender.

I would also like to encourage other people to share ideas of inclusivity that they think would be beneficial. Thank you!

Posts: 4

Participants: 3

Read full topic