Quantcast
Channel: Discourse Meta - Latest topics
Viewing all 60690 articles
Browse latest View live

Does anyone have an OAuth 1.0 plugin sample?

$
0
0

@Ad_Huikeshoven wrote:

We like to setup Oauth (not Oauth2) identification at https://discourse.wmflabs.org/. Authentification will be against existing accounts at any wikimedia site like e.g. https://en.wikipedia.org/ or https://www.mediawiki.org/ or https://commons.wikimedia.org/ or https://meta.wikimeda.org/. A ticket is up at https://phabricator.wikimedia.org/T124691. Wikimedians can login at phabricator with a wikimedia account, it has Oauth identification, not Oauth2 identification. I have found sample plugins for Oauth2, but not for Oauth. Has anyone a sample Oauth plugin?

Posts: 3

Participants: 2

Read full topic


Allowing www. on discourse

$
0
0

@rexi88 wrote:

Hey,

Trying to set my prefered domain on google webmasters and it won't let me select anything until I add the www. version of my site:

Part of the process of setting a preferred domain is to verify that you own http://www.domain.com/. Please verify http://www.domain.com

Is there a setting to allow this? I only need it to verify on webmsters to then change my preffered domain to https:// domain.com/

Thanks

Posts: 3

Participants: 2

Read full topic

Feature request: receive reply email via http

$
0
0

@zh99998 wrote:

some mail delivery provider or domain register provider, can forward mail to HTTP POST .
it will be much easier to configure reply by email if discourse can receive them.

Posts: 3

Participants: 2

Read full topic

Reply Keys / reply email addresses not always used - mail client issues

$
0
0

@DeanMarkTaylor wrote:

I've been tracking on-and-off an issue where mail clients...

...don't always use the "reply+%reply-key-here%@example.com" email address when the user selects to reply to an email notification.

Instead the email client selecting the Reply-To email address with the reply key, it selects the From email address.

For example for a notification from "meta" I see emails sent the the following headers:

From: Jeff Atwood <info@discourse.org>
Reply-To: Discourse Meta <reply+%reply-key-here%@discourse.org>

In my case some email clients are effectively sending emails to info@discourse.org but for my Discourse instance.

In the case of the Discourse installation I have been monitoring we don't see much mail-in posting, so this issue might be larger for other instances.

I understand that mail functionality has changed a lot since the initial instances of this in this log below, but having the first occurrence in 2016 made me write this up.

The table below contains date and time, email client identifier gleamed from email headers and the users email domain:

30 January 2016 at 08:42 - Yahoo Mail for iPad - @yahoo.com
8 October 2015 at 16:02 - iPhone Mail (12B440) - @googlemail.com
13 August 2015 at 21:09 - com.samsung.android.email - @live.co.uk
9 July 2015 at 18:26 - com.android.email - @aol.com
8 July 2015 at 10:01 - com.android.email - @aol.com
18 June 2015 at 20:20 - com.android.email - @aol.com
16 June 2015 at 20:19 - com.android.email - @aol.com
12 June 2015 at 19:04 - com.samsung.android.email - @gmail.com
12 June 2015 at 18:56 - com.samsung.android.email - @gmail.com
21 April 2015 at 16:33 - com.android.email - @yahoo.com
19 April 2015 at 20:02 - com.android.email - @yahoo.com
6 February 2015 at 19:33 - "Sent from my Windows Phone" - @gmail.com
1 February 2015 at 20:22 - "Sent from my Windows Phone" - @gmail.com
19 January 2015 at 15:57 - com.android.email - @yahoo.com
19 January 2015 at 13:27 - com.android.email - @yahoo.com
16 September 2014 at 15:12 - com.android.email - @aol.com

In each case of this occurring the user has been contacted individually and pointed towards a better mail client.
Difficult to explain to users, usual response "I'm just using the normal one called 'mail'."

What can be done?

  • You can't change the "From" address each time, because complications - mail server configs, SPAM problems etc.
  • Other systems include a number in the subject line or body. Perhaps ugly - could it be done it a better way?

Should something be done?

  • Is this a problem?
  • how much does it occur?
  • Do others tack emails sent "to" their "From" email addresses?

Just thought I would share - "put it on the radar".

Posts: 3

Participants: 2

Read full topic

Receiving mail with SendGrid

Facebook-like Newsfeed tab (As a means to better mix topics from high-volume and low-volume categories)

$
0
0

@mcwumbly wrote:

I was thinking about adding a category on a new forum that could risk being very noisy. The basic idea is similar to what is described here: Wanted: Discourse Hacker News Plugin

My concern with adding such a category is that it could dominate the latest page if people post too much. But I don't want to discourage posting anything interesting here. And I'm not sure that I want to completely hide the category from latest, because that could also damage its usefulness.

So the first thought that came to mind was adding a setting on categories that would limit how many topics show up on the latest page... Sounds like a simple approach, but it has some issues. Let's assume we put the number 5 into the forseen max_topics_on_latest box.

