@JeremyK wrote:

Hello everyone,

I'm using the Airport CEO Forum, which is running on Discourse. I think that it's great, but I'm experiencing a little bug lately. Sometimes when I reply to someone's post, it doesn't show up as a reply to that post/person, but just as a normal post/reply. There is however a little arrow with the username that shows that I'm replying to a user in the editor while typing..

I still couldn't figure out what's the cause of this or how I can reproduce this..

-Jérémy

Little update on this: the reply does however shows up as a reply on the post to which I'm replying (when I click on the little arrow that says for example '2 Replies [Arrow Down]'). So actually only the arrow and the username of the person to who I'm replying to in the upper right corner of my post is missing..

Posts: 4

Participants: 2

Read full topic

@kevinprow wrote:

So the blue blur around the avatar of the latest poster in a topic is only showing up if the person is displayed as the first avatar in the Users column (bold added for emphasis). Is there a reason for this? Or should it give the indicator regardless of the positioning of the avatar in the column?

.topic-list .posters **a:first-child** .avatar.latest:not(.single) {
    box-shadow: 0 0 3px 1px #acc2e3;
    border: 2px solid #8da9d3;
    position: relative;
    top: -2px;
    left: -2px;
}

Posts: 4

Participants: 2

Read full topic

@lkramer wrote:

Let's say you loads of informative articles in the Wordpress part of your site and then of course loads of informative conversations in the Discourse part of your site.

When you type a phrase into the Wordpress search box, it would be really cool if relevant Discourse threads could come up in addition to the relevant Wordpress articles.

Has anyone found a clever way to do this? This is not a deal breaker of course. It would just be really useful.

Posts: 1

Participants: 1

Read full topic

@RobMeade wrote:

Hi,

I wouldn't say this is a huge issue, but something that may be worth being aware of.

Whilst experimenting with the poll functionality this evening I initially assumed that the range was set at 1 to 20. I then noticed that increasing the step had a bearing on the max - which in turn, if you select the highest value has a bearing on the step - repeat this about 4 (I think) times and you can achieve this;

image.png721x447 16.3 KB

The whole browser locked up, presumably whilst hundreds more options were being dynamically added to the drop down menus. Eventually, given enough time, it responded again and I was quick to set it to something lower, but I'm guessing potentially I could keep raising these values to a literal breaking point.

As I say, it's not a massive issue, who would be silly enough to do this anyway right? (me! /waves) - I was actually in the process of writing a little guide on how to put the polls into your posts when I started experimenting.

Any reason these are drop down menus and not just text boxes with some validation that a number has been entered?

Oh, and as I am writing this in the context of the world revolving solely around myself - I'll add that having the Show Who Voted option in a different order for the Number Rating poll type compared to the Single Choice and Multiple Choice is playing havoc with my OCD (CDO)...!

---

Just spotted that when choosing the Multiple Choice type, you can select the Min value equal to the total number of options - meaning a user would have to select everything on the poll.

image.png715x461 13.1 KB

Posts: 3

Participants: 2

Read full topic

@watchmanmonitor wrote:

I've confirmed this on 4 invites.

• With an invite only site
• Operating as a site-admin
• Visit a topic
• invite a new user to that topic
• User accepts the invitation
• User shows in /admin/users/list/pending

I would expect the user to be pre-approved.

For what it's worth, this is a regression, as it didn't used to work this way, but I haven't invited someone in a few months at least.

Posts: 2

Participants: 2

Read full topic

@barryvan wrote:

At present, if you want to vote on a topic, you have to scroll up to the first post in that topic. It'd be great if you could vote at any time (not sure how that would work on mobile, though), or if the voting options were duplicated at the bottom of the topic. That way, you could read through the entire discussion before deciding whether or not to expend your vote.

Posts: 1

Participants: 1

Read full topic

@y2kenny wrote:

I understand Discourse has a concept of group and there are ldap plugin out there. Is there a way to use existing ldap distribution lists as groups without recreating them in Discourse?

Posts: 1

Participants: 1

Read full topic

@pfaffman wrote:

I'm trying to improve the permalink redirects on the vbulletin importer. Vbulletin can have any of several URL formats. My solution is to create generic permalinks which will then be handled by permalink normalizations. Like this:

Old URL: http://somesite/forums/f38/slug-blah-blah-blue-11769.html
Permalink: oldlinks/topics/thread-11769

