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

Unable to bootstrap discourse on docker

$
0
0

Jacob Mani wrote:

Am trying to install discourse on AWS EC2
and i have been following the under 30 miuntes installation github instruction

but after i type in the following command $ ./launcher bootstrap app

i get the following error

which: no docker.io in (/sbin:/bin:/usr/sbin:/usr/bin)
Your Docker installation is not using aufs, in the past we have had issues with it
If you are unable to bootstrap your image (or stop it) please report the issue at:

ERROR: Docker version 1.1.2 not supported, please upgrade to at least 1.2.0, or recommended 1.2.0

I went through few posts and tried out things but i am confused and nothing is working
What should i do?

Posts: 4

Participants: 3

Read full topic


Missing pl_PL translations for Poll plugin

Document keyboard command to link a URL

$
0
0

Allen - Watchman Monitoring wrote:

I'm a huge keyboard fan.. anything I can do to prevent a mouse click is great.

I'm creating documentation in our discourse and am constantly making linked text pre-formatted by typing Command K.

It took me a minute to realize that the command I'm used to in gmail, google docs and wordpress won't work here, and I have to remember that it's Command L to link text.

Could we get K made more universal, and maybe add these to the keyboard shortcut list?

Posts: 14

Participants: 3

Read full topic

Can't create a category

$
0
0

Camille Roux wrote:

When I try to create a category, I get an error:

Here is what I get in logs:

<hash>
  <date type="dateTime">2014-09-12T23:13:37+00:00</date>
  <guid>fdb8bf2e-eaa0-4906-a94b-8080273f38c4</guid>
  <user-id type="integer">2</user-id>
  <parameters>{"name":"Test","color":"AB9364","text_color":"FFFFFF","permissions":{"fr.category.everyone_permission":"1"},"allow_badges":"true","action":"create","controller":"categories"}</parameters>
  <action>create</action>
  <controller>categories</controller>
  <backtrace>[RAILS_ROOT]/app/models/group.rb:192:in `lookup_group'
[RAILS_ROOT]/app/models/group.rb:162:in `[]'
[RAILS_ROOT]/app/models/category.rb:300:in `block in resolve_permissions'
[RAILS_ROOT]/app/models/category.rb:296:in `each'
[RAILS_ROOT]/app/models/category.rb:296:in `map'
[RAILS_ROOT]/app/models/category.rb:296:in `resolve_permissions'
[RAILS_ROOT]/app/models/category.rb:235:in `set_permissions'
[RAILS_ROOT]/app/models/category.rb:242:in `permissions='
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/attribute_assignment.rb:45:in `public_send'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/attribute_assignment.rb:45:in `_assign_attribute'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/attribute_assignment.rb:56:in `block in assign_nested_parameter_attributes'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/attribute_assignment.rb:56:in `each'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/attribute_assignment.rb:56:in `assign_nested_parameter_attributes'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/attribute_assignment.rb:36:in `assign_attributes'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/core.rb:455:in `init_attributes'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/core.rb:198:in `initialize'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/inheritance.rb:30:in `new'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/inheritance.rb:30:in `new'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/persistence.rb:33:in `create'
[RAILS_ROOT]/app/controllers/categories_controller.rb:69:in `create'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/abstract_controller/base.rb:189:in `process_action'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/rendering.rb:10:in `process_action'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:113:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:113:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149:in `block in halting_and_conditional'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149:in `block in halting_and_conditional'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149:in `block in halting_and_conditional'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:229:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:229:in `block in halting'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166:in `block in halting'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:86:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:86:in `run_callbacks'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/abstract_controller/callbacks.rb:19:in `process_action'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/rescue.rb:29:in `process_action'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/instrumentation.rb:31:in `block in process_action'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/notifications.rb:159:in `block in instrument'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/notifications.rb:159:in `instrument'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/abstract_controller/base.rb:136:in `process'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.5/lib/action_view/rendering.rb:30:in `process'
[RAILS_ROOT]/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'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal.rb:196:in `dispatch'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_controller/metal.rb:232:in `block in action'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/routing/route_set.rb:82:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/routing/route_set.rb:82:in `dispatch'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/routing/route_set.rb:50:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/journey/router.rb:71:in `block in call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/journey/router.rb:59:in `each'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/journey/router.rb:59:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/routing/route_set.rb:678:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/rack-protection-1.5.2/lib/rack/protection/frame_options.rb:31:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/builder.rb:59:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/conditionalget.rb:35:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/head.rb:11:in `call'
[RAILS_ROOT]/lib/middleware/anonymous_cache.rb:119:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/flash.rb:254:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/message_bus-0.9.5/lib/message_bus/rack/middleware.rb:55:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:225:in `context'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:220:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/cookies.rb:560:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/query_cache.rb:36:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.5/lib/active_record/connection_adapters/abstract/connection_pool.rb:621:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:82:in `run_callbacks'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/remote_ip.rb:76:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/logster-0.1.6/lib/logster/middleware/reporter.rb:23:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/railties-4.1.5/lib/rails/rack/logger.rb:38:in `call_app'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/railties-4.1.5/lib/rails/rack/logger.rb:22:in `call'
[RAILS_ROOT]/config/initializers/quiet_logger.rb:10:in `call_with_quiet_assets'
[RAILS_ROOT]/config/initializers/silence_logger.rb:26:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.5/lib/action_dispatch/middleware/request_id.rb:21:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/methodoverride.rb:21:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/runtime.rb:17:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/sendfile.rb:112:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.1/lib/mini_profiler/profiler.rb:215:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/railties-4.1.5/lib/rails/engine.rb:514:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/railties-4.1.5/lib/rails/application.rb:144:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/railties-4.1.5/lib/rails/railtie.rb:194:in `public_send'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/railties-4.1.5/lib/rails/railtie.rb:194:in `method_missing'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:138:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:65:in `block in call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in `each'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:576:in `process_client'
[RAILS_ROOT]/lib/middleware/unicorn_oobgc.rb:95:in `process_client'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:670:in `worker_loop'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:525:in `spawn_missing_workers'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:140:in `start'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/bin/unicorn:126:in `&lt;top (required)&gt;'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in `load'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in `&lt;main&gt;'</backtrace>
  <message>unknown group</message>
  <url>https://forum.humancoders.com/categories</url>
  <exception-class>ArgumentError</exception-class>
