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

Job exception: connection refused - connect(2)


New Unhide Feature

0
0

cpradio wrote:

Continuing the discussion from No mod option to unhide a post:

Can I get some clarification? Does this apply to both of the following scenarios?
Scenario 1
When a post is hidden by the community (3 flags by 3 users), there isn't a way for Mods to unhide it (that we can find -- we think there is supposed to be)

Scenario 2
When a mod flags a post (or agrees with a flag) and chooses Take Action, we have no way to unhide that post (should we make a mistake or edit the post ourselves).

Posts: 4

Participants: 3

Read full topic

Discourse Vs MUUT vs other

0
0

Mick Coll wrote:

I really like Discourse... a lot, and I want to use it in a project but I find the journey to activation pretty intimidating / frustrating. As such, in the project I am building I chose MUUT as the forum. It was literally setup and installed on the site in minutes.

The project isn't live yet so the choice of forum isn't set in stone, but is there no easier way than renting a server and booting up docker instances etc to get discourse into my project? Have I missed something? I realise there is a paid hosted solution but $100 a month might as well be $100000000 a day for how realistic it is to this project.

If MUUT can do so much, so easily, and for free... why can't discourse? Discourse and MUUT seem to be the only players on the field right now in terms of next gen forum software but MUUT makes it so easy for people, I don't see how discourse can thrive, which is a shame as it is my preferred product.

Posts: 4

Participants: 3

Read full topic

How long do the tests take? "master" to "tests-pass"

0
0

Dean Taylor wrote:

Currently waiting a commit to become available on the "tests-pass" branch on GitHub.

Just wondering: how long it takes for tests to go from commit on master to available on "tests-pass"?

Thanks.

Posts: 4

Participants: 2

Read full topic

Onebox: Github blob - Line Number

0
0

lid wrote:

I started off fixing the wrong lines bug and I got carried a way and introduced an option to also show line numbers.

Thinking I can just add line numbers in the beginning of each line and off I go, everybody happy blush
Highlight.js is the library used by Discourse to highlight code block on the fly. It is a pretty nice and powerful library but it does not support any sort of line numbering functionality. Adding the line number as I learnt breaks the lingual detection and syntax highlighting.

First Try

My first approach was to try to trick highlight.js to treat my line numbers as line comments.
so I created a table, placed the line number on the 2nd column. and using css float the line number back to the left.

td.code {
float:right;
}
td.line_number{
float:left;
}

This solution sort of worked, but it is not the ideal solution. things will go ugly when the window width scale down.
And highlight.js will count the comment when it decide which language it is highlighting.

Second Try / Approach

In the onebox template, instead of adding the line number as a content, I added it as an attribute to the column.

Using a delayed jQuery procedure with the hope that it will be enough for highlight.js finished processing my onebox. I Then change the content of the TD to its "line_number" attribute value.

This way we don't have to use CSS trick and dangerous floats and word wrapping. We can use a proper stable markup. and highlight will have the proper content to work with. The only challenge here is to make sure the delay is sufficient.

I liked this overall approach, but we do have to inject JS from onebox.
with delay and such.

<table>
<tr>
<td line_number="5"></td>
<td>Some Code Line</td>
</tr>
</table>

Final approach

I asked myself is there a better way? can we avoid using JavaScript? at least fundamentally?
You didn't read this far just to hear "no" did you ?

So yes, we can have a css a pure css solution that will give us the following and will allow highlight.js
to properly highlight the syntax.

I did want to give Onebox a more robust way to be embedded without the complication of custom or external css dependencies.

$.onebox client Helper

So I wrote an helper for onebox to load embedded styling.
Now the problem with onebox is that we can have more then one box on the same page.
that mean that the code below will run for each box. but the helper is smart enoghe to only add a style once.

We can also add the $.onebox definition in the onebox template. and it will only be defined if not defined previously.

//define $.onebox here or externally
cssRule =  "b { color:red} ";
$.Onebox.loadStyle("make_bold_red",cssRule);

The full source of the $.onebox helper can be seen here.
https://gist.github.com/lidlanca/5a17d77ed8654d408e54

Onebox Githob blob using $.onbox helper

The CSS rule is a little bit lengthier, and this is how it will look.
So we are using js to load styling, but the number are actually generated by CSS
and an Ordered List.

if you are curious you can have a look here how it works. this is basically the code that will be used by the onebox.
http://jsfiddle.net/lid0/qa6dvpzo/

An Interesting fetug is that empty lines does not show, this is why for example we jump from line 228 to line 231 .
it makes code more compact smirk

Now all that is left is to actually push this PR and hope that it doesn't fail facepunch

I personally think that syntax highlight could have moved to the ruby side, but it will add more dependency to Discourse / Onebox. The advantages is that the client side will have much less efforts rendering pages with code. specially for low end devices.

rouge A pure-ruby code highlighter that is compatible with pygments


Continuing the discussion from Github onebox shows wrong lines:

Posts: 2

Participants: 2

Read full topic