Normalization: /forums\/f[0-9]+\/.+-([0-9])+\.html.*/oldlinks\/topics\/thread-\1

It looks like it should work to me, but it's not.

Have I missed a character somewhere?

Posts: 4

Participants: 2

Read full topic

@modius wrote:

Continuing the discussion from Set up reply via email support:

Am in need of a sanity check

I have set up a dedicated Google Apps account with aliases configured in Discourse in the following way:

• hello@gorgeous.com --> bound to a private group hello
• alias dev@gorgeous.com --> bound to a category dev

We're merging in a mailing list, and the dev category will represent that traffic. To create a new post in the category you have to email the alias dev@gorgeous.com

Everything is working as expected.. only when i look at my settings for reply by email address i have second thoughts:

Admin_-_Lucee_Dev.jpg740x216 38.2 KB

All reply-to traffic is going to hello@gorgeous.com -- would i be better off making all reply-to traffic go through dev@gorgeous.com instead?

At this point it seems counter intuitive to be creating topics through an email address that is different to the reply-to address. Has anyone got any real world experience in this area?

Posts: 2

Participants: 2

Read full topic

@meglio wrote:

Ecwid is a server-less shopping cart:

I would use it as means for our users to embed their mini-shopping-carts right into their "personal pages-topics".

It can be embedded with inserting JS / HTML embed code.

Would be interesting to see how it fits into:

• Discourse infinite scroll
• Ember automatic DOM update

Posts: 1

Participants: 1

Read full topic

@meglio wrote:

We use the split screen for our home page: the left column is the list of categories, the right column is the list of latest topic updates.

I would like to exclude topics from some categories from the topics list, but only when viewed at home page.

Is it possible?

If not, this is a feature request then.

Posts: 1

Participants: 1

Read full topic

@meglio wrote:

image.png1744x198 18.5 KB

There is no exact reproduction steps. What I did is changed message ownership of all public messages of a given user, then tried to delete the user.

The system wouldn't delete the user.

The "Remove all user messages" button wouldn't help (it would reset the counter to 0, but after page refresh it becomes negative again).

Possibly related error

Message

