@thangngoc89 wrote:

In the unpinned topic, the icon is was hidden a bits by site logo. Maybe a little padding would help.

Tested with Firefox, Chrome, IE

Posts: 1

Participants: 1

Read full topic

@scottfsmith wrote:

I have one user regularly getting a 403 error when trying to post a new topic or reply to a post. At the point of the error there is also a CSRF warning in the log file. He is using the latest IE (11.0.17). Here is the log env at the point of the warning ("Can't verify CSRF token authenticity"):

HTTP_HOST: www.growingfruit.org
REQUEST_URI: /draft.json
REQUEST_METHOD: POST
HTTP_USER_AGENT: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko
HTTP_ACCEPT: */*
HTTP_REFERER: http://www.growingfruit.org/t/scott-can-you-help-forestandfarm-with-issue-on-reply-of-posting/656/3
HTTP_X_FORWARDED_FOR: 108.56.173.122, 172.17.42.1
HTTP_X_REAL_IP: 172.17.42.1

params:
  draft_key: topic_656
  data: {"reply":"I just tested trying to post to the Roger Meyers Jujubes thread and got the 403 error.","ac
  sequence: 1

Note this reply didn't show up on the thread, this issue is often (but not always) preventing this user from posting.

Here is the log backtrace for what its worth:

/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-0.1.8/lib/logster/logger.rb:47:in `add'
/usr/local/lib/ruby/2.0.0/logger.rb:445:in `warn'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_controller/metal/request_forgery_protection.rb:196:in `verify_authenticity_token'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:424:in `block in make_lambda'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:160:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:160:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:86:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:86:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/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.9/lib/active_support/notifications.rb:159:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/notifications.rb:159:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/abstract_controller/base.rb:136:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.9/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.3/lib/mini_profiler/profiling_methods.rb:106:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_controller/metal.rb:232:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/routing/route_set.rb:82:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/routing/route_set.rb:82:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/routing/route_set.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/journey/router.rb:73:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/journey/router.rb:59:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/journey/router.rb:59:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/routing/route_set.rb:685:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/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:35: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:123:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/flash.rb:254:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.6/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.9/lib/action_dispatch/middleware/cookies.rb:562:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/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.9/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:82:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/remote_ip.rb:76:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-0.1.8/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.9/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.9/lib/rails/rack/logger.rb:22:in `call'
/var/www/discourse/config/initializers/quiet_logger.rb:10:in `call_with_quiet_assets'
/var/www/discourse/config/initializers/silence_logger.rb:26:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/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.3/lib/mini_profiler/profiler.rb:276:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:70:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.9/lib/rails/engine.rb:514:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.9/lib/rails/application.rb:144:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.9/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.9/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/scheduler/defer.rb:85:in `process_client'
/var/www/discourse/lib/middleware/unicorn_oobgc.rb:95:in `process_client'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:670:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:525:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:140:in `start'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/bin/unicorn:126:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in `load'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in `<main>'

Posts: 2

Participants: 2

Read full topic

@DeanMarkTaylor wrote:

When a private message is received in Discourse it looks like this:

Pasted image783x529 69 KB

Note the list of users.

When the private message notification is received by Email - it is not clear if there are other recipients.

I would suggest that a list of other recipients is included to avoid any confusion.

Posts: 3

Participants: 2

Read full topic

@riking wrote:

@sam it's bad that one rogue query can stop all the daily badges, people should get a /admin alert for this

Posts: 4

Participants: 2

Read full topic

@evannak wrote:

I'm trying to post a topic with this title "សាលា​ដំបូង​​​រាជ​​​ធានី​​​ចាប់​​​ផ្តើម​​​សវនាការ​​​ជុំ​​​នះ​​​ជម្រះ​​​សកម្ម​​​ជន​​​ និង​​​តំណាង​​​រាស្ត្រ​​​គណបក្ស​​​ប្រឆាំង​​​ពីបទ​​​កុបកម្ម​​​" in khmer khmer unicode. but it always shows this message.

descriptive.JPG770x145 18.2 KB

I think that it might be because of title field doesn't recorgnize the zwsp that is why it need more spaces.

Posts: 2

Participants: 2

Read full topic

@boomer196 wrote:

Is it by design that this happens? When you make a topic a banner it displays at the top of all pages, which is correct. However, when you view that banner topic it causes the entire background around post of the page to be blue.

Posts: 1

Participants: 1

Read full topic

@rowanjamesmiller wrote:

Literally updated a few settings in the admin setting of the site, and all of these T's started to appear.

I would upload the image but as a new user i'm not allowed to...

So for example it says

all categories (t6) Categories (t8) Latest (t10) New (17) (t12)

Has anyone else had this and no what the cause is/what i should do about it.

Cheers

Posts: 4

Participants: 2

Read full topic

@watchmanmonitor wrote:

Continuing the discussion from How do I update my Docker image to latest?:

We got a notice on one of our servers that disk space was low.

The download_remote_images_to_local setting was disabled because the disk space limit at `download_remote_images_threshold was reached.

When following Sam's commands, we ended up with 95% of our space used on our boot drive.

Following Sam's recommendations here, I was told that docker had tried to delete items which were still marked as in-use. Is this normal or OK? Maybe it's a Docker issue?

# docker rm `docker ps -aq`
Error response from daemon: Conflict, You cannot remove a running container. Stop the container before attempting removal or use -f
FATA[0000] Error: failed to remove one or more containers
root@discuss:/var/discourse# docker rmi `docker images -aq`
Error response from daemon: Conflict, cannot delete 91f6dfa70a1a because the running container aa1d4d35c8be is using it, stop it and use -f to force
Error response from daemon: Conflict, cannot delete 1e6d9a1f7326 because the running container aa1d4d35c8be is using it, stop it and use -f to force
Error response from daemon: Conflict, cannot delete 2a29f41bee3a because the running container aa1d4d35c8be is using it, stop it and use -f to force
Error response from daemon: Conflict, cannot delete 8ef4bef407a1 because the running container aa1d4d35c8be is using it, stop it and use -f to force
Error response from daemon: Conflict, cannot delete bc6884534416 because the running container aa1d4d35c8be is using it, stop it and use -f to force
Error response from daemon: Conflict, cannot delete ac3bba3cdcf5 because the running container aa1d4d35c8be is using it, stop it and use -f to force
Deleted: d5cdf7304e3a36b7443ce96a239d249953323b507fb7f0b84d90fe0f31c69170
Deleted: 4b87ea2e8f289b63e722fbe58b75ade579694c3828154c7a77dad9c4b2fe1a47

Posts: 2

Participants: 2

Read full topic

@Pirat wrote:

I think it would be cool if it could be to add a picture
instead of text
/admin/customize/user_fields

2424.jpg739x269 131 KB

gdsg.jpg739x269 138 KB

how you like the idea?

Posts: 2

Participants: 2

Read full topic

@Pirat wrote:

proposal
I propose to make playback of MP3 files on the site

Posts: 5

Participants: 3

Read full topic

@evannak wrote:

i'm not sure if any of you notice this.

image.jpg750x1334 99.8 KB

Posts: 5

Participants: 4

Read full topic

@NomNuggetNom wrote:

User title is too far down

The main problem here is trying to cram three lines of text in a 45px height, but it seems the user title is abnormally low. Removing the padding-top: 2px from the .user-title mobile CSS helps:

But it still looks a little weird.

---

Dropdowns overlay the header

Normally this is no problem:

As you can see, the drop down just barely rests above the banner. It's a nice look. Problems arise when the dropdown is not fixed to the top, like on the users page:

When you scroll down, the dropdown stays in place, totally overlapping the header.

Posts: 4

Participants: 3

Read full topic

@NomNuggetNom wrote:

I noticed people with grayed out names here on meta:

And I had no idea what it meant. I thought maybe it wasn't their full name, or something. I actually had to look into the CSS to realize it symbolized they were new users. There's no indication of that anywhere, except on the profile where their trust level shows as "new user."

I'm not sure what the best solution is to this, but I was definitely confused by the name color, so I think something needs to be changed.

Posts: 22

Participants: 9

Read full topic

@doudou wrote:

WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.

But I have set somaxconn to 2048, when I rebuild discourse, it still shows errors.

Posts: 3

Participants: 3

Read full topic

@watchmanmonitor wrote:

As a user, I can change my email preference, not see a Save button (despite them being at the top & bottom of the page) and navigate away from the Preferences page with no warning that my preferences weren't saved.

Not sure if they should auto-save, or have the same green/red boxes we have on the admin/settings.. or just warn them that settings weren't saved...

Posts: 3

Participants: 2

Read full topic

@watchmanmonitor wrote:

Continuing the discussion from Should 'Categories' link be always visible?:

I wonder .. is it possible to have /c link to categories?

IE https://meta.discourse.org/c or https://meta.discourse.org/c/

Linking to https://meta.discourse.org/categories ?

Posts: 2

Participants: 2

Read full topic

@badevguru wrote:

I propose adding the rss capability to the group feeds. So https://meta.discourse.org/groups/trust_level_0.rss would give you the rss feed for all trust_level_0 users for example.

Use Case #1: We have slack notifications that are pulling the rss feed for new topics. I would rather have a feed of all posts, not just new topics. Looks like the groups already does this. So to get a feed of all activity I should be able to do: https://meta.discourse.org/groups/everyone.rss

Note: The one catch to Use Case #1, is that the everyone group, unlike the other automatic groups, does not appear to offer a group feed.

Posts: 4

Participants: 3

Read full topic

@patcon wrote:

On our forum, we're trying to create a visible way for users to identify their skills and experience, without using plugins if possible. I was wondering whether someone could tell me whether this possible, before I get full admin access or set up my own instance to check:

I was hoping to replace the badges in this screencap with self-selected skills badges:
imgur.com/aaeG9vv

Was thinking we could disable standard badges, and use custom SQL queries like so:

We create a custom forum for "Skills badges" and allow anyone to create new posts titled as the skill. Anyone who "likes" the post gets a badge with the post title.

So I suppose the main question is whether the badge name can be dynamic. I suspect this is where the plan would be kiboshed. Would also be nice if badges could be removed by "unliking" the same post, but this might also be impossible without more work than I'm interested in investing

Anyhow, I appreciate any quick advice. Otherwise, I'll just have to dig in myself

Posts: 9

Participants: 5

Read full topic

@dandv wrote:

Continuing the discussion from Topic Summaries: when the conversation is over:

Here's an example of a thread with 17 posts that has a definitive answer as indicated by the community (4 likes). Ignoring for a moment my bias as being the poster of that post - how can this topic be effectively (auto)summarized as "Yep, that's the answer"?

I'm not a mod on that forum.

Posts: 3

Participants: 3

Read full topic

@dandv wrote:

What do the grey and blue circled counts mean? Presumably "unread" and "total" number of posts in that topic?

Tooltips would help. Thanks.

Posts: 4

Participants: 4

Read full topic