Travis wrote:

My docker admin is showing "Currently Upgrading" even though I just did a manual ./launcher rebuild app.

Should I go ahead and click "reset" even though there's a huge WARNING on it?

Posts: 2

Participants: 2

Read full topic

NomNuggetNom wrote:

I think folding spoilers should be implemented using existing HTML presentation:

Spoiler Title

Spoiler Contents

Which can be achieved like this:

<details><summary>Spoiler Title</summary>Spoiler Contents</details>

Note: This requires all inside elements to be HTML, and would need to be fixed. All markdown inside of it is broken. Obviously this isn't user friendly. I saw it suggested something like this:

[spoiler "Spoiler Title"]Spoiler Content[/spoiler]

Posts: 12

Participants: 6

Read full topic

Jonas Stendahl wrote:

Hello!

I've been trying to get an instance running using the docker image and everything seems to work just fine except for the Jobs::VersionCheck.

The admin dashboard says "A check for updates has not been performed. Ensure sidekiq is running.", but Sidekiq is without doubt running. If I go to example.com/sidekiq it says that Jobs::VersionCheck fails with the error "RestClient::InternalServerError: 500 Internal Server Error".

I went through the logs and found the following stacktrace:

exception: 500 Internal Server Error
context: {"retry"=>true, "queue"=>"default", "class"=>"Jobs::VersionCheck", "args"=>[{}], "jid"=>"9fec4a6aca59becd31d3244e", "enqueued_at"=>1401494376.5670652, "error_message"=>"500 Internal Server Error", "error_class"=>"RestClient::InternalServerError", "failed_at"=>1401494378.2052548, "retry_count"=>5, "retried_at"=>1401495107.6883876}
backtrace: /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rest-client-1.6.7/lib/restclient/abstract_response.rb:48:in `return!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rest-client-1.6.7/lib/restclient/request.rb:230:in `process_result'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rest-client-1.6.7/lib/restclient/request.rb:178:in `block in transmit'
/usr/local/lib/ruby/2.0.0/net/http.rb:852:in `start'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rest-client-1.6.7/lib/restclient/request.rb:172:in `transmit'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rest-client-1.6.7/lib/restclient/request.rb:64:in `execute'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rest-client-1.6.7/lib/restclient/request.rb:33:in `execute'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rest-client-1.6.7/lib/restclient.rb:68:in `get'
/var/www/discourse/lib/discourse_hub.rb:106:in `singular_action'
/var/www/discourse/lib/discourse_hub.rb:90:in `get'
/var/www/discourse/lib/discourse_hub.rb:83:in `discourse_version_check'
/var/www/discourse/app/jobs/scheduled/version_check.rb:13:in `execute'
/var/www/discourse/app/jobs/base.rb:131:in `block (2 levels) in perform'

Any ideas?

Thanks!

Posts: 3

Participants: 3

Read full topic

David McClure wrote:

Continuing the discussion from Move some post actions to "extra drawer":

This seems to warrant its own discussion. A few thoughts I have regarding the current indicator and its history:

1. By the time you can see the current bookmark indicator, you've probably already read the post, since its below the post.
   • A long time ago the bookmark icon was on top of the posts. Since it was doing double-duty as the bookmark feature, it made sense to move it down to the bottom, but its more clear not that these two functions are somewhat in conflict with each other.

2. Its not that useful as is because the indicator is really only visible on the last post you've read in a topic. You have to scroll up and down to find it if you're not already there or entering the topic from the topic list.

So, there seem to be two main goals out of this:

1. The indicator should show which posts are read and which aren't.
2. It'd be nice to have a way to jump to the last read post from within a topic.

So here's an idea:

First, for the 'subtle but visible indicator'... 'a "you read this" indicator on each post', follow some conventions from email clients. Just style the name and date on each post differently for read vs unread: bold = unread normal = read

ec36aac68b09fdc2.png1760x160

b1aa15094c6a2205.jpg1760x160

(Ignore the funky outline/dropshadow... just a quick and dirty mock)

Having this indicator back at the top would help make it more clear that the state changes as you read the post like in the old days.

Then, to answer the issue of losing your place, what if the progress bar showed which the last read post was in a darker shade of green?

Clicking anywhere in the dark green region would bring you back to the last read post.

(I realize this second part of the discussion overlaps with the one going on here as well...)

Posts: 6

Participants: 2

Read full topic

Briancguy wrote:

We just upgraded our forums to 9.9.5 yesterday evening and I'm finding I'm getting a number of new strange notifications from "system" - which when I look at the messages are actually old postings by me - the admin, that were done months ago.

Very strange.

Posts: 3

Participants: 3

Read full topic

Hrvoje Šimić wrote:

Navigating from categories to topics and back is not consistent.

Steps to reproduce:

1. Browse some category
2. Click on any topic
3. Click the back button

I end up browsing top topics.

Cannot reproduce on try.discourse.org.

Posts: 5

Participants: 2

Read full topic

Alex Tonkonozhenko wrote:

Hello!

I've got existing Rails app, auth is made with Devise.
Is it possible to connect it with Discource for using my users for auth and getting Discourse details e.g. bages in my app?

Posts: 2

Participants: 2

Read full topic

Rafael Pereira wrote:

Silly question, how do I unblock an email?

Captura de Tela 2014-05-31 às 12.46.57.PNG1768x570 86.4 KB

Posts: 2

Participants: 2

Read full topic

versvs wrote:

Hi,

I'm facing a problem that has been tangentially treated in a previous thread, but to which I can't seem to find a solution.

I was running a legacy Discourse install (coming back from version 0.5-0.6 or so, but updated up to 0.9.8.5 if i remember well), installed using the then-fancy Ubuntu install guide. My server died mercilessly yesterday. I have backups... but not the kind of modern backups that Discourse sports today (no dashboard dump file), instead I have a postgresql dump and a lot of files.

As I intend to start from scratch using Docker now that destiny has given me the chance ( ), my problems are centered in getting back the public/uploads into a container. At the same time, I can restore my database into Postgresql, but I don't know how to make my containers use it.

In the previously linked thread we can find some solution that is in part what I need (as it delves into the problem of reconverting old installs into docker installs) and in part exactly what I dont need, as my server is dead and I don't have a running instance to which I can do this git/rake work.

I managed to get a docker install alive and running in 0.0.0.0:80, it is completely blank, any ideas on how may i get my database and uploaded files loaded and rake:migrated to the latest numbered version so I can do a proper dashboard export and reimport in the now recommended-easy way?

Thank you all in advance,

Posts: 12

Participants: 2

Read full topic

Adam Capriola wrote:

I'm working on pulling the "latest" feed onto the homepage of my site (which I think will look great – once I finish my redesign I'll share the integration), and I'm trying to figure out if there's a way to set the number of topics that should appear.

By default, it seems like 30 topics show on each "page":

https://meta.discourse.org/latest.json

And each page has a link to the next one:

https://meta.discourse.org/latest.json?no_definitions=true&page=1

So, since it appears you can add parameters, I did some searching and found more listed here, I think. I want to set per_page to something more than 30. I know I could make a call to each page, but it would be so much more convenient if I could just make one single call to retrieve the desired number of topics.

Is this doable? I couldn't get the output to budge with anything like this:

https://meta.discourse.org/latest.json?per_page=50

Posts: 1

Participants: 1

Read full topic

James Finstrom wrote:

When our moderators community lock a post I would like them to add a link at the bottom.

If you feel this message was locked in error please message the "abuse team"

The abuse team being select staff moderators who can review the action and make a decision on it

I saw in another search something about pm's to #group which doesn't seem to work it gives a message about arch type.

There is also no intuitive way to create a PM.

Ideally something like a link to: url/message/[recipient|group] that would bring up the pm compose to to the group would be excelent

Edit: should something like this work?

<a {{action composePrivateMessage user}}>PM</a>

Posts: 2

Participants: 2

Read full topic

Adam Capriola wrote:

Avatars are always displayed square, but I've had a number of users upload custom avatars that are not square, which then get distorted via CSS upon display and look kind of bad.

Are there any plans down the road for a cropper to make all custom uploaded avatars squares? (It's hip to be square...)

Posts: 3

Participants: 3

Read full topic

Peter Lewis wrote:

Would it be possible to add support for POP3 (non-s) (ie port 110).

On my server, discourse and the pop server are both on the same server, so there is no need to encrypt the session (anyone with access to the connection already has access to the data at either end). The POP3 server I use is a custom server that doesn't require unix-level accounts and so is very safe (any security issue would compromise only a minimal permission account).

I added support for POP3 in discourse simply be editing app/jobs/scheduled/poll_mailbox.rb near line 43:

 if SiteSetting.pop3s_polling_port.to_i != 110
   Net::POP3.enable_ssl(OpenSSL::SSL::VERIFY_NONE)
 end

Basically, if the port is 110, don't use SSL. Now obviously it would be better to have a UI switch for POP3/POP3s, but at least this got me working and proved that the change is trivial at the engine side.

Thanks.

Posts: 2

Participants: 2

Read full topic

Erlend Sogge Heggen wrote:

Continuing the discussion from Avatar Subsystem redesign.

For some reason, Sam's profile is using the letter avatar:

Screen Shot 2014-06-01 at 12.24.09.png2310x1168 231 KB

Mine is not.

Posts: 4

Participants: 3

Read full topic

Kiran Patil wrote:

Hello,

edx-platform(https://github.com/edx/edx-platform) is LMS(Learning management system) and we would like to use discourse as comment service and discussion forum.

We would like to know has anybody started the work on this line and if so please share it.

Thanks.

Posts: 1

Participants: 1

Read full topic

Matthew Jones wrote:

Hi there, on a docker install which was recently upgraded to 0.9.9.6 I'm seeing broken images when loading avatars with the following stack trace in the production_errors.log

<hash>
  <date type="dateTime">2014-06-01T15:15:00+00:00</date>
  <guid>a127484c-0a13-495c-a43b-8c993d25290b</guid>
  <user-id type="integer">2</user-id>
  <parameters>{"controller":"user_avatars","action":"show","hostname":"forums.online-go.com","username":"matburt","size":"50","version":"1"}</parameters>
  <action>show</action>
  <controller>user_avatars</controller>
  <backtrace>[RAILS_ROOT]/lib/file_helper.rb:10:in `download'