ActiveRecord::StatementInvalid (PG::TRDeadlockDetected: ERROR: deadlock detected
DETAIL: Process 18791 waits for ShareLock on transaction 80120169; blocked by process 18704.
Process 18704 waits for ShareLock on transaction 80120168; blocked by process 18791.
HINT: See server log for query details.
CONTEXT: while updating tuple (12077,4) in relation "posts"
: UPDATE "posts" SET like_count = 24, like_score = 26 WHERE ("posts"."deleted_at" IS NULL) AND "posts"."id" = 129201)
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/lib/patches/db/pg.rb:93:in `exec'
Backtrace

/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/lib/patches/db/pg.rb:93:in exec'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/lib/patches/db/pg.rb:93:inasync_exec'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/postgresql_adapter.rb:592:in block in exec_no_cache'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract_adapter.rb:484:inblock in log'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/notifications/instrumenter.rb:20:in instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract_adapter.rb:478:inlog'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/postgresql_adapter.rb:592:in exec_no_cache'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/postgresql_adapter.rb:584:inexecute_and_clear'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/postgresql/database_statements.rb:173:in exec_delete'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/database_statements.rb:114:inupdate'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/query_cache.rb:14:in update'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/relation.rb:345:inupdate_all'
/var/www/discourse/app/models/post_action.rb:426:in update_counters'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:432:inblock in make_lambda'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:228:in block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:506:inblock in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:506:in each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:506:incall'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:92:in __run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:778:inrunsave_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/callbacks.rb:302:in create_or_update'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/persistence.rb:120:insave'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/validations.rb:37:in save'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/attribute_methods/dirty.rb:21:insave'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:286:in block (2 levels) in save'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:351:inblock in with_transaction_returning_status'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/database_statements.rb:211:in transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:220:intransaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:348:in with_transaction_returning_status'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:286:inblock in save'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:301:in rollback_active_record_state!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:285:insave'
/var/www/discourse/app/models/post_action.rb:326:in remove_act!'
/var/www/discourse/app/services/user_destroyer.rb:51:inblock (2 levels) in destroy'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/relation/delegation.rb:46:in each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/relation/delegation.rb:46:ineach'
/var/www/discourse/app/services/user_destroyer.rb:50:in block in destroy'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/database_statements.rb:213:inblock in transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/transaction.rb:184:in within_new_transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/database_statements.rb:213:intransaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:220:in transaction'
/var/www/discourse/app/services/user_destroyer.rb:21:indestroy'
/var/www/discourse/app/controllers/admin/users_controller.rb:258:in destroy'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/implicit_render.rb:4:insend_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/abstract_controller/base.rb:198:in process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rendering.rb:10:inprocess_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/abstract_controller/callbacks.rb:20:in block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:117:incall'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:555:in block (2 levels) in compile'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:505:incall'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:92:in __run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:778:inrunprocess_action_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:81:in run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/abstract_controller/callbacks.rb:19:inprocess_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rescue.rb:29:in process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/instrumentation.rb:32:inblock in process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/notifications.rb:164:in block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/notifications/instrumenter.rb:20:ininstrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/notifications.rb:164:in instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/instrumentation.rb:30:inprocess_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/params_wrapper.rb:250:in process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/railties/controller_runtime.rb:18:inprocess_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/abstract_controller/base.rb:137:in process'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/rendering.rb:30:inprocess'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/lib/mini_profiler/profiling_methods.rb:102:in block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal.rb:196:indispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rack_delegation.rb:13:in dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal.rb:237:inblock in action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/routing/route_set.rb:74:in dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/routing/route_set.rb:43:inserve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/routing/mapper.rb:49:in serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/journey/router.rb:43:inblock in serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/journey/router.rb:30:in each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/journey/router.rb:30:inserve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/routing/route_set.rb:817:in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:incall'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:incall'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:incall'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:incall'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:incall'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:incall'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:incall'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/builder.rb:63:in call'
/var/www/discourse/config/initializers/008-rack-cors.rb:15:incall'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/conditionalget.rb:38:in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/head.rb:13:incall'
/var/www/discourse/lib/middleware/anonymous_cache.rb:138:in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/params_parser.rb:27:incall'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/flash.rb:260:in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/session/abstract/id.rb:225:incontext'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/session/abstract/id.rb:220:in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/cookies.rb:560:incall'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/query_cache.rb:36:in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:653:incall'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/callbacks.rb:29:in block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:88:inrun_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:778:in _run_call_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:81:inrun_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/callbacks.rb:27:in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/remote_ip.rb:78:incall'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/debug_exceptions.rb:17:in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/show_exceptions.rb:30:incall'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/logster-1.2.7/lib/logster/middleware/reporter.rb:31:in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/rack/logger.rb:38:incall_app'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/rack/logger.rb:22:in call'
/var/www/discourse/config/initializers/100-quiet_logger.rb:17:incall_with_quiet_assets'
/var/www/discourse/config/initializers/100-silence_logger.rb:29:in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/request_id.rb:21:incall'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/methodoverride.rb:22:in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/runtime.rb:18:incall'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/sendfile.rb:113:in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/lib/mini_profiler/profiler.rb:278:incall'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus/rack/middleware.rb:62:in call'
/var/www/discourse/lib/middleware/request_tracker.rb:73:incall'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/engine.rb:518:in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/application.rb:165:incall'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/railtie.rb:194:in public_send'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/railtie.rb:194:inmethod_missing'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/urlmap.rb:66:in block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/urlmap.rb:50:ineach'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/urlmap.rb:50:in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/lib/unicorn/http_server.rb:562:inprocess_client'
/var/www/discourse/lib/scheduler/defer.rb:85:in process_client'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/lib/unicorn/http_server.rb:658:inworker_loop'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/lib/unicorn/http_server.rb:508:in spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/lib/unicorn/http_server.rb:519:inmaintain_worker_count'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/lib/unicorn/http_server.rb:283:in join'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/bin/unicorn:126:in'
/var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:22:in load'
/var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:22:in'
Env

hostname kozovod-app
process_id 21588
application_version b2cfad5f47e6335ba514297517fa20e84dd004a8
HTTP_HOST forum.kozovod.com
REQUEST_URI /admin/users/1593.json
REQUEST_METHOD DELETE
HTTP_USER_AGENT Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
HTTP_ACCEPT /
HTTP_REFERER http://forum.kozovod.com/admin/users/1593/bobrovchanka
HTTP_X_FORWARDED_FOR 103.192.193.144
HTTP_X_REAL_IP 103.192.193.144
username meg
params
context /admin/users/1593/bobrovchanka

Posts: 1

Participants: 1

Read full topic

@Gareth_Williams wrote:

Hey All,

I have managed to import our entire history of VBulletin across to an install of Discourse.

We have it setup via Docker on AWS and all has been going well however, we suddenly have an issue with the site becoming unstable - I have been unable to browse the site intermittently. Now the site isnt running at all and I have been going for the nuclear option, I have tried running a rebuild however, it just sits there.

From what I can see, every time the command is run it spins up a new docker container without taking down the previous one:

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
bc0aa2a365ed discourse/discourse:1.3.10 "echo working" 27 minutes ago Up 27 minutes keen_mclean
1f668baf3c33 discourse/discourse:1.3.10 "echo working" 40 minutes ago Up 40 minutes gifted_lewin
8818eedd48ae discourse/discourse:1.3.10 "echo working" About an hour ago Up About an hour romantic_gates
42993e97fa78 discourse/discourse:1.3.10 "echo working" 2 hours ago Up 2 hours elegant_goldwasser
1e94ce3fa47f discourse/discourse:1.3.10 "echo working" 3 hours ago Up 3 hours epic_haibt
0e4b77f62034 discourse/discourse:1.3.10 "echo working" 15 hours ago Up 15 hours affectionate_bhabha
075ec3cd4ff2 discourse/discourse:1.3.10 "echo working" 16 hours ago Up 15 hours adoring_pike
4076a433cfbf samsaffron/docker-gc "/docker-gc" 21 hours ago Up 21 hours angry_newton
a8d0cf73d03a local_discourse/app "/sbin/boot" 27 hours ago Up 21 hours 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp app

As you will see the last few containers all seem to have halted when running an "echo working" command. Is this something anyone has come across at all? Any Ideas on what I should be trying?

Posts: 3

Participants: 2

Read full topic

@Callahan wrote:

Hello,
We've been running into this problem where if you change your external name, it will still show your old name on the forums. We've tried changing the name, logging out of the forums, then logging back in but that still didn't work. I was thinking it was the "sso overrides username" but that's already ticked.. any ideas?

Posts: 4

Participants: 2

Read full topic

@Philip_Colmer wrote:

One of our Discourse platforms crashed last night. A restart got it working again but I'd like to try and better understand what caused the problem, particularly if that helps the code improve.

Unfortunately, I can't see anything in the logs that hints at Discourse actually crashing. The logs continue to show messages even after a site admin had reported that Discourse was down and all we were getting was 500 errors.

There are lots of warnings like this:

failed to deliver message, skipping #<struct MessageBus::Message global_id=321617, message_id=3795, channel="/site_settings", data={"process"=>"d9ded469-6c45-4cca-9dcf-3e18b949f182"}>
ex: no implicit conversion of nil into String backtrace: ["/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/connection/hiredis.rb:19:in `connect'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/connection/hiredis.rb:19:in `connect'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:336:in `establish_connection'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:101:in `block in connect'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:293:in `with_reconnect'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:100:in `connect'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:364:in `ensure_connected'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:221:in `block in process'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:306:in `logging'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:220:in `process'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:120:in `call'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis.rb:494:in `block in del'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis.rb:58:in `block in synchronize'", "/usr/local/lib/ruby/2.3.0/monitor.rb:214:in `mon_synchronize'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis.rb:58:in `synchronize'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis.rb:493:in `del'", "/var/www/discourse/lib/discourse_redis.rb:192:in `block in del'", "/var/www/discourse/lib/discourse_redis.rb:146:in `ignore_readonly'", "/var/www/discourse/lib/discourse_redis.rb:190:in `del'", "/var/www/discourse/lib/cache.rb:53:in `delete_entry'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/cache.rb:402:in `block in delete'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/cache.rb:547:in `block in instrument'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/notifications.rb:166:in `instrument'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/cache.rb:547:in `instrument'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/cache.rb:401:in `delete'", "/var/www/discourse/lib/site_setting_extension.rb:379:in `clear_cache!'", "/var/www/discourse/lib/site_setting_extension.rb:235:in `block in refresh!'", "/var/www/discourse/lib/site_setting_extension.rb:216:in `synchronize'", "/var/www/discourse/lib/site_setting_extension.rb:216:in `refresh!'", "/var/www/discourse/lib/site_setting_extension.rb:254:in `process_message'", "/var/www/discourse/lib/site_setting_extension.rb:242:in `block in ensure_listen_for_changes'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus.rb:535:in `block (2 levels) in global_subscribe_thread'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus.rb:549:in `each'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus.rb:549:in `block in multi_each'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus.rb:548:in `each'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus.rb:548:in `multi_each'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus.rb:533:in `block in global_subscribe_thread'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus/backends/redis.rb:331:in `block (2 levels) in global_subscribe'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/subscribe.rb:45:in `block in subscription'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:141:in `block (3 levels) in call_loop'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:135:in `loop'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:135:in `block (2 levels) in call_loop'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:231:in `block (2 levels) in process'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:367:in `ensure_connected'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:221:in `block in process'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:306:in `logging'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:220:in `process'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:134:in `block in call_loop'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:280:in `with_socket_timeout'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:133:in `call_loop'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/subscribe.rb:43:in `subscription'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/subscribe.rb:12:in `subscribe'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis.rb:2760:in `_subscription'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis.rb:2138:in `block in subscribe'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis.rb:58:in `block in synchronize'", "/usr/local/lib/ruby/2.3.0/monitor.rb:214:in `mon_synchronize'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis.rb:58:in `synchronize'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis.rb:2137:in `subscribe'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus/backends/redis.rb:304:in `global_subscribe'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus.rb:513:in `global_subscribe_thread'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus.rb:461:in `block in new_subscriber_thread'"]

