Quantcast
Channel: Discourse Meta - Latest topics
Viewing all 60309 articles
Browse latest View live

How to rename a Category? (safely)

0
0

Philip Rhoades P wrote:

People, I have seen references to people renaming Categories and there being problems - but I can't find out how the renaming is actually done. I have the default category "Uncategorised" with the first nine topics in there and I want to rename the Category to "General" - is there a way to do this without causing problems?

Thanks,

Phil.

Posts: 4

Participants: 2

Read full topic


ActionView :: Template :: Error (incompatible character encodings : UTF 8 and ASCII 8BIT)

0
0

Sam Saffron wrote:

I am seeing this error on a Discourse site

When it happens every visit to the front any page just comes out as a white page.

I suspect this is encoding related, somehow something is getting cached wrong. Perhaps a Rails bug. I tried debugging this but can not find the root cause. Last time it went away after a rebuild which may indicate it is encoding related.

@tenderlove @rafaelfranca have you ever seen anything like this anywhere?

ActionView::Template::Error (incompatible character encodings: ASCII-8BIT and UTF-8)

 

/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/core_ext/string/output_safety.rb:176:in `concat'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/core_ext/string/output_safety.rb:176:in `concat'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.5/lib/action_view/buffers.rb:12:in `<<'
/var/www/discourse/app/views/list/list.erb:17:in `_app_views_list_list_erb___19075230255371980_70047495970040'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.5/lib/action_view/template.rb:145:in `block in render'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/notifications.rb:161:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.5/lib/action_view/template.rb:339:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.5/lib/action_view/template.rb:143:in `render'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.1/lib/mini_profiler/profiling_methods.rb:79:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.5/lib/action_view/renderer/template_renderer.rb:55:in `block (2 levels) in render_template'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.5/lib/action_view/renderer/abstract_renderer.rb:38:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/notifications.rb:159:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/notifications.rb:159:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.5/lib/action_view/renderer/abstract_renderer.rb:38:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.5/lib/action_view/renderer/template_renderer.rb:54:in `block in render_template'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.5/lib/action_view/renderer/template_renderer.rb:62:in `render_with_layout'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.5/lib/action_view/renderer/template_renderer.rb:53:in `render_template'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.5/lib/action_view/renderer/template_renderer.rb:17:in `render'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.5/lib/action_view/renderer/renderer.rb:42:in `render_template'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.5/lib/action_view/renderer/renderer.rb:23:in `render'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.5/lib/action_view/rendering.rb:99:in `_render_template'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/streaming.rb:217:in `_render_template'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.5/lib/action_view/rendering.rb:82:in `render_to_body'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/rendering.rb:32:in `render_to_body'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/renderers.rb:32:in `render_to_body'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/abstract_controller/rendering.rb:25:in `render'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/rendering.rb:16:in `render'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/instrumentation.rb:41:in `block (2 levels) in render'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/core_ext/benchmark.rb:12:in `block in ms'
/usr/local/lib/ruby/2.0.0/benchmark.rb:296:in `realtime'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/core_ext/benchmark.rb:12:in `ms'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/instrumentation.rb:41:in `block in render'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/instrumentation.rb:84:in `cleanup_view_runtime'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/railties/controller_runtime.rb:25:in `cleanup_view_runtime'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/instrumentation.rb:40:in `render'
/var/www/discourse/app/controllers/list_controller.rb:190:in `block (2 levels) in respond'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/mime_responds.rb:258:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/mime_responds.rb:258:in `respond_to'
/var/www/discourse/app/controllers/list_controller.rb:186:in `respond'
/var/www/discourse/app/controllers/list_controller.rb:67:in `block (2 levels) in <class:ListController>'
/var/www/discourse/app/controllers/list_controller.rb:71:in `block (2 levels) in <class:ListController>'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/abstract_controller/base.rb:189:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/rendering.rb:10:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:229:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:229:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:86:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:86:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/instrumentation.rb:31:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/notifications.rb:159:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/notifications.rb:159:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/abstract_controller/base.rb:136:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.5/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.1/lib/mini_profiler/profiling_methods.rb:79:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal.rb:232:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/routing/route_set.rb:82:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/routing/route_set.rb:82:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/routing/route_set.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/journey/router.rb:71:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/journey/router.rb:59:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/journey/router.rb:59:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/routing/route_set.rb:678:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-protection-1.5.2/lib/rack/protection/frame_options.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/builder.rb:59:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/conditionalget.rb:25:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/head.rb:11:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:117:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/flash.rb:254:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-0.9.5/lib/message_bus/rack/middleware.rb:55:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:225:in `context'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/cookies.rb:560:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/connection_adapters/abstract/connection_pool.rb:621:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:82:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/remote_ip.rb:76:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-0.1.6/lib/logster/middleware/reporter.rb:23:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.5/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.5/lib/rails/rack/logger.rb:22:in `call'
/var/www/discourse/config/initializers/quiet_logger.rb:10:in `call_with_quiet_assets'
/var/www/discourse/config/initializers/silence_logger.rb:26:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/methodoverride.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/runtime.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/sendfile.rb:112:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.1/lib/mini_profiler/profiler.rb:193:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.5/lib/rails/engine.rb:514:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.5/lib/rails/application.rb:144:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.5/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.5/lib/rails/railtie.rb:194:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:138:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:65:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:576: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-4.8.3/lib/unicorn/http_server.rb:670:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:525:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:140:in `start'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/bin/unicorn:126:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in `load'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in `<main>'

Posts: 1

Participants: 1

Read full topic

Some keys are not recognized by Transifex as pluralized, e.g. js.filters.new.title

0
0

Anton wrote:

Even though Russian pluralization keys have been recently updated in the Discourse codebase, I just caught a few problems in the GUI:

Correct keys are one, few and other, so few is a correct key.
However, Transifex does not recognize that the key can be pluralized:

Compare with another example where pluralization is recognized by Transifex:

So there should be something wrong with some keys because Transifex does not recognize they can be prlualized and thus we do not have where to input translations for the few pluralization keyword.

Keys affected:

  • js.filters.new.title
  • js.filters.unread.title
  • admin.badges.preview.grant_count

My guess is that in the client.en.yml file some pluralization keys are missing and that leads to Tranfiex not recognizing that a particular key should be pluralized:

title:
      zero: "Unread"
      one: "Unread (1)"
      other: "Unread ({{count}})"

Here the few is missing, while zero is not expected. For English it should be one, few and other.

It may be useful to add some validation over the original English YML files and force keys have either all or none pluralization sub-keys.

Posts: 1

Participants: 1

Read full topic

What does Rebake mean and do?

0
0

Anton wrote:

Please could you explain a bit about what is the purpose of the Rebake?
I struggle finding good word in Russian, so I'd like to better understand what it does exactly.
Thanks.

Posts: 2

Participants: 2

Read full topic

Is it safe to translate trust_level_N and remove underscores

0
0

Anton wrote:

I can see there are 5 keys to be translated:

groups.default_names.trust_level_N where N is 0 to 5.

What confuses me is that even in original English language the translation looks more like an identifier rather than like a human readable string, e.g. trust_level_0 and not Trust level 0.

So I wonder how safe it is to translate the string to something like уровень доверия 1 (Russian) instead of уровень_доверия_1 - what will it affect and what might break if I remove underscores and change the language? Should I also change anything else simultaneously if I translate these strings?

Thank you in advance.

Posts: 2

Participants: 2

Read full topic

Back button not working on Category filter

0
0

ginger man wrote:

Is there a way to open the individual topic page in the right pane like what you see in nytimes.com comments. This is helpful to retain the context.

This is extremely useful when you scroll through 100 topics and choose one topic to read. When you hit the back button after reading the topic, the initial position is lost.

What is the ideal way to implement this need ?

Posts: 10

Participants: 2

Read full topic

Inline links cause a parser infinite loop?

Directory of public discourse sites, or, where are my new users coming from?

0
0

Matt Ginzton wrote:

I have a private instance of Discourse that I've been running for about 1.5 years, a few dozen people use it, nothing too big.

This week I finally got around to upgrading it to the 1.0 release, and since then I've seen a huge number (well, 5!) of unsolicited join requests, which wasn't happening before. I'm wondering where these are coming from, how/why people are finding my site which I don't think I've publicized beyond its intended audience.

I can't find any mention of it in the current www.discourse.org site (about, faq, etc) but I recall from the earlier days there was going to be a public directory of discourse sites. I see a meta post about this from early 2013 which said this was planned and implied it would be on by default unless the discourse instance has a site password.

I went through the settings for my discourse instance and don't see anything that looks like an opt-in or opt-out for "list me in a directory of sites". In Settings::Login, I have selected "login required" and "must approve users" and have not selected "invite only" (I know I could turn that on, and will if I keep getting unsolicited join requests, but I would prefer to leave it possible for people I do give the link to to sign up without a formal invite). I don't believe I have a "site password" set and don't know where to find this setting either; I have a dim recollection this was a feature of the earlier days of Discourse that doesn't exist any more.

Anyway, I'm wondering if this public directory feature actually happened, and if there is some public listing of discourse sites that I added myself to accidentally when I upgraded. Or if not, if you have any other theories why the number of unsolicited join requests went from 0->5 this week.

Posts: 5

Participants: 4

Read full topic


Dismiss buttons missing on category new/unread

Search - Change blue X to "Show less" which is equivalent to "Show more"

0
0

Tobias Eigen wrote:

When I search and then select the "show more" link at bottom, I expect to then be able to select "show less" instead of an X. It's smaller and harder to hit esp on mobile, and it also does not X out the window altogether but instead shows the "show less" search results. I suggest changing this X to "show less".

First window with show more:

Second window with blue X instead of show less:

Posts: 5

Participants: 4

Read full topic

Moderator can't answer personalized notifications

Discourse behind Forefront TMG 2010

0
0

Josué Garméndez wrote:

First, I've installed Discourse on my own Ubuntu Server 14.04 virtual machine following the Beginner Docker install guide for Digital Ocean, you know, just for trying. And It works great! Everything goes smooth! Amazing software.

Before installing Discourse, in addition to postgresql 9.3:

sudo apt-get install python3 python3-yaml ruby redis-server git

Later, I succesfully deployed Discourse on 'production' (on a physical machine) doing the same steps. On the firewall machine (Windows Server 2008 R2 - Forefront TMG 2010, which is my external DNS also) I created the rule to publish the server with its own subdomain. Now is running; although the infrastructure is not the best to say, Discourse loads pretty well.

Mail is working fine, the problem is when login on Discourse, it's seems like I'm not logged. Then I add (e. g.) '/latest' to my URL 'discourse.example.com' resulting 'discourse.example.com/latest', hit Enter, and it turns out that I've already logged (of course). This mean that 'sign up' and 'log in' button disappear, and finally shows the Avatar.
Logout it's pretty much the same, seems like still logged, but user isn't logged anymore.

I guess the Forefront TMG in some way is messing with Discourse server. I've been trying different configurations settings on the publishing rule on the TMG, but nothing has worked yet.

Has someone tried this kind of config before?

Posts: 1

Participants: 1

Read full topic

Traffic lights algorithm

0
0

PJH wrote:

Could we have have some clarity over the traffic lights visible on profiles for admin's (and possibly TL4 's? )

I get the impression that under the algorithm (some?) flagged posts are considered a detriment, but on our forum flags are also used to flag 'positive' posts for manually assigned badges. (Yes, I agree your flagging that post for $BADGE is correct)

If such clarity exists, can I have a link?

If my assumption/impression is true, can this be moved to bugs?

Posts: 6

Participants: 2

Read full topic

Identifying old posts/topics

0
0

cpradio wrote:

Okay, we've had about a dozen users now complain that it is too difficult to identify when a topic/post is old and we are seeing dozens of posts added to topics that are well over a year old.

First things first, yes, the Revive topic warning does show (but everyone seems to ignore it -- maybe because it is too similar to the Suggested Topics popup?). Secondly, the topic list is still making it hard to identify these. Yes, the activity column is blue, our users aren't noticing that either.

Is anyone else experiencing these issues with Discourse?

ping @HAWK

Posts: 7

Participants: 2

Read full topic

Uploads and confirmation emails break when changing external docker port in app.yml

0
0

Clay Heaton wrote:

In app.yml, image uploads and new account verification emails break when changing from:

expose:
  - "80:80"
  - "2222:22"

to the following (9999 as an exampe):

expose:
  - "9999:80"
  - "2222:22"

... if you don't use URL rewriting to mask the external port number.

In my situation, I'm on a private internal network and want to run discourse on a server that already is hosting sites on 80 and 443. I can get to the instance of Discourse that I installed at http://www.mysite.com:9999 but when I try to upload images (into the site assets category, for example) the image paths all lack the port number.

So... I tried going back into the app.yml file and changing:

env:
  DISCOURSE_HOSTNAME: 'www.mysite.com'

to the following:

env:
  DISCOURSE_HOSTNAME: 'www.mysite.com:9999'

I then rebuilt the app. After that change, image uploads (into posts) worked, but avatar images were broken. The src for them became, for example:

src="/user_avatar/www.mysite.com:9999/system/45/1.png"

From my point of view, the expected behavior is that setting:

expose:
  - "9999:80"
  - "2222:22"

Should append the port number to all links OR I should be able to change

env:
  DISCOURSE_HOSTNAME: 'www.mysite.com:9999'

To indicate that all links should include the port number. Alternatively, perhaps we should be able to have a second setting:

env:
  DISCOURSE_HOSTNAME: 'www.mysite.com'
  DISCOURSE_PORTNUMBER: 9999        # or 80 or whatever

FYI, I first asked about this here:

Posts: 3

Participants: 2

Read full topic


Where is the Delete a post icon?

0
0

Chris wrote:

I can't seem to find the Delete botton. I saw it, and made a topic invisible, but now I don't see it, or I don't remember where it was.

Posts: 2

Participants: 2

Read full topic

Add link to commit on GitHub when closing a fixed bug/added feature: Part 2

0
0

c-i-p-h-e-r-1 wrote:

Continuing the discussion from Add link to commit on GitHub when closing a fixed bug/added feature:

I understand that @codinghorror might not want to discuss this, but I don't think the previous topic was ready to be closed. In fact, his final comment on the topic does leave a great, big question in my mind:

Why not? Why don't you have a policy requiring that when you fix a bug, you post a link to the Github commit in the relevant bug topic? You guys already do a pretty good job of policing the bug and feature categories to weed out duplicates, so that shouldn't be too big a problem. I know I really appreciate seeing those posts when they are put in there. Unfortunately, I usually only see them on bugs/features that are handled by @zogstrip and @elberet. From what I understand, your official dev team is less than 10 people, so it looks like you've already got over 20% of your team doing this on a regular basis. Why don't you want to make this additional layer of transparency part of your development standard for Discourse?

Posts: 12

Participants: 5

Read full topic

Hide topics from topic listing/category view if the only post is hidden by flaging

0
0

cpradio wrote:

I'm not sure if this is the right place, but we've seen several posts (that are the only post for a given topic - so 1 topic 1 post) that get flagged, then automatically hidden (or hidden by Mod agreement), but the Topic remains visible on the topic listings, under New, Unread, the Category Listing, etc.

The only post of that topic was deemed not worth viewing, shouldn't it hide the topic too?

Posts: 3

Participants: 2

Read full topic

[Paid] Need someone that can help us to extend tags, plugins, and some system maintenance

0
0

Federico wrote:

Hi, we are looking for someone that can help us to integrate Discourse with our actual PHP web.
We need to extend tags plugin to let us create topics with tags using PHP and the API.
Also that person will take care of Discourse system (upgrades, etc).

Please send me hourly rates. Thank you

Posts: 1

Participants: 1

Read full topic

Thank you for putting edit link right at top of wiki posts - can we do this for all posts?

0
0

Tobias Eigen wrote:

I see that in the latest update a nifty edit link has been added right at the top of wiki posts - I love this. Would it be possible to also display this link to anyone who has permission to edit the post? Maybe in a different color or simply with a different mouseover text? When I want to make a quick edit to a post, my eye is often drawn to that corner for an edit link because of the "last edited" button that is up there.

Posts: 1

Participants: 1

Read full topic

Viewing all 60309 articles
Browse latest View live




Latest Images