If it were really noisy, those topics might always be newer than everything else. So they'd just be stuck at the top of the topic list... not ideal.

So, what if instead it was a limit_percentage_of_latest box instead? And so if I put 10 in the box then at most 1 of every 10 topics shown on latest would be from this category?

Well that opens a small can of worms since chronology will get disrupted in some fashion.

Which leads me to think the best way to approach this problem is to come up with a tab that isn't exactly Latest. Rather than the strict chronology we're used to here on discourse and on twitter, I imagine a more facebook-like approach would be necessary. On this 'Newsfeed' tab, strict chronology would not be a promise or an expectation. Instead, what is displayed would attempt to balance different content, taking user preferences into account based on what they read more of, who they interact with more, plus some influence from the moderators on what they want to see promoted, etc.

What do folks think of this idea?

Some other related topics:

Posts: 3

Participants: 2

Read full topic

Error when moving post to existing topic

$
0
0

@jamesmarkcook wrote:

A member of my forum accidentally hit the 'Reply as linked topic' link when replying to a topic. Now I want to close the new topic and move the post into the original topic. However I run into the following error:

NoMethodError (undefined method 'update_column' for nil:NilClass)
/var/www/discourse/app/models/post_mover.rb:88:in 'create_first_post'

Full stacktrace:

/var/www/discourse/app/models/post_mover.rb:88:in 'create_first_post'
/var/www/discourse/app/models/post_mover.rb:77:in 'block in move_each_post'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/relation/delegation.rb:46:in 'each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/relation/delegation.rb:46:in 'each'
/var/www/discourse/app/models/post_mover.rb:76:in 'move_each_post'
/var/www/discourse/app/models/post_mover.rb:46:in 'move_posts_to'
/var/www/discourse/app/models/post_mover.rb:18:in 'block in to_topic'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/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.5.1/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.5.1/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.5.1/lib/active_record/transactions.rb:220:in 'transaction'
/var/www/discourse/app/models/post_mover.rb:17:in 'to_topic'
/var/www/discourse/app/models/topic.rb:645:in 'move_posts'
/var/www/discourse/app/controllers/topics_controller.rb:599:in 'move_posts_to_destination'
/var/www/discourse/app/controllers/topics_controller.rb:414:in 'move_posts'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.1/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.1/lib/abstract_controller/base.rb:198:in 'process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.1/lib/action_controller/metal/rendering.rb:10:in 'process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.1/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.1/lib/active_support/callbacks.rb:117:in 'call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:117:in 'call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/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.1/lib/active_support/callbacks.rb:505:in 'call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:505:in 'call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:92:in '__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/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.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/abstract_controller/callbacks.rb:19:in 'process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.1/lib/action_controller/metal/rescue.rb:29:in 'process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.1/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.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/actionpack-4.2.5.1/lib/action_controller/metal/instrumentation.rb:30:in 'process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.1/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.1/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.1/lib/abstract_controller/base.rb:137:in 'process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.2.5.1/lib/action_view/rendering.rb:30:in 'process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.8/lib/mini_profiler/profiling_methods.rb:106:in 'block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.1/lib/action_controller/metal.rb:196:in 'dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.1/lib/action_controller/metal/rack_delegation.rb:13:in 'dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.1/lib/action_controller/metal.rb:237:in 'block in action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.1/lib/action_dispatch/routing/route_set.rb:74:in 'call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.1/lib/action_dispatch/routing/route_set.rb:74:in 'dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.1/lib/action_dispatch/routing/route_set.rb:43:in 'serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.1/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.1/lib/action_dispatch/journey/router.rb:30:in 'each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.1/lib/action_dispatch/journey/router.rb:30:in 'serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.1/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/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.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: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.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:in 'call'
/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:in 'block 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:in '_run_call_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:in 'call'
/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:in 'call'
/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:in 'call'
/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: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.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: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.8/lib/mini_profiler/profiler.rb:282: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: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.1/lib/rails/engine.rb:518:in 'call'
/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:in 'public_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: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:132:in 'start'
/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:in 'load'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in '<main>'

I don't mind trying to debug this myself but I was just wondering if anybody else has run into this problem before, or if the reasoning is immediately obvious to the core contributors to Discourse.

Any help would be greatly appreciated! :thumbsup:

Posts: 3

Participants: 2

Read full topic

List of project ideas for Google Summer of Code 2016

$
0
0

@erlend_sh wrote:

Please post your links to any appropriate GSoC ideas here. If you're not familiar with GSoC, briefly put it's an event run by Google wherein they pay students to work on an open source project for 3 months.

https://developers.google.com/open-source/gsoc/

If you have a feature on your wishlist that fits the scope of a 3-month student project, share it here!

If you have an idea that hasn't been discussed before, please start a new topic about it first and then link to it from here. Feel free to share multiple links in one reply.

GSoC Projects

Common event system for chatrooms

Posts: 3

