@carlokok wrote:

rake aborted!
NoMethodError: undefined method `each_pair' for nil:NilClass
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/core_ext/hash/deep_merge.rb:22:in
 `deep_merge!'
/var/www/discourse/lib/js_locale_helper.rb:10:in `block in
plugin_translations'
/var/www/discourse/lib/js_locale_helper.rb:9:in `each'
/var/www/discourse/lib/js_locale_helper.rb:9:in `plugin_translations'
/var/www/discourse/lib/js_locale_helper.rb:30:in `load_translations'
/var/www/discourse/lib/js_locale_helper.rb:67:in `block in
load_translations_merged'
/var/www/discourse/lib/js_locale_helper.rb:66:in `each'
/var/www/discourse/lib/js_locale_helper.rb:66:in
`load_translations_merged'
/var/www/discourse/lib/js_locale_helper.rb:89:in `translations_for'
/var/www/discourse/lib/js_locale_helper.rb:101:in `output_locale'
/var/www/discourse/app/assets/javascripts/locales/nl.js.erb:3:in
`_evaluate_template'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/erb_processor.rb:26:in
 `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/erb_processor.rb:13:in
 `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/processor_utils.rb:75:in
 `call_processor'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/processor_utils.rb:57:in
 `block in call_processors'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/processor_utils.rb:56:in
 `reverse_each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/processor_utils.rb:56:in
 `call_processors'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/loader.rb:134:in
 `load_from_unloaded'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/loader.rb:60:in
 `block in load'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/loader.rb:317:in
 `fetch_asset_from_dependency_cache'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/loader.rb:44:in
 `load'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/cached_environment.rb:20:in
 `block in initialize'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/cached_environment.rb:47:in
 `load'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/bundle.rb:23:in
 `block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/utils.rb:196:in
 `dfs'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/bundle.rb:24:in
 `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/processor_utils.rb:75:in
 `call_processor'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/processor_utils.rb:57:in
 `block in call_processors'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/processor_utils.rb:56:in
 `reverse_each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/processor_utils.rb:56:in
 `call_processors'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/loader.rb:134:in
 `load_from_unloaded'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/loader.rb:60:in
 `block in load'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/loader.rb:317:in
 `fetch_asset_from_dependency_cache'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/loader.rb:44:in
 `load'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/cached_environment.rb:20:in
 `block in initialize'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/cached_environment.rb:47:in
 `load'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/base.rb:66:in
 `find_asset'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/base.rb:73:in
 `find_all_linked_assets'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/manifest.rb:134:in
 `block in find'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/manifest.rb:133:in
 `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/manifest.rb:133:in
 `find'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/manifest.rb:185:in
 `compile'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-rails-3.1.1/lib/sprockets/rails/task.rb:68:in
 `block (3 levels) in define'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/rake/sprocketstask.rb:147:in
 `with_logger'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-rails-3.1.1/lib/sprockets/rails/task.rb:67:in
 `block (2 levels) in define'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/exe/rake:27:in
 `<top (required)>'
/usr/local/bin/bundle:23:in `load'
/usr/local/bin/bundle:23:in `<main>'
Tasks: TOP => assets:precompile
(See full trace by running task with --trace)
Bundling assets

Posts: 3

Participants: 2

Read full topic

@codmakr wrote:

I get this error can someone please help me?

Stopping old container
+ /usr/bin/docker stop -t 10 app
app
(<unknown>): found character that cannot start any token while scanning for the next token at line 18 column 3 -e LANG=en_US.UTF-8
YAML syntax error. Please check your containers/*.yml config files.

Try http://www.yamllint.com/ to search an error but there are no errors in there.

Posts: 11

Participants: 3

Read full topic

@xiasummer wrote:

As a beginner of discourse, there seems to be too many plugins and most of them are non-default. Truely I think some of them are fully-developed (you know, no bugs and very helpful. ) and can improve the forum service very much.

But there are still many plugins that are only an idea hoping for suggestions are many plugins useless—— or we say not for most of the forums.

So I think we should maintain a list of plugins recommended. And let the plugin developers to apply for entering such list. We can also vote for the best plugin for the month and then the winner plugin would enter such list. You know, for fun and encourage developers.

Posts: 5

Participants: 5

Read full topic

@battlesnake wrote:

I have configured email:

DISCOURSE_HOSTNAME: mydomain.com

DISCOURSE_SMTP_ADDRESS: myprovider.com
DISCOURSE_SMTP_PORT: 2525
DISCOURSE_SMTP_USER_NAME: username@mydomain.com
DISCOURSE_SMTP_PASSWORD: not_password
DISCOURSE_SMTP_ENABLE_START_TLS: true

I rebuilt the container, and the settings in the admin panel (/admin/email) match.

I enter an address to send a test email to, hit "Send Test Email" and see "Sent!". But the email never arrives (either in Inbox or Spam).

I've tested with swaks:

swaks -s myprovider.com -p 2525 --ehlo mydomain.com -au username@mydomain.com -ap not_password -a PLAIN --tls --tls-verify -t myself@gmail.com -f username@mydomain.com --body "From $(hostname)"

1. When run from my laptop, the email arrives within seconds.

2. When run from the cloud server, the email arrives within seconds.

3. When run from within the Discourse Docker container, the email arrives within seconds.

4. But when I send a test email via Discourse, it doesn't arrive. Nobody is receiving emails from the Discourse site.

For (4), here is a tail of shared/standalone/log/rails/production.log:

Started POST "/admin/email/test" for 188.222.201.238 at 2016-09-29 13:41:39 +0000
Processing by Admin::EmailController#test as */*
  Parameters: {"email_address"=>"myself@gmail.com"}

Sent mail to myself@gmail.com (378.0ms)
  Rendered text template (0.1ms)
Completed 200 OK in 535ms (Views: 1.8ms | ActiveRecord: 4.9ms)

I should add that the hostname set in the docker container does not match DISCOURSE_HOSTNAME. It is instead *-discourse, where * is the first subdomain of the full hostname name of the host machine. With TCPDUMP, I found that the EHLO command has the wrong local host name (although I doubt that this matters): EHLO localhost.localdomain

I have also reviewed the suggestions at https://meta.discourse.org/t/troubleshooting-email-on-a-new-discourse-install/16326/2

Info for current configuration:
* Git revision: "0a27bab Bump acme.sh version."
* Git remote: "https://github.com/discourse/discourse_docker.git"

Posts: 2

Participants: 1

Read full topic

@adopilot wrote:

My apologies if this was a case before or if this is already implemented.
When topic is created by e mail , and somebody answers to that topic.
Can discource in that case to do e mail response to creator without standard wait time for e mail notifications.

Posts: 1

Participants: 1

Read full topic

@Alberto_Soares wrote:

Hi,

So yesterday I followed the install docs and I have a new discourse instance running on a digitalocean droplet. I just installed discourse, changed some logos, add ssl to it and nothing more.

Today google reports this site with potential malware. I've been looking at the logs, and some websites that supposedly help with this, to no avail (one of the errors on one of those site was that the instance had a link to discourse.org).

I can always create a new droplet (and probably I will), but I wan't to know what is going on, so that I can prevent this of happening again.

Thx!

Edit: forgot to add the link http://forum.umn.space/

Posts: 5

Participants: 4

Read full topic

@codmakr wrote:

The title says everything.

We need this feature for an internal Forum, does anyone knows a plugin or a other way?

Posts: 3

Participants: 3

Read full topic

@kudos wrote:

If I install the Discourse with the help of Bitnami then it installs a bit older version and i could not find automatic update system when I tried their 1 Hour trial server. So is there a way by which Discourse could be upgraded almost like automatically?

Posts: 10

Participants: 4

Read full topic

@kudos wrote:

Can discourse be customized beyond just CSS colors options that are available in Admin.

Customization as in →

1. Customized Header and Footer
2. Possibility of placing widget or snippets or even placing advertisement slots such Google ads etc.[Inner pages such as → https://meta.discourse.org/t/with-the-new-right-gutter-where-should-reply-as-linked-topic-go/44815]

Posts: 4

Participants: 2

Read full topic

@Mihai_Raulea wrote:

I get this error, when running the rake command in my vagrant machine. I followed the tutorial here:

I am using Mac OS X El Capitan.

Here is the error:

vagrant@discourse:/vagrant$ bundle exec rake db:migrate
DEPRECATION WARNING: Sprockets method register_engine is deprecated.
Please register a mime type using register_mime_type then
use register_compressor or register_transformer.

(called from at /vagrant/lib/es6_module_transpiler/sprockets.rb:3)
rake aborted!
Errno::ENOENT: No such file or directory @ rb_sysopen - /home/vagrant/.rvm/gems/ruby-2.3.1/gems/ember-data-source-2.3.0.beta.5/dist/ember-data.js

I thought vagrant was supposed to make this painless?

Posts: 1

Participants: 1

Read full topic

@interneteur wrote:

I just installed discourse using the tutorial offered here https://github.com/discourse/discourse/blob/master/docs/INSTALL.md all went well, except when I put in to have it be done with lets encrypt. What I'm trying to do is have the discourse be domain.com and have www.domain.com redirect, but I also followed the directions https://meta.discourse.org/t/how-do-i-redirect-www-to-non-www/20039 and it's still not resolving the www and redirecting to the none www. But the site resolves fine on https://domain.com

Posts: 1

Participants: 1

Read full topic

@mackk wrote:

Eu não sou do Brasil, mas eu falo um pouco português

Seems like this might actually be a bug? This is what I'm seeing.

Screen Shot 2016-09-29 at 3.46.27 PM.png2304x670 125 KB

Screen Shot 2016-09-29 at 3.45.34 PM.png2012x412 63.3 KB

So the translation is pulled on the badges page, but not in the notifications dropdown, for some reason... (but some translations are pulled in the notifications dropdown).

Posts: 4

Participants: 2

Read full topic

@zachwlewis wrote:

Continuing the discussion from Docker rebuild failed updating Postgresql: Signature verification failed:

After following the steps on the Discourse update page, I was asked to update via the command line. When updating via the command line, I was asked to update my app.yml, and the update essentially attempted to downgrade my postgresql install, resulting in all my data being lost. Luckily, I have several backups in an S3 bucket.

After a bit of work, my Discourse install was running, but it was a totally fresh copy. I pointed the backups directory to the S3 bucket, but was unable to see any of my old backups. To test that everything was configured correctly, I ran a manual backup, which appeared both in my Discourse Backups page and in the S3 bucket (alongside the previous backups).

I made very sure to keep lots of backups in case I somehow lost all my data. How can I restore from these backups?

Posts: 10

Participants: 3

Read full topic

@robbyoconnor wrote:

Looks like the latest update to tests-passed failed in our Docker Manager: I was updating to cde1883 Currently at 119225e

***  Bundling assets. This might take a while ***
$ bundle exec rake assets:precompile
Purging temp files
rake aborted!
NoMethodError: undefined method `each_pair' for nil:NilClass
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/core_ext/hash/deep_merge.rb:22:in `deep_merge!'
/var/www/discourse/lib/js_locale_helper.rb:10:in `block in plugin_translations'
/var/www/discourse/lib/js_locale_helper.rb:9:in `each'
/var/www/discourse/lib/js_locale_helper.rb:9:in `plugin_translations'
/var/www/discourse/lib/js_locale_helper.rb:30:in `load_translations'
/var/www/discourse/lib/js_locale_helper.rb:67:in `block in load_translations_merged'
/var/www/discourse/lib/js_locale_helper.rb:66:in `each'
/var/www/discourse/lib/js_locale_helper.rb:66:in `load_translations_merged'
/var/www/discourse/lib/js_locale_helper.rb:89:in `translations_for'
/var/www/discourse/lib/js_locale_helper.rb:101:in `output_locale'
/var/www/discourse/app/assets/javascripts/locales/nl.js.erb:3:in `_evaluate_template'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/erb_processor.rb:26:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/erb_processor.rb:13:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/processor_utils.rb:75:in `call_processor'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/processor_utils.rb:57:in `block in call_processors'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/processor_utils.rb:56:in `reverse_each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/processor_utils.rb:56:in `call_processors'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/loader.rb:134:in `load_from_unloaded'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/loader.rb:60:in `block in load'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/loader.rb:317:in `fetch_asset_from_dependency_cache'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/loader.rb:44:in `load'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/cached_environment.rb:20:in `block in initialize'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/cached_environment.rb:47:in `load'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/bundle.rb:23:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/utils.rb:196:in `dfs'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/bundle.rb:24:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/processor_utils.rb:75:in `call_processor'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/processor_utils.rb:57:in `block in call_processors'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/processor_utils.rb:56:in `reverse_each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/processor_utils.rb:56:in `call_processors'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/loader.rb:134:in `load_from_unloaded'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/loader.rb:60:in `block in load'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/loader.rb:317:in `fetch_asset_from_dependency_cache'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/loader.rb:44:in `load'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/cached_environment.rb:20:in `block in initialize'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/cached_environment.rb:47:in `load'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/base.rb:66:in `find_asset'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/base.rb:73:in `find_all_linked_assets'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/manifest.rb:134:in `block in find'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/manifest.rb:133:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/manifest.rb:133:in `find'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/sprockets/manifest.rb:185:in `compile'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-rails-3.1.1/lib/sprockets/rails/task.rb:68:in `block (3 levels) in define'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-3.6.3/lib/rake/sprocketstask.rb:147:in `with_logger'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sprockets-rails-3.1.1/lib/sprockets/rails/task.rb:67:in `block (2 levels) in define'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/exe/rake:27:in `<top (required)>'
/usr/local/bin/bundle:23:in `load'
/usr/local/bin/bundle:23:in `<main>'
Tasks: TOP => assets:precompile
(See full trace by running task with --trace)
Bundling assets

