@Nuck wrote:

Would it be possible to sync a ban/suspension via SSO? If this is too broad for SSO (which, tbh, it probably is) is there a different API that would make it fairly simple?

For Hummingbird.me, we often get people we have to suspend (and occasionally hellban) to protect our other users, but we have to currently do two separate bans: one for our own server and one for Discourse, which frequently results in desynchronized bans... And the occasional "oh shit I'm sorry dude I thought we unbanned you months ago!", which is about as awkward as it gets.

Anyways, I'm in the process of switching us to SSO from our current hand-rolled (yuck!) system, and I noticed that there's already support for admin and moderator syncing (huzzah!) and custom fields (awesome!) and avatars (yay!) but it doesn't look like there's any way to synchronize the bans from our service onto Discourse.

So I guess my questions are:

1. Is this possible in SSO or via the API?
2. Assuming the answer is is "no", how hard would it be to add? Where should I look to start?

Posts: 3

Participants: 2

Read full topic

@Ankhamax wrote:

How do top users get ranked here?

Posts: 3

Participants: 2

Read full topic

@Anthony_Hopkins wrote:

When I try to upload image (composer form, User Avatar etc.) the Uploading... never ends.

I tested everything:
1. Heroku -> S3 connection correct (file uploaded):

Zaznaczenie_278.png1152x562 140 KB

2. Heroku response Success (HTTP Status 200)
3. It looks like some JS error but No JS errors
4. The same configuration works properly on my local Ubuntu.

Any idea? Thanks for response

Posts: 4

Participants: 2

Read full topic

@stylesm wrote:

I have reply-by-email setup and working on my Discourse installation.

I seem unable to get starting new topics by email working though.

A few things to note:

• The Categories have email addresses for starting topics by email set (e.g. staffnewtopic@example.com)
• The emails successfully alias to the same mailbox as reply-by-email messages
• I can pop3 to the mail server and open the mailbox from the host Discourse is on
• If I open the mailbox, the incoming new topic emails are there
• The sender email addresses are members of the groups with rights to the categories
• I've tried increasing and decreasing the pop3 polling frequency
• Have also tried allowing anonymous users to mail in new topics

In the logs, I get this:

Net::OpenTimeout (execution expired)
/usr/local/lib/ruby/2.0.0/net/pop.rb:544:in 'initialize'
/usr/local/lib/ruby/2.0.0/net/pop.rb:544:in 'open'
/usr/local/lib/ruby/2.0.0/net/pop.rb:544:in 'block in do_start'
/usr/local/lib/ruby/2.0.0/net/pop.rb:543:in 'do_start'
/usr/local/lib/ruby/2.0.0/net/pop.rb:530:in 'start'
/usr/local/lib/ruby/2.0.0/net/pop.rb:316:in 'auth_only'
/var/www/discourse/lib/validators/pop3_polling_enabled_setting_validator.rb:37:in 'authentication_works?'
/var/www/discourse/lib/validators/pop3_polling_enabled_setting_validator.rb:26:in 'error_message'
/var/www/discourse/app/models/admin_dashboard_data.rb:210:in 'pop3_polling_configuration'
/var/www/discourse/app/models/admin_dashboard_data.rb:45:in 'block in problems'
/var/www/discourse/app/models/admin_dashboard_data.rb:44:in 'each'
/var/www/discourse/app/models/admin_dashboard_data.rb:44:in 'problems'
/var/www/discourse/app/models/admin_dashboard_data.rb:83:in 'fetch_problems'
/var/www/discourse/app/controllers/admin/dashboard_controller.rb:12:in 'problems'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_controller/metal/implicit_render.rb:4:in 'send_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/abstract_controller/base.rb:198:in 'process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_controller/metal/rendering.rb:10:in 'process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/abstract_controller/callbacks.rb:20:in 'block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/callbacks.rb:117:in 'call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/callbacks.rb:117:in 'call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/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.5.2/lib/active_support/callbacks.rb:505:in 'call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/callbacks.rb:505:in 'call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/callbacks.rb:92:in '__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/callbacks.rb:778:in '_run_process_action_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/callbacks.rb:81:in 'run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/abstract_controller/callbacks.rb:19:in 'process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_controller/metal/rescue.rb:29:in 'process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/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.5.2/lib/active_support/notifications.rb:164:in 'block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/notifications/instrumenter.rb:20:in 'instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/notifications.rb:164:in 'instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_controller/metal/instrumentation.rb:30:in 'process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_controller/metal/params_wrapper.rb:250:in 'process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.2/lib/active_record/railties/controller_runtime.rb:18:in 'process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/abstract_controller/base.rb:137:in 'process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.2.5.2/lib/action_view/rendering.rb:30:in 'process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.9.2/lib/mini_profiler/profiling_methods.rb:76:in 'block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_controller/metal.rb:196:in 'dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_controller/metal/rack_delegation.rb:13:in 'dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_controller/metal.rb:237:in 'block in action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/routing/route_set.rb:74:in 'call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/routing/route_set.rb:74:in 'dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/routing/route_set.rb:43:in 'serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/routing/mapper.rb:49:in 'serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/journey/router.rb:43:in 'block in serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/journey/router.rb:30:in 'each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/journey/router.rb:30:in 'serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/routing/route_set.rb:815: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:25: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.5.2/lib/action_dispatch/middleware/params_parser.rb:27:in 'call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/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.5.2/lib/action_dispatch/middleware/cookies.rb:560:in 'call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.2/lib/active_record/query_cache.rb:36:in 'call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.2/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.5.2/lib/action_dispatch/middleware/callbacks.rb:29:in 'block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/callbacks.rb:88:in '__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/callbacks.rb:778:in '_run_call_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/callbacks.rb:81:in 'run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/middleware/callbacks.rb:27:in 'call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/middleware/remote_ip.rb:78:in 'call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/middleware/debug_exceptions.rb:17:in 'call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/middleware/show_exceptions.rb:30:in 'call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-1.1.1/lib/logster/middleware/reporter.rb:31:in 'call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.5.2/lib/rails/rack/logger.rb:38:in 'call_app'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.5.2/lib/rails/rack/logger.rb:22:in 'call'
/var/www/discourse/config/initializers/100-quiet_logger.rb:10: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.5.2/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.9.9.2/lib/mini_profiler/profiler.rb:167:in 'call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-2.0.0.beta.5/lib/message_bus/rack/middleware.rb:60: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.5.2/lib/rails/engine.rb:518:in 'call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.5.2/lib/rails/application.rb:165:in 'call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.5.2/lib/rails/railtie.rb:194:in 'public_send'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.5.2/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.0.1/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.0.1/lib/unicorn/http_server.rb:658:in 'worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/lib/unicorn/http_server.rb:508:in 'spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/lib/unicorn/http_server.rb:519:in 'maintain_worker_count'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/lib/unicorn/http_server.rb:283:in 'join'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/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>'

Then each time it polls:

Job exception: execution expired
/usr/local/lib/ruby/2.0.0/net/pop.rb:544:in `initialize'
/usr/local/lib/ruby/2.0.0/net/pop.rb:544:in `open'
/usr/local/lib/ruby/2.0.0/net/pop.rb:544:in `block in do_start'
/usr/local/lib/ruby/2.0.0/net/pop.rb:543:in `do_start'
/usr/local/lib/ruby/2.0.0/net/pop.rb:530:in `start'
/var/www/discourse/app/jobs/scheduled/poll_mailbox.rb:92:in `poll_pop3'
/var/www/discourse/app/jobs/scheduled/poll_mailbox.rb:15:in `execute'
/var/www/discourse/app/jobs/base.rb:154:in `block (2 levels) in perform'

Strangely, in /admin/email/received, there are no records, not even of reply posts, which work absolutely fine.

/var/log/mail.err is empty, /var/log/mail.log doesn't show any issues or timeouts.

A bit stumped now! Any thoughts?