Participants: 3

Read full topic


Navigating via a sub-category mention then unable to go back

$
0
0

@DeanMarkTaylor wrote:

If you navigate to a sub-category via a sub-category mention you are then unable to use the browsers back / previous page navigation to return to the page you clicked the link on.

Steps to Reproduce

  1. Select a sub-category mention i.e. #feature:spec
  2. Select the browsers back button or use keyboard navigation — Alt +

Expected Result

To return to the page you clicked the category mention link on (the one that contained #feature:spec )

Actual Result

See "spec" topics list refresh.

Posts: 4

Participants: 2

Read full topic

Changing flag resolution?

$
0
0

@gdelprete wrote:

Hi,

I installed a test instance of Discourse to play with it. I flagged a message, then resolved it. Now the post does not show the flag icon anymore, nor I can understand if I can change that flag resolution... can someone explain what's happening?

Posts: 3

Participants: 3

Read full topic

NameCheap DNS vs DigitalOcean DNS

$
0
0

@BluSpektrum wrote:

Installing new instance of Discourse on DigitalOcean. I have a domain through NameCheap. Do I need to invoke 'Custom DNS' in NameCheap and point it to DO (ns1.digitalocean.com, etc) and then do all the domain work (C Name, A Name, etc) through DO? Or should the domain work be done through NameCheap?

Posts: 5

Participants: 3

Read full topic

Certain Topics redirect back to home screen

$
0
0

@MiG wrote:

Some users are seeing a weird behaviour on my Discourse install. It's a docker-based install on a Linode VPS.

Here's a screencast of what it looks like:

So far I've only seen it happening on Firefox, not on other browsers, but that may just be luck.

The symptoms seem to clear up after a few browser refreshes. I'm using Cloudflare, but I've switched it to "developer mode" and it's still happening.

Any advice on how I could troubleshoot what's happening? URL is http://forum.hackingthemainframe.com BTW.

Posts: 3

Participants: 2

Read full topic

Preserve quotes from messages that start threads

$
0
0

@UndecidedAdmin wrote:

I am working on importing an mbox archive from a mailman mailing list into discourse. I've found that Discourse's email Parse doors a pretty good job, but it does a bit too good of a job on quoted messages that start threads.

For example, when someone forwards a message into the mailing list, the message often contains content that is prefixed with the '>' character. This content is lost when I import it into Discourse with the mbox importer. I believe the same thing happens when a user forwards a quoted message to Discourse to start a thread.

Is there is a way to disable the quote removal feature, for messages that start threads? I looked at the import handling code, and it looks like the parser doesn't have knowledge of the thread position, so I'm not sure if its possible right now.

Thanks.

Posts: 1

Participants: 1

Read full topic

Would any of the following work as a plugin?

I want to Start my own Community


How do I remove "Your topic is similar to..."?

$
0
0

@Alankrit_Choudh wrote:

I would like to remove this as it pops up on the right side of the composer. (On top of Preview section). I am on a lower resolution screen.
Anyway, I could get rid of this completely?

Posts: 9

Participants: 4

Read full topic

FAQ in hamburger menu is always NEW

Restore on multisite fails for anything but the primary database

$
0
0

@Sander78 wrote:

Case:
* Restore a backup from a Discourse installation that is not the primary instance of a multisite
* Error in log is permission denied for database <database_name>

Posts: 1

Participants: 1

Read full topic

Customize login page

$
0
0

@weebo wrote:

Hello, I'm new on Discourse platform. Just created my community about accounting at www.racun.org. It is in my native language(Serbian).

What is the problem? I currently don't allow anonymous viewing so this is how landing page look on mobile:

There is no Sign Up button. It is inside menu.

Can I somehow modify layout to add it up. It is confusing for my users how to sign up when there is no Sign Up button. I would replace bottom Log in with Sign Up or add next to it.

Posts: 1

Participants: 1

Read full topic

Server scaling and load created by the plugin

$
0
0

@steve_pd wrote:

We recently included Discourse in our APM, having noticed that performance was beginning to drag a little.

Our existing site is around 15/16 months old and sits on a 2GB/2core DO box (with swap). The instance isn't massive, we have around 15k threads, or thereabouts.

This seems to be the problem:

I was tempted to sling it onto a larger host, but after a bit more digging noticed that the wp-discourse plugin on our front end site, which is quite large and reasonably high trafficked, is by far the most consuming:

Making anything between 1k and 3k calls per minute. We don't have debugging enabled, so Discourse shouldn't be hammered by every post view, but judging from the native performance reports in Discourse the wordpress route is by far the most heavily trafficked, by several orders of magnitude.

Is there any way to throttle this behavior? I can throw more resources at our Discourse instance, or attempt to move it into AWS so it's adjacent to our front end servers, but at the same time would like to understand the cause before I begin treating symptoms.

Posts: 8

Participants: 2

Read full topic

Viewing all 60690 articles
Browse latest View live




Latest Images