Posts: 3

Participants: 2

Read full topic

@dylanh7241 wrote:

I made a test account >>

Activated the email >>

The first thing I did was reply to a post >>

In the post, all I did was quote someone and say "Ahhhhh, that would be bad.."

I got this (sent from my super admin account):

Pasted image799x305 20.6 KB

I've seen other new users post fine (I've never approved 1 new account before) -- why was this guy blocked? And how do I prevent this from happening while my forum is still super new (I could always enable it later)?

Posts: 2

Participants: 2

Read full topic

@kstaikov wrote:

/directory_items?period=all&order=likes_received returns a 500.

On the UI, the spinner just spins forever if I have selected all time, otherwise the other options (weekly, monthly, etc.) load OK. However, they show a user that is blank that is probably a test user I deleted after making a post:

Screen Shot 2016-09-30 at 3.04.22 AM.png2334x496 50.3 KB

The logs show a serializer error:

NoMethodError (undefined method `time_read' for nil:NilClass) /var/www/discourse/app/serializers/directory_item_serializer.rb:14:in `time_read'

Posts: 7

Participants: 3

Read full topic

@erlend_sh wrote:

Continuing the discussion from Nominate Discourse for CMS Critic Awards 2016:

If you like Discourse, please take a moment aside to vote for us in the CMS Critic Awards.

Thanks!

Posts: 1

Participants: 1

Read full topic

@Chopper wrote:

I notice on my forum if a share a link of a public topic on a private or public topic there is a preview like this :

But if I share a private topic on the same private topic or another one also private, there is no preview, just a link (a made an error on this link to show you the result)

https://meta.discourse.org/t/sidekiq-is-consuming-too-much-memory-restarting/4839

By private i mean not all the community can read the post, only a group !

Version : v1.7.0.beta5 +45

Posts: 3

Participants: 2

Read full topic

@louirobert wrote:

I'm using the official discourse tags plugin: discourse-tagging and I'm planning to upgrade my Discourse instance to a higher version with tags built-in and thus without the need of the plugin. Before taking real action I decide to make a test. So I setup a clean local dev Discourse instance with v1.6.4 stable without the plugin, and filled it(by "script/discourse restore") with backup data from my production instance(v1.6.0beta1). I did see the settings for the tags but:
1) The tags I created by the tags plugin are gone! How could I migrate the old tags to new version?
2) There's no drop list for tags beside the category drop list, while there was when using the plugin. So how could users view topic by tags? Say, he wants to see a list of tags and then to click on one to find topics on it?

Thanks.

Posts: 3

Participants: 2

Read full topic

@Law wrote:

Just wondering is there a way to put a Stripe payment form within a post.

We sell club stickers on our site and normally use paypal which works but want to move over to Stripe payment gateway.

Just wondering if there is a way to embeded it within a post at all.

<*form action="/your-server-side-code" method="POST">
<script
src="https://checkout.stripe.com/checkout.js" class="stripe-button"
data-key="***"
data-amount="2000"
data-name="Name"
data-description="2 widgets"
data-image=""
data-locale="auto"
data-zip-code="true"
data-currency="gbp">
<*/script>
<*/form>

Thanks in advance.

Posts: 3

Participants: 3

Read full topic