Rebuilding app fails at db:migrate with unique constraint 'badges_pkey' error

0
0

etewiah wrote:

I just now tried to rebuild my docker installation with the following command:

./launcher rebuild app

When it gets to running db:migrate, the following error regarding the unique constraint "badges_pkey" occurs:

I, [2014-09-23T02:09:50.362876 #47]  INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate'
2014-09-23 02:10:05 UTC ERROR:  duplicate key value violates unique constraint "badges_pkey"
2014-09-23 02:10:05 UTC DETAIL:  Key (id)=(1) already exists.
2014-09-23 02:10:05 UTC STATEMENT:  INSERT INTO "badges" ("badge_type_id", "created_at", "id", "name", "query", "system", "trigger", "updated_at") VALUES ($1, $2, $3, $4, $5, $6, $7, $8) RETURNING "id"
rake aborted!
ActiveRecord::RecordNotUnique: PG::Error: ERROR:  duplicate key value violates unique constraint "badges_pkey"
DETAIL:  Key (id)=(1) already exists.
: INSERT INTO "badges" ("badge_type_id", "created_at", "id", "name", "query", "system", "trigger", "updated_at") VALUES ($1, $2, $3, $4, $5, $6, $7, $8) RETURNING "id"

Can anyone give me some pointers as to how I can go about resolving this please?

Thanks

Posts: 22

Participants: 3

Read full topic

How many concurrent users are supported in discourse?

0
0

ginger man wrote:

I am going to start a community for my college with discourse. I like to use discourse as a private forum with logins.

Can someone points to the concurrent user limit for Digital Ocean 1 GB & 2 GB plans especially for private forums ?

What about discourse.org hosting ? How many concurrent users is benchmarked for standard & business plans ? @codinghorror can you shed some light here?

@michaeld your inputs on discoursehosting for different plans will also be useful.

Posts: 2

Participants: 2

Read full topic

Is anyone working on a Discourse Wiki?

0
0

Peter Lewis wrote:

I would love to replace my Mediawiki installation with a Discourse styled wiki. Same CommonMark preview/editor, similar Discourse look and feel, etc.

It doesn't seem to me that just using Discourse with "wiki" posts would be a suitable solution as a replacement for a wiki, but perhaps someone is trying to do that.

Anyway, I hope that is on the development plan somewhere!

Posts: 3

Participants: 3

Read full topic


How to allow particular file types for moderators only?

0
0

Anton wrote:

Is there a way to only allow, say, Word and Excel files to be uploaded by moderators and admins only, but not by end users?

Posts: 1

Participants: 1

Read full topic

Discourse Markdown does not see lists without a proceeding blank line

0
0

Peter Lewis wrote:

If you type:

This is a list:
* one
* two

You get this non-list result:

This is a list:
* one
* two

For some reason Markdown on Discourse requires a blank line before the list, like this:

This is really a list:

* one
* two

Which gives this:

This is really a list:

  • one
  • two

I checked on CommonMark, and confirmed its "Try" behaves correctly. Reading the spec is unclear (surprise, surprise - a spec that doesn't actually answer the case you're looking at, like every other spec in existence). Section 4.8 says "A sequence of non-blank lines that cannot be interpreted as other kinds of blocks forms a paragraph", and clearly those lines can be interpreted as a list block, so presumably that is definitive enough, as is 4.9 which says "Blank lines between block-level elements are ignored, except for the role they play in determining whether a list is tight or loose."

In any event, if the CommonMark spec for the above (without a line break) does not define it to be a list, then its pretty silly IMNVHO, and this catches me out regularly when posting, especially as the Preview look and the rendered look, and the email results are all very different (and get worse which is bad).

Posts: 3

Participants: 2

Read full topic

Formatting issue if quoted post contains more than one quote

0
0

TechnoBear wrote:

I apologise if this has been reported already, but I couldn't find it anywhere.

If I quote a post which itself contains more than one quote - sequentially, not nested - only the first quote is correctly displayed; subsequent quotes show the markup/markdown.

For example:

Oh - I've just realised it corrects if you use the arrow to expand and reveal the initial quote.

OK - if the first quote is not at the top of the post, it appears that it is missing altogether. (It is not intuitive to click to expand, where there appears to be missing text mid-post.)

One of our members noticed this issue in the preview window and tried to edit in the "missing" quote manually. In that case there is (of course) no "expand", and the second quote does not format.

[quote=poes]Well, Bear said
>a lot of nonsense as usual

to which Somebody replied
>I thought you were smarter than the average bear?[/quote]

gives me

Try that with quote tags:

[quote=poes]Well, Bear said
[quote=Bear]a lot of nonsense as usual[/quote]
to which Somebody replied
[quote=Somebody]I thought you were smarter than the average bear?[/quote]
[/quote]

Posts: 1

Participants: 1

Read full topic

Autosave settings

0
0

Andy Routledge wrote:

What are the default autosave settings for the editor?

It appears to save after 2 seconds of inactivity.

Posts: 1

Participants: 1

Read full topic

"Download Remote Images" setting reset during upgrade?

0
0

Dean Taylor wrote:

It's starting to feel like the download_remote_images_to_local setting is reset during the docker upgrade process.

I keep on having to turn the setting back "on".

It doesn't look like anybody else is turning it off...

Any ideas?

Cheers,
Dean.

Posts: 10

Participants: 3

Read full topic

Why is hosting so expensive?

0
0

Salman, Freelance Developer wrote:

I was exciting that discourse would be a hosted service (run by the founders), but the price point seems very high at this point .
$100 for 100K page views
$200 for 250K page views
etc.

I'm curious, is the cost of hosting so high because of Rails? I was hoping for something in the $30-50 a month range as it is much easier to sell to clients in that price range

Are there future plans to have lower the pricing or it is probably going to be like this going forward also?

I realize that you are free to charge whatever you want but just trying to get an understanding (assuming this is a topic you wish to discuss openly).

P.S I know I can self-host or go with other hosting providers but who wouldn't want to host with the founders of the software as theoretically they should be the best at it.

Posts: 3

Participants: 3

Read full topic

Search results need a visited link color


Unable to add existing users to private message with SSO enabled

0
0

Dean Taylor wrote:

When SSO is enabled the ability to Invite Others... is removed from private message topics.

This should not occur - it should only limit the ability to invite via email adding users that exist already should not be prevented.

The Invite Others... button exists here when SSO is disabled.

Steps to Reproduce

  1. Enable SSO
  2. Visit existing PM

Actual Results

Invite Others... button is missing.

Expected Results

Invite Others... to exist and when dialog is displayed only allow input of existing usernames / email addresses - prompting the user with a message if the user doesn't already exist in the system.

Related post

Possible duplicate of this post - but the previous post is not explicit regarding SSO in it's initial post - nor that it is a bug.

Posts: 1

Participants: 1

Read full topic

500 Error fetching gravatar after enabling s3 (1.1.0b2 / 1.1.0b3)

0
0

mike w wrote:

Hi there,

As far as I can tell this is a reoccurrence of this issue although no steps there resolved it for me.

It also sounds like it could be this issue. Updating to 1.1.0b3 has not helped (see full steps below).

Synopsis:

  • Discourse v1.1.0b2
  • Brand new install using docker + digital ocean

Repro steps:

  1. Create first account, log in.
  2. Settings -> Files: Set
    • enable s3 uploads, s3 access key id, s3 secret access key, s3 upload bucket
  3. Tried uploading media in thread -- failed due to wrong upload bucket. Fixed this (not sure if significant).
  4. Gravatars are broken (eg in the "Welcome to Discourse" system thread); 500 error (traceback below).
  5. Normal profile uploads and media work as expected (and are uploaded to s3).

I noticed 1.1.0b3 was just released, went through docker upgrade, and for good measure ran RAILS_ENV=production bundle exec rake avatars:clean avatars:refresh. However I still get the following traceback:

URL
GET http://myhostname/user_avatar/myhostname/system/90/1.png

TRACEBACK
Discourse::InvalidParameters (url)

/var/www/discourse/lib/file_helper.rb:10:in `download'
/var/www/discourse/lib/file_store/s3_store.rb:52:in `download'
/var/www/discourse/app/models/optimized_image.rb:20:in `create_for'
/var/www/discourse/app/controllers/user_avatars_controller.rb:93:in `get_optimized_image'
/var/www/discourse/app/controllers/user_avatars_controller.rb:65:in `show_in_site'
/var/www/discourse/app/controllers/user_avatars_controller.rb:40:in `block in show'
/var/www/discourse/vendor/gems/rails_multisite/lib/rails_multisite/connection_management.rb:44:in `with_hostname'
/var/www/discourse/app/controllers/user_avatars_controller.rb:39:in `show'
/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: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: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: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:119: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/config/initializers/silence_logger.rb:24: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>'

Suggestions welcome!

Posts: 1

Participants: 1

Read full topic

How the debugging bar works? And how to hide it?

0
0

Caue Rego wrote:

You know, that little floating bar on the top-left, if you're an admin:

What triggers it to appear? What are we supposed to do with it? And how can we make it go away?

This is probably a very newbie question, but I couldn't find any info about it.

It does look like an awesome debugging tool if I knew what the data meant (i.e. I was actually active on github). stuck_out_tongue

Posts: 4

Participants: 3

Read full topic

Python 3 - SSO Helper Class

Should category go below the topic title on the topic page?

0
0

Jeff Atwood wrote:

I find that over time I've started to really dislike our categories-in-front design.

Category is very important, but putting it in front of the title might be a bit too strong. What if category was, instead, just below the title?

The sizing is probably fine as-is on the page but in the scrolled down docked header, things would need to shrink a bit.

Not proposing any change to the topic list page at the moment, just thinking about this for the topic page.

Posts: 12

Participants: 6

Read full topic

Viewing all 60279 articles
Browse latest View live




Latest Images