@sedget wrote:

Hi, i had setup an discourse instane, it was working fine. i had configured oauth2 with google and it was working.

yesterday i'm trying a new fresh install at the same adress. I'm using the same parameters but now i got error 500.

my discourse version is Discourse latest-release +41 1.5.0.beta9

is tehre someone can help me ?

texte préformaté indenté par 4 espaces

 /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/jwt-1.5.2/lib/jwt.rb:170:indecode'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bundler/gems/omniauth-google-oauth2-b492c4bb8286/lib/omniauth/strategies/google_oauth2.rb:61:in block in <class:GoogleOauth2>'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:105:ininstance_eval'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:105:in block in compile_stack'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:104:ineach'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:104:in inject'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:104:incompile_stack'
(eval):7:in extra_stack'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:329:inextra'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:336:in auth_hash'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:361:incallback_phase'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-oauth2-1.3.1/lib/omniauth/strategies/oauth2.rb:79:in callback_phase'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:227:incallback_call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:184:in call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:incall'
/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:incall'
/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:incall'
/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:127:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.1/lib/action_dispatch/middleware/params_parser.rb:27:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.1/lib/action_dispatch/middleware/flash.rb:260:incall'
/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:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.1/lib/action_dispatch/middleware/cookies.rb:560:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/query_cache.rb:36:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/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.1/lib/action_dispatch/middleware/callbacks.rb:29:inblock in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:88:in __run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:778:inruncall_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:81:in run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.1/lib/action_dispatch/middleware/callbacks.rb:27:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.1/lib/action_dispatch/middleware/remote_ip.rb:78:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.1/lib/action_dispatch/middleware/debug_exceptions.rb:17:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.1/lib/action_dispatch/middleware/show_exceptions.rb:30:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-1.0.1/lib/logster/middleware/reporter.rb:31:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.5.1/lib/rails/rack/logger.rb:38:in call_app'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.5.1/lib/rails/rack/logger.rb:22:incall'
/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:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.1/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:incall'
/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:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.8/lib/mini_profiler/profiler.rb:170:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-2.0.0.beta.2/lib/message_bus/rack/middleware.rb:60:incall'
/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.1/lib/rails/engine.rb:518:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.5.1/lib/rails/application.rb:165:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.5.1/lib/rails/railtie.rb:194:inpublic_send'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.5.1/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:inblock 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:incall'
/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:inprocess_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:inworker_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:132:instart'
/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:23:inload'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in <main>'

Posts: 1

Participants: 1

Read full topic

@stevenpslade wrote:

Hello Discoursers,

What are your thoughts on a plugin that could completely redesign the Discourse homepage, turning questions into cards, like so:

Also, what are the chances that liking a question could also have functionality on this page? It could be hard, but is it possible?

This overhaul would need some big template changes, pulling in different parts of the question, and some big CSS changes. If it's possible, I'm going to try!

Posts: 6

Participants: 4

Read full topic

@clay wrote:

I'm using Discourse internally at a large organization that has people working in many different offices on vastly different types of research projects. We're getting complaints that users are unable to really "parse" the default landing page and would prefer to have an easier way to get to the categories specific to their research areas.

What I propose is this:

• allow users to "favorite" or "star" or "bookmark" categories of interest.
• when they visit the categories or bookmarks page, those categories appear at the top of the list.

This would just give users a simple way to isolate categories of most interest.

I'd love to see an alternate landing/latest page that only showed posts from the favorite categories, but IIRC, that's been debated here previously and shot down.

Posts: 6

Participants: 5

Read full topic

@finalcloud wrote:

On digitalocean, ubuntu 14.04.3 LTS
Fresh docker install according to the 30-min guide.
Logged in as admin, posted a link to a tweet and it shows as this:

tweet.PNG703x233 9.04 KB

I wiped my test installation and tried from scratch, no difference...

The hyperlink in the tweet is not clickable. Here on Meta it works.

Does anyone have an idea what it might be?

Thanks!

Posts: 5

Participants: 3

Read full topic

@John_Fleming wrote:

I'm having some trouble understanding the outgoing email options. Basically, I don't want any outgoing emails to be sent that contain post content (i.e. if someone has replied to a topic) and probably I'd rather nobody get email when they receive a PM either (although that would be acceptable).