</hash>

Do you know what happens? thanks!

Posts: 2

Participants: 1

Read full topic

Add members to group from another group

$
0
0

mfeckie wrote:

What are people's thoughts on adding the ability to bulk add users to a Group based on membership of another group?

Use case is like, "I'm setting up a new project, but it's not for everyone to see, so I want to add all the Developers and all the Marketers". I don't currently see a simple way to do this (though I may be missing something).

I'm thinking something that looks like this

Thoughts?

Posts: 1

Participants: 1

Read full topic

How do you install theme on Discourse

Docker upgrade links point only to the repo, not the displayed commit

$
0
0

Allen - Watchman Monitoring wrote:

In docker manager the links show the commit numbers; awesome!

but the link just go to the repo. disappointing!

Could they point to the commit please?

PS Bonus feature request... if we could get linked to the compare URL, that'd be spiffy

https://github.com/discourse/docker_manager/compare/9c285f0...c599991

PPS (Bonus rant, ever since this commit I have to remember to command click if I want to read what's up and not lose my spot.. I guess I wasn't watching when we had that vote frowning

Posts: 1

Participants: 1

Read full topic

Why does it take forever to rebuild discourse?

$
0
0

flexihack wrote:

I recently installed Discourse on DigitalOcean (1GB CPU) and then when I try to rebuild the site it takes about 15 minutes (not even complete yet). It's currently on something like "Background saving terminate with success"

Posts: 3

Participants: 3

Read full topic


There was a problem sending another activation email

$
0
0

Michael wrote:

Continuing the discussion from "There was a problem sending another activation email" and a pair of questions:

We're getting this error as well in a few forums when you go to an unactivated user and hit the 'resend activation email' button. Activating and then deactivating the user account does not help.

It's sending an empty POST to /users/username/send_activation_email and getting a 404 back.

production.log:

Started POST "/users/testuser/send_activation_email" for x.x.x.x at 2014-09-13 02:31:23 -0400
Processing by UsersController#send_activation_email as */*
  Parameters: {"username"=>"testuser"}
  Rendered exceptions/not_found.html.erb within layouts/no_js (15.1ms)
  Rendered common/_special_font_face.html.erb (1.3ms)
  Rendered common/_discourse_stylesheet.html.erb (6.2ms)
  Rendered layouts/_head.html.erb (8.7ms)
  Rendered text template (0.0ms)
Completed 404 Not Found in 50ms (Views: 0.8ms | ActiveRecord: 13.2ms)

Posts: 3

Participants: 2

Read full topic

How to increase the minimum number of words in private message and post

Reader badge bug?

Automatic feature/branch deployment in Docker cloud for Discourse contributors

$
0
0

Anton wrote:

Just found this and thought it could be interesting for Discourse contributors:

https://teatro.io/

  1. Create feature in a separate branch and make a pull request on Github.
  2. Click on link (posted by Teatro right in GitHub) and it opens stage right for that specific feature branch

It's based on Docker and supports Rails.

Posts: 1

Participants: 1

Read full topic

Home/Index taking to long to load

$
0
0

The long version of me wrote:

It is taking to long to load homepage index page. Even here on your instance it can be slow, but it is much slower on 2GB Digital Ocean droplet. I understand that Discourse needs a lot of resources, but line has to be drawn somewhere as we progress from 1.0 forward. Speed has to be one of the main concerns before adding additional features.

Loading image could solve problem temporarily at least when going back to homepage from certain topic.

Posts: 7

Participants: 4

Read full topic

Getting 502 sometimes when deleting topic

$
0
0

scrher wrote:

Sometimes when I'm trying to delete a topic the DELETE request takes a long time and then returns 502 error.
There is nothing in production_errors.log and here is what I found in production.log

Started DELETE "/t/9497" for IP at 2014-09-13 03:31:38 +0000
Processing by TopicsController#destroy as */*
  Parameters: {"id"=>"9497"}

And there is just no "Completed: " line.
Nginx says "upstream prematurely closed connection while reading response header from upstream".

I'm running discourse in docker with custom current_user_provider for custom authentication, but it seems unrelated.

Can someone give an advice on how to debug this?

Posts: 1

Participants: 1

Read full topic

Editing Window in Admin area overrides the ability to Edit a Flagged Post

$
0
0

cpradio wrote:

Continuing the discussion from Editing Old Posts and Adding Links Doesn't Alert Anybody:

Can we make the above change (granted, that might not be the actual code... but the idea behind it is simple:

Repro Steps (requires 2 accounts - one moderator or higher and one normal user)
Set Edit Window to something small (such as 10 minutes)

  1. Login as normal user, create a post, wait 10 minutes for edit icon to disappear
  2. Logout as normal user, login as moderator
  3. Find post created by normal user, flag as inappropriate and choose Take Action, logout
  4. Login as normal user, read PM, wait 10 minutes (per PM), visit post, edit icon isn't available
  5. Login as moderator/admin, change edit window to 1 day, logout
  6. Login as normal user, you can edit your post now.

Posts: 1

Participants: 1

Read full topic


Prioritise a specific search result

$
0
0

Andy Crichton wrote:

Hope I can explain my search requirement in time. (I am still giddy with excitement having had my WP forum migrated over by Discourse Hosting.)

To manipulate a certain result to be top of the search results in Google, you can pay the man. How can you force a result to the top within Discourse search?

e.g. If someone searches for "recommended contractor London" on my forum, I would like

a) the full Andy recommended contractor listing to appear at the top of the results and

b) the result should be formatted in a way that screams "official".

