@ljpp wrote:
Goofing around to find a color scheme for a new Discourse project. The seed color is #fe0000, but when I set it as the color for the header icons I get something pink-ish instead of the pure red (burger, search icon).
Why is that?
Posts: 3
Participants: 2
@Drew_Warwick wrote:
Posting in uncategorized because I'm not sure if this is feature-worthy or not -- this is a topic for discovering if it is.
When you're bringing another person's thoughts to a thread through an out-of-thread quote, it can also be useful to know what other people thought of those thoughts. You can jump to the thread the quote came from to see the #likes and types of replies, but not many people bother opening up and reading through a different thread. It could be handy if quotes from out-of-thread topics showed the number of likes the quoted post had. For instance, imagine a debate/opinionated discussion pops up somewhere about something that happens to have been discussed in another topic. If you quote something, that holds as much weight as a regular post unless it came from an authority figure, but if you quote something that had 50 likes, that holds a lot more weight and can prevent circular discussion of what had already been discussed and help advance the discussion to something constructive.
I don't see many use cases for it though, which is why I'm not sure if it's feature-worthy. It seems like a gimmick at this point, but maybe there are other uses for it.
Edit: to answer a question before it's asked, yes I could mention how many likes the post has when I quote it, but that may seem like an attack on the person I'm replying to. Sort of like "Hey, this post has more likes than yours so it's right and you're wrong", which is totally not the case nor what I want to get across. If it's just sort of there and not mentioned directly though, I think instead of getting defensive and making the situation worse, the people posting on the thread might do a double take and think about what they're posting since they're not being directly called out.
Posts: 3
Participants: 2
@V0rTeX wrote:
Hello. I'm wondering what's the best way to prevent local uploads in post mode? Has anyone managed to do it somehow? I don't like random images to be hosted on my server.
Posts: 2
Participants: 2
@Trash wrote:
From the last beta (5, 6 and 7) in all the italian discourse forums I've checked, we have a
[missing %{data} value]for every badge.I know that italian translators have checked on Transifex but it seems the problem is not related to translation.
Posts: 4
Participants: 2
@Yunus wrote:
I have tried to ask this question before but the only answers I have received are from seasoned Discourse staff or developers. Ideally I would like to hear from people who have set it up themselves and did not know anything before doing so.
Can anyone tell me how much work / time to be expected to set this up once installed - for someone like myself who would be learning it from scratch. I am a web designer with CSS and HTML skills. That's it. I would be setting this up for a client and need some realistic expectation so I know how to price the work offered to my client.
Thanks,
Posts: 14
Participants: 7
@Yuun wrote:
Issue:
Repro:
1. Go to the bottom of a topic such as this one
2. Begin scrolling up (possibly until more posts need to be loaded, not sure of scrolling extent required)
3. Click on the time indicator at the bottom of the timeline (e.g. "20m ago" in my screenshot) to go the bottom of the topic
4. PanicEnv:
Chrome, Windows 10
Posts: 4
Participants: 3
@mikehc wrote:
Hi I'm having troubles in my installation of Discourse (v1.6.0.beta8 +28) after upgrading it today.
When trying to edit some posts I receive an error: 422 Unprocessable Entity. I notice that if I modify the title and the content only the title gets updated. The error mentioned is always thrown. This behavior doesn't occur with all posts and new posts are not affected by this.
On the logs this shows up:
ActiveRecord::RecordInvalid (Validation failed: Url has already been taken) /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/validations.rb:79:in `raise_record_invalid' Stacktrace: /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/validations.rb:79:in `raise_record_invalid' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/validations.rb:43:in `save!' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/attribute_methods/dirty.rb:29:in `save!' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/transactions.rb:291:in `block in save!' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/transactions.rb:351:in `block in with_transaction_returning_status' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/database_statements.rb:211:in `transaction' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/transactions.rb:220:in `transaction' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/transactions.rb:348:in `with_transaction_returning_status' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/transactions.rb:291:in `save!' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/persistence.rb:51:in `create!' /var/www/discourse/app/models/topic_link.rb:168:in `block (2 levels) in extract_from' /var/www/discourse/app/models/topic_link.rb:116:in `each' /var/www/discourse/app/models/topic_link.rb:116:in `block in extract_from' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/database_statements.rb:211:in `transaction' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/transactions.rb:220:in `transaction' /var/www/discourse/app/models/topic_link.rb:106:in `extract_from' /var/www/discourse/lib/post_revisor.rb:162:in `revise!' /var/www/discourse/app/models/post.rb:408:in `revise' /var/www/discourse/app/models/post.rb:452:in `set_owner' /var/www/discourse/app/services/post_owner_changer.rb:22:in `block (2 levels) in change_owner!' /var/www/discourse/app/services/post_owner_changer.rb:14:in `each' /var/www/discourse/app/services/post_owner_changer.rb:14:in `block in change_owner!' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `block in transaction' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/transaction.rb:184:in `within_new_transaction' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `transaction' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/transactions.rb:220:in `transaction' /var/www/discourse/app/services/post_owner_changer.rb:13:in `change_owner!' /var/www/discourse/app/controllers/topics_controller.rb:443:in `change_post_owners' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/implicit_render.rb:4:in `send_action' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/abstract_controller/base.rb:198:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/rendering.rb:10:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/abstract_controller/callbacks.rb:20:in `block in process_action' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:117:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:117:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:505:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:505:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:92:in `__run_callbacks__' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:778:in `_run_process_action_callbacks' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:81:in `run_callbacks' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/abstract_controller/callbacks.rb:19:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/rescue.rb:29:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/notifications.rb:164:in `block in instrument' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/notifications/instrumenter.rb:20:in `instrument' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/notifications.rb:164:in `instrument' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/instrumentation.rb:30:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/params_wrapper.rb:250:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/railties/controller_runtime.rb:18:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/abstract_controller/base.rb:137:in `process' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.2.6/lib/action_view/rendering.rb:30:in `process' /var/www/discourse/vendor/bundle/ruby/2.0.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.0.0/gems/actionpack-4.2.6/lib/action_controller/metal.rb:196:in `dispatch' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal.rb:237:in `block in action' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb:74:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb:74:in `dispatch' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb:43:in `serve' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/journey/router.rb:43:in `block in serve' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/journey/router.rb:30:in `each' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/journey/router.rb:30:in `serve' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb:817: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.3.1/lib/omniauth/strategy.rb:186:in `call!' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/builder.rb:63:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/conditionalget.rb:38:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/head.rb:13:in `call' /var/www/discourse/lib/middleware/anonymous_cache.rb:129:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/params_parser.rb:27:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/flash.rb:260:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:225:in `context' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:220:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/cookies.rb:560:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/query_cache.rb:36:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:653:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:88:in `__run_callbacks__' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:778:in `_run_call_callbacks' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:81:in `run_callbacks' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/callbacks.rb:27:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/remote_ip.rb:78:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-1.2.3/lib/logster/middleware/reporter.rb:31:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.6/lib/rails/rack/logger.rb:38:in `call_app' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.6/lib/rails/rack/logger.rb:22:in `call' /var/www/discourse/config/initializers/100-quiet_logger.rb:13:in `call_with_quiet_assets' /var/www/discourse/config/initializers/100-silence_logger.rb:26:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/request_id.rb:21:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/methodoverride.rb:22:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/runtime.rb:18:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/sendfile.rb:113:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.10.1/lib/mini_profiler/profiler.rb:278:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-2.0.0.beta.11/lib/message_bus/rack/middleware.rb:62:in `call' /var/www/discourse/lib/middleware/request_tracker.rb:73:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.6/lib/rails/engine.rb:518:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.6/lib/rails/application.rb:165:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.6/lib/rails/railtie.rb:194:in `public_send' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.6/lib/rails/railtie.rb:194:in `method_missing' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/urlmap.rb:66:in `block in call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `each' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.1.0/lib/unicorn/http_server.rb:562: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-5.1.0/lib/unicorn/http_server.rb:658:in `worker_loop' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.1.0/lib/unicorn/http_server.rb:508:in `spawn_missing_workers' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.1.0/lib/unicorn/http_server.rb:132:in `start' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.1.0/bin/unicorn:126:in `<top (required)>' /var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:22:in `load' /var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:22:in `<main>'Second exception
Job exception: Validation failed: Url has already been taken Stacktrace: /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/validations.rb:79:in `raise_record_invalid' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/validations.rb:43:in `save!' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/attribute_methods/dirty.rb:29:in `save!' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/transactions.rb:291:in `block in save!' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/transactions.rb:351:in `block in with_transaction_returning_status' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/database_statements.rb:211:in `transaction' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/transactions.rb:220:in `transaction' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/transactions.rb:348:in `with_transaction_returning_status' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/transactions.rb:291:in `save!' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/persistence.rb:51:in `create!' /var/www/discourse/app/models/topic_link.rb:168:in `block (2 levels) in extract_from' /var/www/discourse/app/models/topic_link.rb:116:in `each' /var/www/discourse/app/models/topic_link.rb:116:in `block in extract_from' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `block in transaction' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/transaction.rb:184:in `within_new_transaction' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `transaction' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/transactions.rb:220:in `transaction' /var/www/discourse/app/models/topic_link.rb:106:in `extract_from' /var/www/discourse/lib/cooked_post_processor.rb:41:in `extract_links' /var/www/discourse/lib/cooked_post_processor.rb:35:in `block in post_process' /var/www/discourse/lib/distributed_mutex.rb:21:in `synchronize' /var/www/discourse/lib/distributed_mutex.rb:5:in `synchronize' /var/www/discourse/lib/cooked_post_processor.rb:28:in `post_process' /var/www/discourse/app/jobs/regular/process_post.rb:24:in `execute' /var/www/discourse/app/jobs/base.rb:154:in `block (2 levels) in perform'When I try to change ownership of a post both errors are thrown as well. This is more consistent and happens with all post.
Let me know if you need more information.
Posts: 8
Participants: 4
@ron_jeremy wrote:
Tonight was the first time I've ever checked the logs. Should I be worried about this? My forum is "stock" (no plugins or custom anything).
Posts: 2
Participants: 2
@HAWK wrote:
Is anyone using geo-targeted banners on their Discourse instance? Is it possible?
Posts: 1
Participants: 1
@Steve_Ng wrote:
Hi,
I've discourse hosted at
http://a.comI am hosting the same discourse instance at
http://b.comwould there be some config to make SSO works? Such that when a user clicks login from b.com, it will be redirected back to b.com?
Posts: 1
Participants: 1
@grxninesix wrote:
Hi guys, i am back here after 2 weeks.
Its normal that the profile name's are in bold and first then it show the username in normal font?
Posts: 3
Participants: 3
@precessor wrote:
Is it possible to force users to fill out a custom user profile field?
I.e. prevent further site interaction until some text is entered in that field.
Posts: 5
Participants: 3
@precessor wrote:
It is possible to have a limited list of allowed tags on topics?
I can't find a way.Use case: I would like to label some posts as tutorial-style "how to" posts under each of my Categories, instead of taking these useful posts our of the categories where they really belong to a separate "how to" category (which is what I currently do). So currently my whitelist would be one tag: "howto".
Posts: 4
Participants: 3
@alphaman wrote:
I am using discourse and still the email is not working
My discourse address is discourse.smartclashcoc.com
My SMPT credentials are as follows
hostname : srv67.hostinger,com username : no-reply@smartclashcoc.com pass : not mentioned Incoming Server : smartclashcoc.com IMAP Port: 993 POP3 Port: 995 Outgoing Server : smartclashcoc.com SMTP Port: 465Now the email I want the discourse to use is no-reply.smartclashcoc.com but i think there is nothing to set somthing like that. Can you help me with this?
And if possible, can you make an example config.yml file with my credential as i am a newbie?
Posts: 1
Participants: 1
@casperovergaard wrote:
My team and I are currently working on implementing a custom styled discourse solution at http://beta.danskdynamit.com/. To that extend, it would be really useful to have descriptive/route classes on the body tag (also, as described here https://meta.discourse.org/t/descriptive-classes-in-body/34188). It would be awesome in terms of per page/state specific styling. Is it something thats possible?
E.g. front page
<body class="route-index">E.g. user
<body class="route-user">E.g. topic
<body class="route-topic">
Posts: 6
Participants: 6
@Alexander_Wright wrote:
I've just encountered a bug with the "About Category Posts":
- Create a new Category
- Delete the About Post.
- Set the category view only for everyone.
- Click the edit Edit Description button in the category settings
- Save topic
- Note that the topic is now in the uncategorised category.
- Make the category in 1 writable.
- Click on the button in (4) again. Note that you can't change it's category.
I had to change the category of the topic in the database to get it to appear in the correct place! I hope I didn't break anythings else.
Posts: 3
Participants: 2
@P16 wrote:
Read this on HN today. Posting in case someone needs a slackbot:
https://medium.dgraph.io/wisemonk-a-slackbot-to-move-discussions-from-slack-to-discourse-22a53ddce78f#.m4bonyds3Their repo is at:
https://github.com/dgraph-io/wisemonk
Posts: 1
Participants: 1
@kyler wrote:
I'd like to remove the pinned About topic for categories, and just can't figure out how to do it. I just want my categories to start with the posts, not an about posts.
Thanks!
Posts: 6
Participants: 4
@haiduong wrote:
Hello everyone,
I'm having a problem with my Discourse instance after upgrading it via the UI. It was running fine back then. The upgrade was successful, however, reloading the page has resulted in a blank page since then. I found a relevant thread at https://meta.discourse.org/t/blank-page-after-upgrading-due-to-old-tagging-plugin/45243 and tried to rebuild the app, however, things still haven't recovered.
Here is the log of the launcher after I rebuilt the app:
run-parts: executing /etc/runit/1.d/00-ensure-links run-parts: executing /etc/runit/1.d/anacron run-parts: executing /etc/runit/1.d/cleanup-pids Cleaning stale PID files run-parts: executing /etc/runit/1.d/copy-env run-parts: executing /etc/runit/1.d/enable-brotli run-parts: executing /etc/runit/1.d/ensure-web-nginx-read Started runsvdir, PID is 31 sh: echo: I/O error ok: run: redis: (pid 41) 0s ok: run: postgres: (pid 40) 0s _._ _.-``__ ''-._ _.-`` `. `_. ''-._ Redis 3.0.6 (00000000/0) 64 bit .-`` .-```. ```\/ _.,_ ''-._ ( ' , .-` | `, ) Running in standalone mode |`-._`-...-` __...-.``-._|'` _.-'| Port: 6379 | `-._ `._ / _.-' | PID: 41 `-._ `-._ `-./ _.-' _.-' |`-._`-._ `-.__.-' _.-'_.-'| | `-._`-._ _.-'_.-' | http://redis.io `-._ `-._`-.__.-'_.-' _.-' |`-._`-._ `-.__.-' _.-'_.-'| | `-._`-._ _.-'_.-' | `-._ `-._`-.__.-'_.-' _.-' `-._ `-.__.-' _.-' `-._ _.-' `-.__.-' 41:M 15 Jun 22:02:09.879 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128. 41:M 15 Jun 22:02:09.879 # Server started, Redis version 3.0.6 41:M 15 Jun 22:02:09.880 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. 41:M 15 Jun 22:02:09.880 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled. 41:M 15 Jun 22:02:09.890 * DB loaded from disk: 0.010 seconds 41:M 15 Jun 22:02:09.890 * The server is now ready to accept connections on port 6379 rsyslogd: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ] rsyslogd: imklog: cannot open kernel log (/proc/kmsg): Operation not permitted. rsyslogd: activation of module imklog failed [v8.16.0 try http://www.rsyslog.com/e/2145 ] rsyslogd: Could not open output pipe '/dev/xconsole':: No such file or directory [v8.16.0 try http://www.rsyslog.com/e/2039 ] Server listening on 0.0.0.0 port 22. Server listening on :: port 22. 2016-06-15 22:02:10 UTC [60-1] LOG: database system was shut down at 2016-06-15 22:01:09 UTC 2016-06-15 22:02:10 UTC [60-2] LOG: MultiXact member wraparound protections are now enabled 2016-06-15 22:02:10 UTC [40-1] LOG: database system is ready to accept connections 2016-06-15 22:02:10 UTC [64-1] LOG: autovacuum launcher started supervisor pid: 42 unicorn pid: 66I did see the following error in production.log:
Error connecting to Redis on localhost:6379 (Errno::ECONNREFUSED) subscribe failed, reconnecting in 1 second. Call stack ["/var/www/discourse/vendor/bundle/ru by/2.3.0/gems/redis-3.3.0/lib/redis/client.rb:345:in `rescue in establish_connection'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redi s/client.rb:331:in `establish_connection'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis/client.rb:101:in `block in connect'", "/va r/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis/client.rb:293:in `with_reconnect'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redi s-3.3.0/lib/redis/client.rb:100:in `connect'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis/client.rb:364:in `ensure_connected'", " /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis/client.rb:221:in `block in process'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems /redis-3.3.0/lib/redis/client.rb:306:in `logging'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis/client.rb:220:in `process'", "/var /www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis/client.rb:134:in `block in call_loop'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/r edis-3.3.0/lib/redis/client.rb:280:in `with_socket_timeout'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis/client.rb:133:in `call_loop'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis/subscribe.rb:43:in `subscription'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis/subscribe.rb:12:in `subscribe'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis.rb:2760:in `_subscription'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis.rb:2138:in `block in subscribe'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/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.0/lib/redis.rb:58:in `synchronize'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis.rb:2137:in `subscribe'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.0.beta.11/lib/message_bus/backends/redis.rb:304:in `global_subscribe'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.0.beta.11/lib/message_bus.rb:504:in `global_subscribe_thread'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.0.beta.11/lib/message_bus.rb:456:in `block in new_subscriber_thread'"]Could you guys advise me on a way to debug and resolve the problem in this case? Thanks!
Posts: 7
Participants: 2
@debynory wrote:
Hi all,
I would like to know if it's possible add a dropdown on the registration page to allow to user to choose his group.
For example: You are a: "seller" / "buyer"
Thank you in advance
Posts: 1
Participants: 1