[RAILS_ROOT]/lib/file_store/s3_store.rb:52:in `download'
[RAILS_ROOT]/app/models/optimized_image.rb:20:in `create_for'
[RAILS_ROOT]/app/controllers/user_avatars_controller.rb:95:in `get_optimized_image'
[RAILS_ROOT]/app/controllers/user_avatars_controller.rb:68:in `show_in_site'
[RAILS_ROOT]/app/controllers/user_avatars_controller.rb:40:in `block in show'
[RAILS_ROOT]/vendor/gems/rails_multisite/lib/rails_multisite/connection_management.rb:44:in `with_hostname'
[RAILS_ROOT]/app/controllers/user_avatars_controller.rb:39:in `show'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/abstract_controller/base.rb:189:in `process_action'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_controller/metal/rendering.rb:10:in `process_action'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:113:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:113:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:149:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:149:in `block in halting_and_conditional'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:229:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:229:in `block in halting'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:149:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:149:in `block in halting_and_conditional'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:86:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:86:in `run_callbacks'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/abstract_controller/callbacks.rb:19:in `process_action'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_controller/metal/rescue.rb:29:in `process_action'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_controller/metal/instrumentation.rb:31:in `block in process_action'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/notifications.rb:159:in `block in instrument'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/notifications.rb:159:in `instrument'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/abstract_controller/base.rb:136:in `process'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.1/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.1/lib/action_controller/metal.rb:195:in `dispatch'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_controller/metal.rb:231:in `block in action'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/routing/route_set.rb:80:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/routing/route_set.rb:80:in `dispatch'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/routing/route_set.rb:48:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/journey/router.rb:71:in `block in call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/journey/router.rb:59:in `each'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/journey/router.rb:59:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/routing/route_set.rb:676: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/etag.rb:23:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/conditionalget.rb:25: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.1/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/middleware/flash.rb:254: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.1/lib/action_dispatch/middleware/cookies.rb:560:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/message_bus-0.9.4/lib/message_bus/rack/middleware.rb:55:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/query_cache.rb:36:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:621:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:82:in `run_callbacks'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/middleware/remote_ip.rb:76:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/logster-0.0.10/lib/logster/middleware/reporter.rb:23:in `call'
[RAILS_ROOT]/config/initializers/silence_logger.rb:24:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/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:193:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/railties-4.1.1/lib/rails/engine.rb:514:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/railties-4.1.1/lib/rails/application.rb:144:in `call'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/railties-4.1.1/lib/rails/railtie.rb:194:in `public_send'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/railties-4.1.1/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.2/lib/unicorn/http_server.rb:572: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.2/lib/unicorn/http_server.rb:666:in `worker_loop'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.2/lib/unicorn/http_server.rb:521:in `spawn_missing_workers'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.2/lib/unicorn/http_server.rb:140:in `start'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.2/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>url</message>
  <url>http://forums.online-go.com/user_avatar/forums.online-go.com/matburt/50/1.png</url>
  <exception-class>Discourse::InvalidParameters</exception-class>