I found the setting to disable ALL outgoing email and it seems to work quite well, but I need emails related to signing up and signing in to work (reset password link, etc.)

Can I turn off all email notifications, and keep signup/signin emails functional?

Thanks,
John

Posts: 2

Participants: 2

Read full topic

@LanieI wrote:

Hi!

Is there a way I could add this, http://timekit.io, to my "Create a new Topic" text box. I'm trying to find a plugin to add a customizable calendar to the "Create a new Topic" text box, and was wondering other peoples opinion on using Time Kit & if it would be possible to it add to Discourse? Also, do WP plugins work on Discourse?

Thanks a lot!
Lanie

Posts: 1

Participants: 1

Read full topic

@carlokok wrote:

Looks like a missing translation in "Email Reject Destination" :
(latest from earlier today)

translation missing: en.system_messages.email_reject_destination.subject_template

Same for email reject post error and email reject post error specified (and a few others)

translation missing: en.system_messages.email_reject_post_error.subject_template

Posts: 1

Participants: 1

Read full topic

@Yuun wrote:

So, I've grouped these because they seem to be related, but if I need to split this up let me know, I won't be offended.

I am on latest as of now (i.e. post @zogstrip's commit from here: https://meta.discourse.org/t/duplicate-meta-digest-emails-this-morning/38633/7), using Mandrill with generally no problems, and am seeing the following issues:

email_log.png276x696 13.7 KB

As shown in the first 10 entries above, duplication of logs. This in in admin/email/sent. I'm trying to verify right now whether or not duplicate emails are being sent out as well (found while writing this: it looks like it's just a duplicate log, not actually a duplicate email). The duplicate entry has a blank user field. Duplicate log entries don't appear in admin/email/skipped, but sporadic blank user fields do.

The blank entries below those ten are all digest emails, all missing a user but with appropriate email addresses.

Prior to zogstrip's commit referenced above, all of the email logs were showing up with blank user fields. This started happening after I received this error in /logs late Wednesday (with 4 corresponding failed email jobs in sidekiq):

Message (4 copies reported)

Job exception: SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read finished A
Backtrace

/usr/local/lib/ruby/2.0.0/net/smtp.rb:586:in `connect'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:586:in `tlsconnect'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:563:in `do_start'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:520:in `start'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/mail-2.6.3/lib/mail/network/delivery_methods/smtp.rb:112:in `deliver!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/mail-2.6.3/lib/mail/message.rb:2141:in `do_delivery'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/mail-2.6.3/lib/mail/message.rb:236:in `block in deliver'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.2.5.1/lib/action_mailer/base.rb:543:in `block in deliver_mail'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/notifications.rb:164:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/notifications.rb:164:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.2.5.1/lib/action_mailer/base.rb:541:in `deliver_mail'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/mail-2.6.3/lib/mail/message.rb:236:in `deliver'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.2.5.1/lib/action_mailer/message_delivery.rb:85:in `deliver_now'
/var/www/discourse/lib/email/sender.rb:131:in `send'
/var/www/discourse/app/jobs/regular/user_email.rb:42:in `execute'
/var/www/discourse/app/jobs/base.rb:154:in `block (2 levels) in perform'
Env

hostname	sih.onemadogre.com-app
process_id	22034
application_version	8aea75edecc468d04918e13db6924b7da6b1107b
current_db	default
current_hostname	sih.onemadogre.com
job	Jobs::UserEmail
problem_db	default
opts
type	digest
user_id	[225, 114, 216, 105]
current_site_id	default

I also have this error sitting around, which caused again a Sidekiq UserEmail job to fail:

Message

Job exception: end of file reached
Backtrace

/usr/local/lib/ruby/2.0.0/net/protocol.rb:153:in `read_nonblock'
/usr/local/lib/ruby/2.0.0/net/protocol.rb:153:in `rbuf_fill'
/usr/local/lib/ruby/2.0.0/net/protocol.rb:134:in `readuntil'
/usr/local/lib/ruby/2.0.0/net/protocol.rb:144:in `readline'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:932:in `recv_response'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:918:in `block in getok'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:942:in `critical'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:916:in `getok'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:824:in `helo'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:604:in `do_helo'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:556:in `do_start'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:520:in `start'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/mail-2.6.3/lib/mail/network/delivery_methods/smtp.rb:112:in `deliver!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/mail-2.6.3/lib/mail/message.rb:2141:in `do_delivery'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/mail-2.6.3/lib/mail/message.rb:236:in `block in deliver'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.2.5.1/lib/action_mailer/base.rb:543:in `block in deliver_mail'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/notifications.rb:164:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/notifications.rb:164:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.2.5.1/lib/action_mailer/base.rb:541:in `deliver_mail'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/mail-2.6.3/lib/mail/message.rb:236:in `deliver'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.2.5.1/lib/action_mailer/message_delivery.rb:85:in `deliver_now'
/var/www/discourse/lib/email/sender.rb:131:in `send'
/var/www/discourse/app/jobs/regular/user_email.rb:69:in `execute'
/var/www/discourse/app/jobs/base.rb:154:in `block (2 levels) in perform'
Env