Is this within the scope of Discourse, or should I add this to the list for a developer to look at separately.

Posts: 3

Participants: 2

Read full topic

Replying to first post behaves as reply to topic

Master or stable branch for production

$
0
0

Archon wrote:

Should I use the master or stable branch if I'm planning to use Discourse in production?

(not sure if right category, sorry if it's not)

Posts: 5

Participants: 3

Read full topic

Error message "Cannot allocate memory" in logs

$
0
0

Florian Beer wrote:

Hi,
we have been seeing increased amounts of the following messages in the logs:

Cannot allocate memory - df -l . | tail -1 | tr -s ' ' | cut -d ' ' -f 5
Job exception: Wrapped Errno::ENOMEM: Cannot allocate memory - df -l . | tail -1 | tr -s ' ' | cut -d ' ' -f 5

The server has 4GB RAM and there is enough free memory according to free -m but the message keeps popping up nonetheless about every minute. The dfcommand shows enough free harddisk space as well.

Discourse version: 1.1.0.beta2
Latest installed commit: cf4bd67

Does anybody have an idea what to do about this?


Backtraces for the errors:

/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/core_ext/kernel/agnostics.rb:7:in ``'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.5/lib/active_support/core_ext/kernel/agnostics.rb:7:in ``'
/var/www/discourse/lib/cooked_post_processor.rb:255:in `available_disk_space'
/var/www/discourse/lib/cooked_post_processor.rb:246:in `disable_if_low_on_disk_space'
/var/www/discourse/lib/cooked_post_processor.rb:235:in `pull_hotlinked_images'
/var/www/discourse/lib/cooked_post_processor.rb:24:in `post_process'
/var/www/discourse/app/jobs/regular/process_post.rb:16:in `execute'
/var/www/discourse/app/jobs/base.rb:154:in `block (2 levels) in perform'

/var/www/discourse/app/jobs/base.rb:179:in `perform'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.1.3/lib/sidekiq/processor.rb:52:in `block (2 levels) in process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.1.3/lib/sidekiq/middleware/chain.rb:122:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.1.3/lib/sidekiq/middleware/chain.rb:122:in `block in invoke'
/var/www/discourse/lib/sidekiq/pausable.rb:81:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.1.3/lib/sidekiq/middleware/chain.rb:124:in `block in invoke'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.1.3/lib/sidekiq/middleware/server/active_record.rb:6:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.1.3/lib/sidekiq/middleware/chain.rb:124:in `block in invoke'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.1.3/lib/sidekiq/middleware/server/retry_jobs.rb:62:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.1.3/lib/sidekiq/middleware/chain.rb:124:in `block in invoke'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.1.3/lib/sidekiq/middleware/server/logging.rb:11:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.1.3/lib/sidekiq/logging.rb:22:in `with_context'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.1.3/lib/sidekiq/middleware/server/logging.rb:7:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.1.3/lib/sidekiq/middleware/chain.rb:124:in `block in invoke'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.1.3/lib/sidekiq/middleware/chain.rb:127:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.1.3/lib/sidekiq/middleware/chain.rb:127:in `invoke'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.1.3/lib/sidekiq/processor.rb:51:in `block in process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.1.3/lib/sidekiq/processor.rb:94:in `stats'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.1.3/lib/sidekiq/processor.rb:50:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/celluloid-0.15.2/lib/celluloid/calls.rb:25:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/celluloid-0.15.2/lib/celluloid/calls.rb:25:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/celluloid-0.15.2/lib/celluloid/calls.rb:122:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/celluloid-0.15.2/lib/celluloid/actor.rb:322:in `block in handle_message'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/celluloid-0.15.2/lib/celluloid/actor.rb:416:in `block in task'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/celluloid-0.15.2/lib/celluloid/tasks.rb:55:in `block in initialize'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/celluloid-0.15.2/lib/celluloid/tasks/task_fiber.rb:13:in `block in create'

Posts: 6

Participants: 2

Read full topic

Where is my discourse in FTP filezilla?

$
0
0

flexihack wrote:

I used the Filezilla software on my computer to have access to folders and files. I have a Discourse installed on Digitalocean. Not sure where my discourse are located.

Posts: 5

Participants: 3

Read full topic

Viewing all 60721 articles
Browse latest View live




Latest Images