</hash>

Posts: 3

Participants: 2

Read full topic

Travis wrote:

I have a landing page that I would like to display the signup for on. The conversion from a landing page to the forum to signing up is too far. If I could embed the sign up form directly on the site (an S3-hosted static site built with Middleman). I thought perhaps I could simply include the social sign in links but that doesn't work due to the callbacks.

Anyone done this or have any ideas about how I might achieve this?

Posts: 1

Participants: 1

Read full topic

Dror Deleon wrote:

Hi Discourse team,

Sorry to bother you with a well covered topic as "reply be email" but i bubbled around it and i could not make it work.
I followed the guides completely.
I have a google apps account where users can open topics with and its working fine.
The address it is using is discourse@mygoogleappsdomain.com
Replying to it when i get email notification (it comes from the Mandrill) but as configured in Discourse e-mail settings it will go to discourse+%{reply_key}@mygoogleappsdomain.com, and will result in a reply from google saying discourse+some numbers is not a valid address and there is no such user.

I have no idea if got the configuration correctly or if im missing something.

Much appreciate your help and advice.

Thanks,
Dror.

Posts: 2

Participants: 2

Read full topic

Justin Gordon wrote:

I've got a friend who used to work Facebook, and he told me that discourse should have a box at the bottom of each post to just click and start creating a reply, like Facebook and Disqus. He said it definitely makes a difference in terms of getting interaction.

If the user is not yet logged in, we could make it very easy to create an account to comment.

At the very minimum, this would be a great setting to turn on-off.

Remote_Pair_Programming_Tips_Using_RubyMine_and_Screenhero_-_Rails_on_Maui.jpg854x322 208 KB

Facebook.jpg512x584 295 KB

Posts: 4

Participants: 3

Read full topic

neekstah wrote:

I setup Discourse by following the Beginner Docker install guide for Digital Ocean.

I have DISCOURSE_HOSTNAME set to mydomain.com, without the preceding www, because my domain will always be used exclusively for a single install of Discourse and I prefer the shorter address. The problem is cookies from mydomain.com don't apply to www.mydomain.com and vice versa.

I want to redirect www.mydomain.com to mydomain.com. How do I do that?

Posts: 2

Participants: 2

Read full topic