@Tumi wrote:

Hello guys

I got a possitive SSL . What if i want to change the domain for my fresh instance ? I will lose my cert ? Can i use this cert for new domain?

Or mby will be better to do only forwarding for new domain? But the https adres will work or not ? Should i then buy new ssl cert for direct domain witch i want to use??

Posts: 2

Participants: 2

Read full topic

@jomaxro wrote:

The warning received when deleting tags appears to be capped at 30, even when the actual tag count is higher. Warning count is correct when the tag has 30 or less uses.

image.png699x107 2.87 KB

image.png926x251 14.7 KB

Posts: 1

Participants: 1

Read full topic

@Sujan wrote:

I work with a biiiig monitor with Full HD resolution. I enlarged the “Compose” box (Create a new topic, reply to a topic - where I am just typing this) quite a bit. Now I am off for today and back to the 15’’ laptop display with smaller resolution and the box is partly hidden behind the header and I couldn’t find a way to make it smaller and usable again.

Edit: Ctrl + - worked to see that pulling thing again and I could resize the box.

Posts: 1

Participants: 1

Read full topic

@supermathie wrote:

Occasionally, my Android app will forget about the authorization it holds for my Discourse sites and I’ll have to reauthorize it.

Here’s the list of the dates I’ve had to reauthorize it on meta:

Approved: Jul 22
Approved: Sep 9
Approved: Sep 14
Approved: Sep 19
Approved: Sep 26
Approved: Oct 18
Approved: Oct 19
Approved: Nov 9
Approved: Nov 15
Approved: Nov 16
Approved: Nov 24
Approved: Nov 30
Approved: Dec 7

and on another site:

Approved: Sep 14
Approved: Sep 26
Approved: Nov 9
Approved: Nov 18
Approved: Nov 30
Approved: Oct 19
Approved: Nov 15
Approved: Dec 7
Approved: Jul 22
Approved: Sep 19
Approved: Sep 9
Approved: Oct 18
Approved: Nov 24

It seems to happen at the same time for all sites in the list, so I think something is happening on the phone that wipes out the authorization.

Current Chrome version: 63.0.3239.83
Current Android version: 7.0.0; LG-H873 Build/NRD90U

What it’s not:

• phone rebooting

Posts: 1

Participants: 1

Read full topic

@pfaffman wrote:

This is on a hosted instance.

admin/customize/colors/new.

The select base color scheme box comes up, but whether I select dark or light, clicking the “new” button does nothing.

Posts: 6

Participants: 2

Read full topic

@gwmngilfen wrote:

I think we’ve hit an odd edge-case in the inbound email parser. A colleague just sent a post by mail, and on one line it contained a long URL followed by a comma, eg

As I've suggested in https://reallylong/thing/that/has/many/levels#and-a-bunch-of-params-are-here-too,
I will revert the changes in tasks that caused this troubles and release a new version.

However, his email client has tried to flow the paragraph, so what Discourse has actually received is this:

As I've suggested in
https://reallylong/thing/that/has/many/levels#and-a-bunch-of-params-are-here-too
,
I will revert the changes in tasks that caused this troubles and release a
new version

Note how the URL is on it’s own line, and the comma is shifted to a new line. This appears to cause the email parser a problem - the URL becomes a OneBox, and the comma and everything after it is dropped from the post. I’ve tested this by sending the exact same message again, but without the comma, and the second part of the paragraph is then included.

Is there some kind of “a line of all punctuation” regex that is scanning for signatures or something that might be causing this behaviour?

Posts: 5

Participants: 2

Read full topic

@paperless wrote:

Hi all

I’m new to developing on discourse and have been following this guide to setup a development environment for Discourse.

However, I am facing a nasty issue which I have been trying to solve for hours trying to find people with the same issue but to no avail.

When I ran the script linked in the guide to download the necessary technologies, it failed on downloading postgresql (cut for brevity):