Posts: 4

Participants: 2

Read full topic

@downey wrote:

Something about this scenario doesn't seem right. First of all, I don't know how I could possibly reply too fast by email, but so it doesn't even seem like a reasonable thing to block given the latency of email. And how could I reply in any faster than 5 seconds?

Screenshot_20160325-101921.png1440x2560 191 KB

Posts: 5

Participants: 2

Read full topic

@mcwumbly wrote:

I think a combination of things would help users who rarely visit the site, but want to interact via email, in a way that much more closely matches the model Discourse has for on-site usage.

Here's the rough idea for Mailing List 2.0 mode:

• All new topics are sent by email, but not posts
  • If a topic is replied to, then it is watched
    (This way, users can continue to interact with that topic via email-only).
  • A button allows the user to watch the post in a single-click too, without signing into the site.
• A periodic digest of all new posts are sent out
  • Daily is the default frequency, but can be adjusted
  • The digest first lists the topics that have had replies, in a format similar to the /latest page
    • Each row has a link to watch the topic
  • Below the topic-list all posts are shown, grouped by topic
  • Each post in the digest has a reply-by-email link to reply to that post
    • Replying to a topic in this fashion also automatically sets it to watched of course.

This "mailing list 2.0" mode is what I think we should be striving for as a default for these email-only users.

Related topics:

• Get notified of new topics, but not posts
• More granular mailing list mode
• Daily limits for outgoing mail per user
• Add a preference to auto-watch topics I replied in
• Automatically set topics to watching after posting

Posts: 3

Participants: 2

Read full topic

@Ankhamax wrote:

The maximum characters for the topic appears to be set at 16,000 characters. Is there any way that we can increase it 80,000 characters?

Posts: 2

Participants: 2

Read full topic

@Grex315 wrote:

I have had backups setup to run daily on my site for quite awhile but recently I have noticed that have not been running. No new backup files are being created. I looked into the log to see if there was anything there. No errors to speak of.

I then checked sidekiq and looked at the job there. In sidekiq the job is running with a status of success but it looks like it is running way to quick for a backup job.

Sidekiq 2016-03-25 13-10-26.png1903x986 160 KB

What else can i do to troubleshoot this?

EDIT: to add kicking off a manual backup works correctly and a backup file is created.

Thanks

Posts: 1

Participants: 1

Read full topic

@pieterhoogenboom wrote:

I can POST to /users and add a new user succesfully:

$fields = array(
'name' => urlencode($name),
'email' => urlencode($email),
'username' => urlencode($username),
'password' => urlencode($password),
'active' => true,
'api_username' => urlencode($config['api']['username']),
'api_key' => urlencode($config['api']['key']),
);

But then the user gets:

"You can't log in yet. We previously sent an activation email to you at..."

Is it possible to add an extra flag to the /users POST call like "email_confirmed"?

P.S. There's been multiple threads about this without an internal solution:

Posts: 3

Participants: 3

Read full topic

@ljpp wrote:

The next Ubuntu LTS is due in about one month, and service providers are likely to add it to their offering sooner than later. As 14.04 is already 2 years into it's life-cycle, the 16.04 is likely to become the recommended default very quickly.

Is Discourse compatible with the 16.04 as of today or from day 1 after the release? Anyone tried it yet? I will be making some server migrations during spring time, so it would make sense to jump in the 16.04 bandwagon while I am at it.

Posts: 3

Participants: 3

Read full topic

@Carson wrote:

Recently in our community we have been mass locking old topics. I'm aware that when I lock a topic it doesn't come up in latest, but it does come up in Suggested and Unread with the blue bubble.

image.jpeg1242x2208 230 KB

Posts: 4

Participants: 3

Read full topic

@Carson wrote:

I have noticed that the system automatically blocks some new users. These appear to be normal users who don't have the same IP as anyone else and in most cases haven't posted a single thing. Why are these users blocked?

Posts: 10

Participants: 3

Read full topic

@carninglipartners wrote:

Last year I installed a Discourse instance set up on a Digital Ocean droplet. It has worked fine, but now I want to make a series of related posts on a certain topic over a period of several months and make them read only.

I would like discussion of these posts to take place in a separate topic so that the original 'diary-like' posts are kept apart.

Is this possible or indeed desirable?

Thanks
Dan

Posts: 2

Participants: 2

Read full topic

@tobiaseigen wrote:

Just updated to latest, drawn by this tweet:

I very much the new badge page design - nice job! Much appreciated improvement and a welcome way to start the weekend.

However, now I no longer see descriptions for custom badges on the badge pages on my site, which provided much needed explanation of what the badges represent. The descriptions do show up for the default badges but not for my custom badges.

Screen Shot 2016-03-25 at 7.56.33 PM.png2560x1600 564 KB

Posts: 3

Participants: 2

Read full topic

@meglio wrote:

For the content that cannot be one-boxed in Discourse, a universal fallback to embed.ly might be better than nothing. Look like a plugin area.

Posts: 2

Participants: 2

Read full topic

@mbillow wrote:

I have had several people come to me very confused why their post was attributed to another user. This is because the avatar of the latest poster is used in the mobile view and nothing else (not even an author name). The author of the post is always the left most user on the desktop theme for a reason; not carrying over this important distinction is highly confusing.

Posts: 8

Participants: 4

Read full topic

@gingerman wrote:

In continuation with the above discussion, there is a clear need for a solution to achieve 2 things for a community.

1. Prevent private communication channel in a community to encourage public discussion. All the schools, healthcare communities need this requirement.
2. Provide a simple support channel to reach the admin / moderators for help from the web app (I am not talking about emails)

For requirement number 1, we can easily disable the private messaging completely. As a side effect, this stops us to achieve requirement 2.

Categories in discourse are clearly secured with groups and permissions.

The most clean and secure way to support the requirement number 2 is by providing a category of type "Create & See only my topics/posts". (The UI for topics list in a category view is much more intuitive than a personal messages inbox as well.)

I would like to understand why this feature is not encouraged in discourse (based on all old discussion threads I could dig through, I didn't see any clear reason). Can you please provide your insights. @sam @codinghorror

Posts: 11

Participants: 3

Read full topic

@mcwumbly wrote:

I have a user whose account was originally created as a staged account via an import from another system.

Recently, they logged in and created a new topic.

But they still show up as a staged user, and I cannot @mention them.

I do not see any way in the Admin UI to force them to become "unstaged".

Potentially relevant site settings:

1. Google Login enabled
2. Local logins disabled
3. Email whitelist domains (1)

Currently running version v1.5.0.beta13b +38 (67a5fc39ded9f661974b6e06b109c75b50d3a1b1)

Posts: 5

Participants: 2

Read full topic

@steko wrote:

I've finally setup reply by email for my Discourse forum, but unfortunately parsing of replies seems suboptimal and the original message is not stripped. My forum is in Italian, but that should be accounted for, at least judging by some earlier bug reports about this same issue. I've seen a few other topics here on Meta (and there are probably older ones as well):

I don't use Gmail, that probably accounts for 50% of my users alone and should be covered, but I wonder if there's a more robust way to support quirks of other email clients (e.g. mobile email clients, since replying to email from mobile is one of the use cases that Discourse wants to support, I think). Of course I can just suggest users to strip entirely the original message or leave only short quotes if they like, but ... I'm sure Discourse can handle this better!

Posts: 5

Participants: 3

Read full topic

@ljpp wrote:

When using the Edge browser, in mobile view, the text editor falls behind the virtual keyboard.

1. Initial state

Starting to compose a new post. Everything looks ok here. Note that the cursor is positioned on the 2nd row of the editor.

wp_ss_20160326_0001.png1080x1920 68.9 KB

2. After hitting the 1st letter

The editor disappears under the virtual keyboard. You can scroll it back to the visible area though.

wp_ss_20160326_0002.png1080x1920 126 KB

Posts: 2

Participants: 2

Read full topic