hostname	sih.onemadogre.com-app
process_id	4733
application_version	5b8817cc70377ffc1f806a6bb005a5d7d667dee2
current_db	default
current_hostname	sih.onemadogre.com
job	Jobs::UserEmail
problem_db	default
opts
type	user_posted
user_id	115
notification_id	21710
current_site_id	default

But this appears to occur and clear sporadically (e.g. not just this week) and happened earlier in the week, so possibly not related.

Please let me know if there's any more information I can provide to improve this report, or if these issues were actually (largely) fixed by the now thrice referenced zogstrip commit and I just need to chill. Last few days have been hectic and without a lot of sleep so a bit fading in and out of consciousness at the moment, feel like I'm forgetting something.

Posts: 1

Participants: 1

Read full topic

@eriko wrote:

Is it possible to have the text box that shows up for a "Something else" flag also show up for the inappropriate flag? Is there some setting for this.

Posts: 1

Participants: 1

Read full topic

@jomaxro wrote:

Not sure if this is related to the recent DDoS attack, but I have noticed that user mentions look different than they used to. Now if I mention @jomaxro it appears to have a grey font color. Before, it would look like this: with black text.

Is this a side effect of the attack, or a feature change I just missed ?

Posts: 10

Participants: 6

Read full topic

@owenudacity wrote:

Greetings,

I posted a support question in the middle of some network issues, and would not have posted if I had known it was a known issue. In this case, the Twitter feed for Discourse had the latest, and I didn't think to check it until someone pointed it out to me.

For other sites I'll head to status.x.y when I need to know if there's an outage. In our case, that points to meta.discourse.org. Unfortunately, in this case, that didn't give me the status I needed. At the same time, I love that you have a responsive Twitter feed, and don't want to discourage that.

So, I have a request that status get cross-posted to meta somehow when issues arise - perhaps as something pinned at the top of the support category. You don't need to be worrying about notifying multiple channels while you're fighting a problem, but hopefully your API and the Twitter API make it possible to cross-post without driving yourself batty.

Thanks for considering!

Posts: 2

Participants: 2

Read full topic

@awole20 wrote:

Hey,

A bit of feedback from using discourse a little more -- I'm really enjoying the heat monitors for high like ratios and view at a glance colour schemes. They are also quite easy on the eyes at a glance.

I was going to suggest or even PR a similar color indicator for posts that have been necro'd so that resurrected posts that filter back to the top can be easily seen at a glance as well. Then I noticed that this feature already exists, and I felt foolish.

I've updated it in my discourse instance and it is much easier to distinguish.

body .coldmap-high {
    color: #04C2BF !important;
}
body .coldmap-med {
    color: #37BFBD !important;
}
body .coldmap-low {
    color: #77BFBE !important;
}

Wondering what you guys think about possibly adding something similar as well in core. It is much easier to at a glance catch up and miss old topics that have been updated. I realize you don't want to drag too much attention/highlight to an old post, but as it stands it's really difficult to see much distinction at a glance in vanilla.

Posts: 2

Participants: 2

Read full topic