Setting up postgresql-common (188.pgdg16.04+1) …
dpkg: error processing package postgresql-common (–configure):
subprocess installed post-installation script returned error exit status 10
dpkg: dependency problems prevent configuration of postgresql-10:
postgresql-10 depends on postgresql-common (>= 182~); however:
Package postgresql-common is not configured yet.
dpkg: error processing package postgresql-10 (–configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
dpkg: dependency problems prevent configuration of postgresql:
postgresql depends on postgresql-10; however:
Package postgresql-10 is not configured yet.
…
…

I figured it might be a PostgreSQL issue on Ubuntu but it seemed like other people are facing other issues pertaining to their problem and I am having a different problem. Can anyone assist me?

I am using Ubuntu 16.04 Xenial. Thank you!

Posts: 2

Participants: 2

Read full topic

@shaundefense wrote:

I’ve tried searching for a simple answer to this with no luck.

If I archive messages, do they ever get deleted? My hope is that they will stay there for future reference while keeping my inbox clean.

Posts: 2

Participants: 2

Read full topic

@ravituvar wrote:

Hello all,

I am facing issue with taking backup from Admin panel…

Here is what I am getting in Logs…

[2017-12-14 05:01:58] 'user' has started the backup!
[2017-12-14 05:01:58] Marking backup as running...
[2017-12-14 05:01:58] Making sure '/opt/bitnami/apps/discourse/htdocs/tmp/backups/default/2017-12-14-050158' exists...
[2017-12-14 05:01:58] EXCEPTION: Permission denied @ dir_s_mkdir - /opt/bitnami/apps/discourse/htdocs/tmp/backups/default/2017-12-14-050158
[2017-12-14 05:01:58] /opt/bitnami/ruby/lib/ruby/2.3.0/fileutils.rb:254:in `mkdir'
/opt/bitnami/ruby/lib/ruby/2.3.0/fileutils.rb:254:in `fu_mkdir'
/opt/bitnami/ruby/lib/ruby/2.3.0/fileutils.rb:228:in `block (2 levels) in mkdir_p'
/opt/bitnami/ruby/lib/ruby/2.3.0/fileutils.rb:226:in `reverse_each'
/opt/bitnami/ruby/lib/ruby/2.3.0/fileutils.rb:226:in `block in mkdir_p'
/opt/bitnami/ruby/lib/ruby/2.3.0/fileutils.rb:211:in `each'
/opt/bitnami/ruby/lib/ruby/2.3.0/fileutils.rb:211:in `mkdir_p'
/opt/bitnami/apps/discourse/htdocs/lib/backup_restore/backuper.rb:308:in `ensure_directory_exists'
/opt/bitnami/apps/discourse/htdocs/lib/backup_restore/backuper.rb:26:in `run'
/opt/bitnami/apps/discourse/htdocs/lib/backup_restore/backup_restore.rb:163:in `block in start!'
/opt/bitnami/apps/discourse/htdocs/lib/backup_restore/backup_restore.rb:160:in `fork'
/opt/bitnami/apps/discourse/htdocs/lib/backup_restore/backup_restore.rb:160:in `start!'
/opt/bitnami/apps/discourse/htdocs/lib/backup_restore/backup_restore.rb:15:in `backup!'
/opt/bitnami/apps/discourse/htdocs/app/controllers/admin/backups_controller.rb:32:in `create'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/abstract_controller/base.rb:198:in `process_action'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_controller/metal/rendering.rb:10:in `process_action'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:117:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:505:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:778:in `_run_process_action_callbacks'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:81:in `run_callbacks'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/abstract_controller/callbacks.rb:19:in `process_action'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_controller/metal/rescue.rb:29:in `process_action'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/notifications.rb:164:in `block in instrument'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/notifications.rb:164:in `instrument'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/abstract_controller/base.rb:137:in `process'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.8/lib/action_view/rendering.rb:30:in `process'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.4/lib/mini_profiler/profiling_methods.rb:76:in `block in profile_method'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_controller/metal.rb:196:in `dispatch'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_controller/metal.rb:237:in `block in action'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/routing/route_set.rb:74:in `dispatch'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/routing/route_set.rb:43:in `serve'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/routing/mapper.rb:49:in `serve'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/journey/router.rb:43:in `block in serve'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/journey/router.rb:30:in `each'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/journey/router.rb:30:in `serve'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/routing/route_set.rb:817:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/builder.rb:63:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/conditionalget.rb:38:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/head.rb:13:in `call'
/opt/bitnami/apps/discourse/htdocs/lib/middleware/anonymous_cache.rb:138:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/flash.rb:260:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/session/abstract/id.rb:225:in `context'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/session/abstract/id.rb:220:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/cookies.rb:560:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/query_cache.rb:36:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:653:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:88:in `__run_callbacks__'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:778:in `_run_call_callbacks'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:81:in `run_callbacks'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/logster-1.2.7/lib/logster/middleware/reporter.rb:31:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/rack/logger.rb:38:in `call_app'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/rack/logger.rb:22:in `call'
/opt/bitnami/apps/discourse/htdocs/config/initializers/100-quiet_logger.rb:17:in `call_with_quiet_assets'
/opt/bitnami/apps/discourse/htdocs/config/initializers/100-silence_logger.rb:29:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/methodoverride.rb:22:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/runtime.rb:18:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/sendfile.rb:113:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.4/lib/mini_profiler/profiler.rb:171:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus/rack/middleware.rb:62:in `call'
/opt/bitnami/apps/discourse/htdocs/lib/middleware/request_tracker.rb:73:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:518:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/application.rb:165:in `call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/railtie.rb:194:in `public_send'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/railtie.rb:194:in `method_missing'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/urlmap.rb:66:in `block in call'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/urlmap.rb:50:in `each'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/urlmap.rb:50:in `call'
/opt/bitnami/ruby/lib/ruby/gems/2.3.0/gems/passenger-5.1.2/src/ruby_supportlib/phusion_passenger/rack/thread_handler_extension.rb:97:in `process_request'
/opt/bitnami/ruby/lib/ruby/gems/2.3.0/gems/passenger-5.1.2/src/ruby_supportlib/phusion_passenger/request_handler/thread_handler.rb:160:in `accept_and_process_next_request'
/opt/bitnami/ruby/lib/ruby/gems/2.3.0/gems/passenger-5.1.2/src/ruby_supportlib/phusion_passenger/request_handler/thread_handler.rb:113:in `main_loop'
/opt/bitnami/ruby/lib/ruby/gems/2.3.0/gems/passenger-5.1.2/src/ruby_supportlib/phusion_passenger/request_handler.rb:416:in `block (3 levels) in start_threads'
/opt/bitnami/ruby/lib/ruby/gems/2.3.0/gems/passenger-5.1.2/src/ruby_supportlib/phusion_passenger/utils.rb:113:in `block in create_thread_and_abort_on_exception'
[2017-12-14 05:01:58] Notifying 'user' of the end of the backup...
[2017-12-14 05:02:09] Removing old backups...
[2017-12-14 05:02:09] Cleaning stuff up...
[2017-12-14 05:02:09] Removing '.tar' leftovers...
[2017-12-14 05:02:09] Unpausing sidekiq...
[2017-12-14 05:02:09] Marking backup as finished...
[2017-12-14 05:02:09] Finished!


Am I missing some permissions?

I am using [v1.8.5-dirty](https://github.com/discourse/discourse/compare/3982a8ef30d6b7fb9cdf4d4b6c2d590175dfe925...HEAD)

Posts: 1

Participants: 1

Read full topic

@kermie wrote:

Hey Tumi,

I’ll tell you. I am a Community Manager at a software vendor and am responsible for the platforms the community (at least most of it’s members) wants to use, keeping these platforms viral, cross-linked and functioning as HUBs (entry points).

On the one hand, there’s a WP installation including a blog (kind of a planet) that is stuffed by several members as well as core devs with tutorials and similar stuff. Before using WP-Discourse, I always had to announce the presence of a new blog post/tutorial manually in the boards. This is done “electrically” with WP-Discourse now - so one step less work for me in announcements. Of course, this WP installation keeps main and so called static content like a “Getting started”, a download area etc. as well.

Before using WP-Discourse, community members somehow found the WP post and started commenting on it. In WP, at least by default, only the author of this blog post and the admin get to know about this comment and had to answer it (although they might have been busy with totally different topics at this time). The other community members didn’t even notice that there’s a comment as they might have visited the post before or someat. An example:

• Blog post about a new software version (to spread the news)

• Comment: "I cannot install it… " or "I cannot update… " because of this and that error message.

Actually, you want to have this discussion in your boards, right? Additionally, these kind of discussions appear in the boards. When using WP-Discourse, all active members of the boards not only get informed about the new blog post, they also see a new comment on it and can react, most likely in a much shorter time than author or admin of the WP blog post could have ever done.
Thanks to the seven gods and @Simon_Cossar, these reactions in the boards can appear as comments on the original blog post within WP.
From my point of view, this is gold as it is possible to create quick reactions, broadly scattered, involve different peeps into platforms, that they mightn’t have know before and (SEO-wise) generate user generated content.

And here it comes to the point you see:

You’re 100% right! And with WP-Discourse options it is possible to sort that out using Max Visible Comments, Min Trust Level or Only Import Moderator-Liked. And yes, activating these options it is absolutely possible to break the communication flow - so heads up when using it!

In doubt - or when this DC issue comes up in Google Search Console - you might set the canonical tag in WP onto the Discourse discussion. On the other hand you want to have the original focused on your blog entry.

I’m not really sure about it: is this mayhap worth a feature request @Simon_Cossar:
[Story] As a WP-Discourse user I want to have an option whether I want to set a canonical tag to the original WP blog post or not.

Cheers!

Posts: 3

Participants: 3

Read full topic

@thirstforwine wrote:

I’ve ‘magpied’ (a lovely term a Primary School teacher once used to talk about how my son’s inspiration for stories could be heavily influenced by content he had read before … not really plagiarism) some wonderfully useful Data Explorer queries from this discussion, but I struggle to understand what they do and some aspects do not work

For example, I don’t understand the use of --- [params]

I’ve struggled to find an introduction to SQL queries for Data Explorer anywhere so that I didn;t have to ask potentially stupid questions or ask others to do work I should be able to do, so if you can point me to any useful resource I would be very grateful!

Posts: 14

Participants: 5

Read full topic

@alehandrof wrote:

@jomaxro Your guide to polls on the Stoneheart Discourse is great:

I’ll link to it from my site for now, but it got me thinking. Is there any interest in collating good guides about less-used (or not so intuitive) Discourse features and packaging them on a GitHub pages site?

Discourse lacks good, coherent, up-to-date documentation. This would be a way to provide readable community-vetted guides to topics such as:

• Creating polls
• Changing email settings
• Adding a site to the mobile app
• Et cetera

I don’t have time to write all of these up, but I could write one or two and then rely on other admins to provide the rest.

Anyone else think this is a good idea?

(Unless something like this already exists and I just don’t know about it!)

Posts: 13

Participants: 9

Read full topic

@youwiki wrote:

Hello!

In profile preferences, category section (/u/*/preferences/categories), there is a choice of the same category for all notification modes i.e. category blacklist (blacklist=selectedCategories) does not work for category-selector component.

So, it may be necessary to add a computed value to /app/assets/javascripts/discourse/controllers/preferences/categories.js.es6 controller to solve this problem:

@computed("model.watchedCategories", "model.trackedCategories", "model.mutedCategories")
selectedCategories(watched, tracked, muted) {
  return [].concat(watched, tracked, muted);
},

Posts: 3

Participants: 2

Read full topic

@Sujan wrote:

If you edit a Canned Reply, it only gets applied if you reload the page.
If you just edit the same canned reply again, you will see the previous (now outdated and wrong) text again.

Posts: 2

Participants: 2

Read full topic

@Sujan wrote:

Search first shows a smaller number of results, updates when you actually scrolled to the bottom.

Example:
https://forum.ionicframework.com/search?q=Did%20you%20remote%20debug%20the%20problem%20on%20the%20device%20already%3F"

First shows:
50 results for Did you remote debug the problem on the device already?"

When scrolled all the way down shows:
175 results for Did you remote debug the problem on the device already?"

If the number of real results is just unknown because of paging, I suggest showing “50+ results” as a workaround.

Posts: 2

Participants: 2

Read full topic

@erlend_sh wrote:

When a new WP post is made and the corresponding Discourse topic is created, could that topic automatically be Pinned (globally) for a given number of days?

A configurable setting for this would be great, but a good default would be something like: Global pin for 2 days.

Would be a handy feature for us here on Meta, and I imagine elsewhere as well.

Posts: 2

Participants: 2

Read full topic

@quimgil wrote:

(This is a continuation of Embedding Discourse Comments via Javascript)

Currently the embedding feature allows to define multiple hosts. However, it is possible to define only one RSS feed to import posts. Processing feeds is more robust and reliable than scrapping HTML content, and therefore it would be very useful to be able to define one RSS feeds for each host.

Posts: 1

Participants: 1

Read full topic

@Sujan wrote:

image.png736x378 16.3 KB

Input fields for Canned Relies used to be bigger in the previous design I think. This is tiny. Why not same size as normal “Compose” fields?

Posts: 2

Participants: 2

Read full topic

@Sujan wrote:

When you include a URL in a post it will display the number of clicks it received. Is this number also available somewhere for all links, aggregated by URL?

Posts: 2

Participants: 2

Read full topic

@Sujan wrote:

I want to insert some information into a previous discussion that is getting quite some search engine traffic. I am a moderator and could edit any post in the topic, but I would greatly prefer to be able to insert a post under my username directly after the topic creating post. Is this possible somehow?

Posts: 6

Participants: 5

Read full topic