and quite a few "fatal" messages like this:

TypeError (no implicit conversion of nil into String)
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/connection/hiredis.rb:19:in `connect'

Does the fact that it was still logging suggest that it wasn't Discourse itself but, perhaps, nginx that was the cause of the failure? Where do I need to look to pin this down further?

Thanks.

Posts: 1

Participants: 1

Read full topic

@alonle wrote:

Hi @team, Is there any way to catch click event on a link and fire a pixel to google adwords.
I want to know if user click on an amazon link on my site.

I saw this topic

Anything similar to this code can be done with a link? (html a href)

Thanks

Posts: 2

Participants: 2

Read full topic

@zbor wrote:

Is it possible to have additional info around user name in the post?

Something like Full name but other required field...
That will have priority upon name, location, info.. etc...

Posts: 1

Participants: 1

Read full topic

@michaeld wrote:

Since 1.7 we sometimes see processes losing their Redis connection and from that moment on, they're unable to reconnect until the process is restarted.

This is what we are seeing in the logs.

Failed to report error: no implicit conversion of nil into String 4 TypeError (no implicit conversion of nil into String)
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/connection/hiredis.rb:19:in 'connect' web-exception

And

Unexpected error while processing request: no implicit conversion of nil into String
        /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/connection/hiredis.rb:19:in `connect'
        /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/connection/hiredis.rb:19:in `connect'
        /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:336:in `establish_connection'
        /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:101:in `block in connect'
        /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:293:in `with_reconnect'
        /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:100:in `connect'
        /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:364:in `ensure_connected'
        /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:221:in `block in process'
        /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:306:in `logging'
        /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:220:in `process'
        /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:120:in `call'
        /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis.rb:1794:in `block in zrangebyscore'
        /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis.rb:58:in `block in synchronize'
        /usr/local/rvm/rubies/ruby-2.3.1/lib/ruby/2.3.0/monitor.rb:214:in `mon_synchronize'
        /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis.rb:58:in `synchronize'
        /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis.rb:1793:in `zrangebyscore'
        /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus/backends/redis.rb:195:in `backlog'
        /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus.rb:291:in `backlog'
        /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus/client.rb:122:in `block in backlog'
        /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus/client.rb:120:in `each'
        /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus/client.rb:120:in `backlog'
        /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus/rack/middleware.rb:135:in `call'

Now there are no memory issues, no config file changes, and last but not least: redis is working perfectly fine. It can be accessed by the other running processes as well. This only happens to a single process on a machine.

Yes, unsupported install, but does anyone have any idea what might be causing this? It almost feels like a memory corruption issue. This is only happening on 3 or 4 of our servers.

Posts: 3

Participants: 2

Read full topic

@zsero wrote:

Super boring standard setup, logs:
https://bpaste.net/show/18f2bfdb37ce

Posts: 6

Participants: 4

Read full topic

@JagWaugh wrote:

The seen/unseen filter is great.

Would it be a great deal of work to include a groups filter? It wouldn't need any UX real estate, it could just be a part of "Posted by".

Posts: 3

Participants: 2

Read full topic