@emanuelet wrote:

Hi Guys,
I'm developing a customised Discourse and I ran into an issue.
I will like to add Polymer on my assets, but I will like to do it in a maintainable way (something similar of having a bower.json) through a plugin.

Any suggestion on the right way to do it?
Bower?
NPM Ember-polymer?
Gem ? (polymer-elements-rails?)

Cheers

Posts: 1

Participants: 1

Read full topic

@meglio wrote:

Step 1. Click on the "split topic" unread notification:

Pasted image479x1138 352 Bytes

Step 2. Let the web application fully update:

Pasted image1581x1270 637 KB

Notice there is no notification shown - is this a positioning problem?

Step 3. Open the profile menu again, notification was not marked as read:

Pasted image466x1122 349 Bytes

---

The url the notification links to: http://forum.kozovod.com/t/kormovaya-baza-dlya-koz-samostoyatelno-na-uchastke-do-15-sotok/2093/34

Posts: 4

Participants: 2

Read full topic

@DeanMarkTaylor wrote:

Can we get some dark theme CSS love for the category mentions ?

Currently unreadable:

Black seems to be explicit in the CSS

#bug

Posts: 6

Participants: 4

Read full topic

@Lance wrote:

Please go easy on me. Dangerous enough to get in trouble here.

Total newbie here to Discourse, forums admin, everything!

Managed to get theparkingforums.com up and running. I am tweaking what I can and would like users to be able to sign on with google accounts. I did step by step instruction in the welcome topic, got my long codes and secret code from google, selected enable. Tried it and got error.

Error: invalid_client

The OAuth client was not found.

Forum is hosted here: http://theparkingforum.discoursehosting.net/

Now set up to be here: www.theparkingforums.com

Any ideas what I did wrong?

Thanks!

Posts: 1

Participants: 1

Read full topic

@Ossama wrote:

Howdy,

Whenever there's a flagged content that need to moderated, usually you want to contact the OP regarding his post and what was the problem. So usually i get this message.

I click on Agree (hide post + send PM), then it does hide the post, and send PM. But sometimes I'd rather make it more humane and add some information regarding his post. So i suggest adding a 3rd option to do the same, and giving you the option to edit the text before sending.

Why not to replace the current? because if you have a couple of flagged content, you don't want to go back and forth to remove them all.

Posts: 1

Participants: 1

Read full topic

@ljpp wrote:

Here is what I currently do:

• Enable read-only
• Backup
• Upgrade

Discourse however jumps out of read-only after an upgrade and sometimes there are multiple components to update (like today: Beta 9, Docker manager and spoler alert) and every upgrade turns off the read-only mode.

Does it make a difference during upgrades? How do you do it here on Meta or some other busy site?

Posts: 1

Participants: 1

Read full topic

@gingerling wrote:

I am at http://flosscommunitymetrics.org/ and just noting my thoughts relating to discourse.

Thought 1: monitoring regular contributors activity over time in order to care for your community members.

We have about 10 hard-core contributors on out forum (not many, can be tracked by a human over time). Recently, one of our key people "fell of the map" and stopped talking, after about 10 days I realised there was something wrong. Turns out he was seriously ill, we sent him a bunch of flowers etc, now he is better. Would be good to monitor individuals over time for big changes in their posting behaviour, so in a larger project the community manager/leader can reach out and find out what the issue is.

Posts: 6

Participants: 4

Read full topic

@ljpp wrote:

This bug has been:

• Reproduced by two different people at least
• Two different devices (Air 1 @ iOS 9.2, Air 2 @ iOS 9.2.1
• Reproduced at here at Meta and at Tappara.co, today. Tappara.co is on Beta 9.

How to reproduce:

Using Chrome browser: Open a long message thread. Move to bottom of the thread. Go back to index page by tapping the logo.

What is the issue:

Screen content is not drawn. Site seems to function in the background, as for example the unread counter is being updated. Content should re-appear when scrolling a bit.

image.png1536x2048 36.2 KB

IMG_20160130_175047777.jpg1456x2592 410 KB

IMG_20160130_174401252.jpg1456x2592 431 KB

Posts: 4

Participants: 3

Read full topic