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

"latest,-" doesnt work after upgrade from 1.3 to 1.5

0
0

@internetman wrote:

Hello and thanks for this great software!

Up until today I've had the top menu exclude the moderator category on my front page. After upgrading to 1.5.0.beta2 this does not seem to work anymore. Any suggestions?

Cheers

Posts: 1

Participants: 1

Read full topic


Discourse Backup Vs DO Backup?

0
0

@Siraj_M wrote:

I have slightly confusion, if discourse have fully backup option so do we need to enable DO backup option which is premium at this time. Is discourse backup contains all things of discourse community forum.
Actually DO backup is premium and friendly speaking still I have zero experience with DO backups.

Secondly, DO snapshots are free, is it good and is it contains all things of discourse forum?

I need suggestion from any experts who can understand this strategy. Thank you!

Posts: 2

Participants: 2

Read full topic

VPS setup help me

0
0

@suleyman wrote:

Hello I anlatabilirm this software much like I just gotta get VPS know what kind https://www.digitalocean.com/'m not informed to install it in linux ubuntu and course or previously digitaloce in the Qur'an there is one up to the end of the beginning?

Posts: 2

Participants: 2

Read full topic

Translation of yml template

0
0

@ber-64 wrote:

Hi,

how translations are included into discourse. I've checked out the server.pl_PL.yml and some lines are missing:

signup:
  text_body_template:

where in:

signup:
  subject_template: "[%{site_name}] Confirm your new account"
  text_body_template:

The line subject_template is missing. This is transifex doing? Why when there is no translation the config file doesn't include original EN text.

How now I should include translation and put into working instance of discourse?

Posts: 1

Participants: 1

Read full topic

Cannot upload or backup to Amazon S3

0
0

@bartv wrote:

Hi,

we've been trying to set up backup to S3 in the 1.4 stable version, hosted on DiscourseHosting. Our access keys are correct and we can upload through their CLI. However, Discourse throws the following errors (see dump below).

We found an issue that seems to be related:

Any ideas?

[2015-10-12 07:49:16] Executing the after_create_hook for the backup
[2015-10-12 07:49:18] EXCEPTION: multipart upload failed: The request signature we calculated does not match the signature you provided. Check your key and signing method.; The request signature we calculated does not match the signature you provided. Check your key and signing method.; The request signature we calculated does not match the signature you provided. Check your key and signing method.; The request signature we calculated does not match the signature you provided. Check your key and signing method.; The request signature we calculated does not match the signature you provided. Check your key and signing method.; The request signature we calculated does not match the signature you provided. Check your key and signing method.; The request signature we calculated does not match the signature you provided. Check your key and signing method.; The request signature we calculated does not match the signature you provided. Check your key and signing method.; The request signature we calculated does not match the signature you provided. Check your key and signing method.; The request signature we calculated does not match the signature you provided. Check your key and signing method.
[2015-10-12 07:49:18] /var/www/discourse/vendor/bundle/ruby/2.2.0/gems/aws-sdk-resources-2.0.45/lib/aws-sdk-resources/services/s3/multipart_file_uploader.rb:71:in `abort_upload'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/aws-sdk-resources-2.0.45/lib/aws-sdk-resources/services/s3/multipart_file_uploader.rb:60:in `upload_parts'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/aws-sdk-resources-2.0.45/lib/aws-sdk-resources/services/s3/multipart_file_uploader.rb:34:in `upload'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/aws-sdk-resources-2.0.45/lib/aws-sdk-resources/services/s3/file_uploader.rb:32:in `upload'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/aws-sdk-resources-2.0.45/lib/aws-sdk-resources/services/s3/object.rb:102:in `upload_file'
/var/www/discourse/lib/s3_helper.rb:16:in `upload'
/var/www/discourse/app/models/backup.rb:54:in `block in upload_to_s3'
/var/www/discourse/app/models/backup.rb:53:in `open'
/var/www/discourse/app/models/backup.rb:53:in `upload_to_s3'
/var/www/discourse/app/models/backup.rb:33:in `after_create_hook'
/var/www/discourse/lib/backup_restore/backuper.rb:267:in `after_create_hook'
/var/www/discourse/lib/backup_restore/backuper.rb:49:in `run'
/var/www/discourse/lib/backup_restore/backup_restore.rb:161:in `block in start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:158:in `fork'
/var/www/discourse/lib/backup_restore/backup_restore.rb:158:in `start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:13:in `backup!'
/var/www/discourse/app/controllers/admin/backups_controller.rb:31:in `create'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/abstract_controller/base.rb:189:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_controller/metal/rendering.rb:10:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:552:in `block (2 levels) in compile'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:502:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:502:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:86:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/activesupport-4.1.10/lib/active_support/notifications.rb:159:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/activesupport-4.1.10/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/activesupport-4.1.10/lib/active_support/notifications.rb:159:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/activerecord-4.1.10/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/abstract_controller/base.rb:136:in `process'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionview-4.1.10/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/rack-mini-profiler-0.9.6/lib/mini_profiler/profiling_methods.rb:77:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_controller/metal.rb:232:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:82:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:82:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/mapper.rb:45:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_dispatch/journey/router.rb:73:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_dispatch/journey/router.rb:59:in `each'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_dispatch/journey/router.rb:59:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:692:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/omniauth-1.2.2/lib/omniauth/builder.rb:59:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/rack-1.5.5/lib/rack/conditionalget.rb:35:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/rack-1.5.5/lib/rack/head.rb:11:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:124:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/flash.rb:254:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/message_bus-1.0.16/lib/message_bus/rack/middleware.rb:60:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/rack-1.5.5/lib/rack/session/abstract/id.rb:225:in `context'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/rack-1.5.5/lib/rack/session/abstract/id.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/cookies.rb:562:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/activerecord-4.1.10/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/gems/rails_multisite/lib/rails_multisite/connection_management.rb:175:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:82:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/remote_ip.rb:76:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/logster-1.0.0.3.pre/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/railties-4.1.10/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/railties-4.1.10/lib/rails/rack/logger.rb:22:in `call'
/var/www/discourse/config/initializers/quiet_logger.rb:10:in `call_with_quiet_assets'
/var/www/discourse/config/initializers/silence_logger.rb:26:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/rack-1.5.5/lib/rack/methodoverride.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/rack-1.5.5/lib/rack/runtime.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/rack-1.5.5/lib/rack/sendfile.rb:112:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/rack-mini-profiler-0.9.6/lib/mini_profiler/profiler.rb:170:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:73:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/railties-4.1.10/lib/rails/engine.rb:514:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/railties-4.1.10/lib/rails/application.rb:144:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/railties-4.1.10/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/railties-4.1.10/lib/rails/railtie.rb:194:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/rack-1.5.5/lib/rack/builder.rb:138:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/rack-1.5.5/lib/rack/urlmap.rb:65:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/rack-1.5.5/lib/rack/urlmap.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/rack-1.5.5/lib/rack/urlmap.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/thin-1.6.3/lib/thin/connection.rb:86:in `block in pre_process'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/thin-1.6.3/lib/thin/connection.rb:84:in `catch'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/thin-1.6.3/lib/thin/connection.rb:84:in `pre_process'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/thin-1.6.3/lib/thin/connection.rb:53:in `process'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/thin-1.6.3/lib/thin/connection.rb:39:in `receive_data'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/eventmachine-1.0.7/lib/eventmachine.rb:187:in `run_machine'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/eventmachine-1.0.7/lib/eventmachine.rb:187:in `run'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/thin-1.6.3/lib/thin/backends/base.rb:73:in `start'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/thin-1.6.3/lib/thin/server.rb:162:in `start'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/thin-1.6.3/lib/thin/controllers/controller.rb:87:in `start'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/thin-1.6.3/lib/thin/runner.rb:200:in `run_command'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/thin-1.6.3/lib/thin/runner.rb:156:in `run!'
/var/www/discourse/vendor/bundle/ruby/2.2.0/gems/thin-1.6.3/bin/thin:6:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.2.0/bin/thin:23:in `load'
/var/www/discourse/vendor/bundle/ruby/2.2.0/bin/thin:23:in `<main>'
[2015-10-12 07:49:18] Notifying 'pap' of the end of the backup...
[2015-10-12 07:49:18] Removing old backups...
[2015-10-12 07:49:18] Cleaning stuff up...
[2015-10-12 07:49:18] Removing '.tar' leftovers...
[2015-10-12 07:49:18] Removing tmp '/var/www/discourse/tmp/backups/db4890/2015-10-12-074605' directory...
[2015-10-12 07:49:18] Unpausing sidekiq...
[2015-10-12 07:49:18] Marking backup as finished...
[2015-10-12 07:49:18] Finished!

Posts: 2

Participants: 2

Read full topic

Upgrade failed after the recent today's commits: «cannot load such file -- rails_multisite»

0
0

@dmitry_fedyuk wrote:

Tested in Vagrant.

LoadError: cannot load such file -- rails_multisite
/var/lib/gems/2.2.0/gems/bundler-1.9.4/lib/bundler/runtime.rb:76:in require'
/var/lib/gems/2.2.0/gems/bundler-1.9.4/lib/bundler/runtime.rb:76:in
block (2 levels) in require'
/var/lib/gems/2.2.0/gems/bundler-1.9.4/lib/bundler/runtime.rb:72:in each'
/var/lib/gems/2.2.0/gems/bundler-1.9.4/lib/bundler/runtime.rb:72:in
block in require'
/var/lib/gems/2.2.0/gems/bundler-1.9.4/lib/bundler/runtime.rb:61:in each'
/var/lib/gems/2.2.0/gems/bundler-1.9.4/lib/bundler/runtime.rb:61:in
require'
/var/lib/gems/2.2.0/gems/bundler-1.9.4/lib/bundler.rb:134:in require'
/vagrant/config/application.rb:15:in
'
/vagrant/Rakefile:5:in require'
/vagrant/Rakefile:5:in
'

Posts: 5

Participants: 5

Read full topic

How to show badges in the message list?

0
0

@bartv wrote:

Hi,

I'm interested in using badges to gamify our community some more. While they're great for people who receive them, badges are also still quite 'invisible' on the site, and I feel that doesn't encourage the desired behaviour as much as it could.

The closest I've come is to instruct members to use a badge as their title:



The drawbacks of this approach are:

  • People need instruction to display the badge
  • Visibility is low
  • There's no hyperlink to badge info
  • You can only use one badge at a time

Is there a way that we can show selected (not all!) badges in the message list and apply styling?

For example, here's how we have styled our 'Staff' group. It would be great if I could have a small number of badges here too with some styling (color+icon) and a link to their info pages:



Any ideas?

Posts: 8

Participants: 5

Read full topic

Unhandled error when importing banned user

0
0

@dandv wrote:

While running the MyBB importer to incrementally import the posts created since the last import before finally shutting down the MyBB forum, I got this error for a user I had banned in Discourse but hadn't yet deleted from MyBB:

creating users
     4679 / 4736 ( 98.8%)  Failed to create user id: 8382, username: adamssofia, email: adamssofia02@gmail.com
user errors: ["Email is not allowed."]
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activemodel-4.2.4/lib/active_model/attribute_methods.rb:433:in `method_missing': undefined method `user_profiler' for #<User:0x0055be977ef260> (NoMethodError)
        from /var/www/discourse/script/import_scripts/base.rb:242:in `block in create_users'
        from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.7/lib/patches/db/mysql2.rb:6:in `each'
        from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.7/lib/patches/db/mysql2.rb:6:in `each'
        from /var/www/discourse/script/import_scripts/base.rb:221:in `create_users'
        from mybb2.rb:54:in `block in import_users'
        from /var/www/discourse/script/import_scripts/base.rb:665:in `block in batches'
        from /var/www/discourse/script/import_scripts/base.rb:664:in `loop'
        from /var/www/discourse/script/import_scripts/base.rb:664:in `batches'
        from mybb2.rb:39:in `import_users'
        from mybb2.rb:24:in `execute'
        from /var/www/discourse/script/import_scripts/base.rb:45:in `perform'
        from mybb2.rb:221:in `<main>'

Posts: 5

Participants: 4

Read full topic


Help Guidance for New Users

0
0

@JeffreyKeefer wrote:

Has anybody found new participants get overwhelmed when they use Discourse for the first couple times? I know there is a welcome email they get, though wonder if anybody has found a need to simplify them or otherwise post instructions or a basic one-pager to help new discussion participants who may get overwhelmed how the system works?

Posts: 2

Participants: 2

Read full topic

Modifying the home template

0
0

@d90 wrote:

Hi - is there a way to modify the home template so that only the logo and the search is visible?

I would like to have a template where the logo is on the top and right under it is the search bar (kind of like Google search). How can this be achieved?

Thank you in advance

Posts: 1

Participants: 1

Read full topic

Discourse embed blocked on "Loading Discussion..."

0
0

@Anthony_Lethuillier wrote:

Hello,

I have set up a Discourse instance on my server and it works fine.

But when I try to embed it on my Ghost blog the Discourse frame just shows

"Loading Discussion..."

Here is the code I insert :

<div id='discourse-comments'></div>

<script type="text/javascript">
  DiscourseEmbed = { discourseUrl: 'http://discourse.domain.net/',
                                discourseEmbedUrl: 'http://subdomain.domain{{url}}'};

  (function() {
    var d = document.createElement('script'); d.type = 'text/javascript'; d.async = true;
    d.src = DiscourseEmbed.discourseUrl + 'javascripts/embed.js';
    (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(d);
  })();
</script>

I use the admin username I set up first and the allowed host is blog.domain.net

The discourse.domain.net/logs gives me no errors

Any advice on what to do next ?

Thanks

Posts: 7

Participants: 3

Read full topic

"Promoter" Badge broken?

0
0

@uppfinnarn wrote:

It looks like the "Promoter" badge isn't getting assigned properly, at least on our forum.

The SQL for it is:

SELECT u.id user_id, current_timestamp granted_at
FROM users u
WHERE u.id IN (
  SELECT invited_by_id
  FROM invites i
  JOIN users u2 ON u2.id = i.user_id
  WHERE i.deleted_at IS NULL AND u2.active AND u2.trust_level >= 0 AND not u2.blocked
  GROUP BY invited_by_id
  HAVING COUNT(*) > 1
) AND u.active AND NOT u.blocked AND u.id > 0 AND
  (:backfill OR u.id IN (:user_ids) )

The problem appears to be the HAVING COUNT(*) > 1… shouldn't that be HAVING COUNT(*) >= 1? Requiring someone to have invited more than one person to get the Promoter badge seems strange.

Posts: 5

Participants: 3

Read full topic

Optimizing discourse for creating a free host

0
0

@cawas wrote:

Since yesterday I've been talking a bit with my friend about creating a discourse hosting for as cheap as possible, probably even offering some truly free options. And we just started thinking about what would be the technical challenges there (right, @michaeld? :stuck_out_tongue_winking_eye:).

The idea is that by giving everyone the possibility of starting their own "ghost towns" we could see a lot of terrible stuff along with some amazing ones. Sure people already can do it in so many other forum tools, but then some of them do grow up and get stuck in those less than optimal software. There's just nothing like discourse out there, and we believe it's very unlikely there will be any time soon.

Ghost Towns?

Our wish is guaranteeing good enough speed for at most 2 active users, including the admin. From there, offering paid plans, still cheaper and more granular than the current "starts at U$10", maybe around U$5 or even less.

No automated updates, no dedicated support, everything unmanned (at least at first).

I can predict 2 major bumps to overcome:

  • Hardware resources. What would you say or guess to be the bare minimum requirement? It seems 512 MB RAM is way more than enough for this. How about building a shared host?

  • RoR and Docker. What would be the optimal configurations? Is there much room to improve discourse source? Maybe, even going Python or Node? If that's the case, maybe it would be too high of a bump for us.

This is all very early brainstorming, just wanted to hear from others who had experienced similar stuff or could chime in with some more expertise if this might sound like a doable plan.

Posts: 5

Participants: 3

Read full topic

Uploaded images disappeared

0
0

@wglass wrote:

Hi,

I'm running 1.5 beta 1. After installing I uploaded an image into a message (in the "assets" thread, and set up gravatar images for a couple of users.

As other users registered on the site, suddenly all my user-uploaded image links were broken. I had to re-upload the assets and the user preferences. Newly uploaded images appear fine.

Is this a known issue?

I have my site set up with a subfolder -- could this be related to that?

Posts: 6

Participants: 4

Read full topic

Emails will not send: Job exception: getaddrinfo: Name or service not known

0
0

@meharryp1 wrote:

Backtrace:

/usr/local/lib/ruby/2.0.0/net/smtp.rb:541:in `initialize'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:541:in `open'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:541:in `tcp_socket'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:551:in `block in do_start'
/usr/local/lib/ruby/2.0.0/timeout.rb:66:in `timeout'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:550: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.4/lib/action_mailer/base.rb:543:in `block in deliver_mail'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.4/lib/active_support/notifications.rb:164:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.4/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.4/lib/active_support/notifications.rb:164:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.2.4/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.4/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:65:in `execute'
/var/www/discourse/app/jobs/base.rb:154:in `block (2 levels) in perform'

Posts: 5

Participants: 3

Read full topic


Subfolders - after impersonating redirected to the wrong URL

0
0

@wglass wrote:

I have my site set up with subfolders.

When (as an admin) I impersonate a user, it redirects to the root level of the domain. It should redirect to the subfolder instead.

Posts: 2

Participants: 2

Read full topic

Duplicate/Should Have Searched flags

0
0

@Drew_Warwick wrote:

For forums with feature request / bug report categories, it's not uncommon for duplicate bug reports / feature requests to be filed. For all forums, there's the issue of people not liking to use the search feature and immediately jump to posting whatever is on their mind. The forum I'm part does have feature requests / bug reports, and while we don't use Discourse (yet), both the existing forum software and Discourse do not provide good ways for dealing with both duplicates and people who neglect to use the search feature (yes I'm aware Discourse suggests similar posts when you're drafting your own, but more on that later).

With duplicate reports/requests, I've noticed that even when someone points out that it's a duplicate feature request, no matter how nice or mean they word it, and regardless if it's the first reply on the thread or not, discussion still continues. Forum members will prefer to discuss features / bugs on the most recent thread, probably because one or all of the following:

  • it feels wrong for them to resurrect a thread that hasn't been posted on in so long
  • they want to respond to someone's suggestion/outlook but it's only on the new thread and not the old one
  • they didn't see the "this is a duplicate thread" post and continue leaving feedback on the thread

It's really difficult to manually moderate that kind of stuff and merge threads so often -- I really like the way Discourse headed with the automatic flagging system that took the workload off the moderators' backs, and duplicate post flagging could do some good.

As for posting topics before using the search feature, it becomes a problem because:

  • People make a goof every now and then and forget to use the search feature, but similar to how even though birthdays are rare, only taking 0.27% (a single day) of the entire year, so many people exist on Earth that there are countless birthdays per day, because of the volume of members on the forum it's not uncommon to see posts that could have been answered by searching because there are such a large amount of people tripping up occasionally.

  • Since there isn't a "should have searched" flag to slowly eat away at their trust level and boot them out if and when they continue to ignore the search feature because they don't feel like using it, manual moderation is the only way to get rid of these people. "Oh you should have used the search" isn't exactly "this guy should be removed" material, so this results in these people never being removed and they continue to poison the forum. This manual moderation babysitting is also the exact opposite direction of the one Discourse is going in the event that moderators actively work to oust these types of people.

  • Just linking to threads where the question has already been answered does not motivate people to use the search feature in the future (this comes from personal experience -- they don't realize they're inconveniencing others when they could have just searched it themselves), telling them "please use the search feature" (either on their thread or in a PM) comes off as rude, and since you're calling them out they get super defensive about it or they just don't care that they're inconveniencing other people and in either case telling them doesn't work.

Looking back at "Your topic is similar to",

forum members may forget that it exists after a certain period of time, ignore it and not care about it, or close it because it gets in the way. It also may not provide perfect matches to similar threads and posters would assume there was no similar thread even though they would have found it through the search feature. Additionally, we've had problems with threads where they start repeating themselves ever couple of pages -- people are lazy and don't want to read the whole thread before posting so they end up asking the same questions over and over and over. We can't start booting people left and right for this because so many people do it, and just telling them not to doesn't stop them from doing that in the future. I'd also like to point out that StackExchange has the "your topic is similar to" notification as well, but the community can still flag topics as duplicates -- it's because the "your topic is similar to", while helpful in solving the problem, does not solve the problem completely.

Getting a PM that says your post/topic has been hidden because it was flagged by the community and knowing that if you continue that behavior you will eventually get booted from the community provides excellent motivation to improve behavior, and I'm sure the Discourse team knows that very well. It would be amazing if there were flags for duplicate posts / should have used the search feature or read the thread in general so duplicate posts and people who are too quick to post manageable, and preventing moderators from having to babysit the forum with manual moderation every time this occurs. When flagged for being a duplicate thread, it should automatically either be merged with the original thread or closed and linked to the original thread (merging it directly might result in weird results). When flagged for not using the search feature / reading the thread, the post should be hidden automatically like if it were spam and the poster notified in their inbox that it had already been answered (with links people provided to the post(s) that had answered their question).

Posts: 7

Participants: 5

Read full topic

Is it possible to have discourse sort by anything other than recent Activity on the main feed

0
0

@timpone wrote:

I have watched the progression of this app and it looks really slick (well, it always has). One question is whether you can sort via something other than activity? Even possiblly writing custom code for it. I just got out of a meeting where having a custom sort (like number of people who have favorited in the past 6 hours) was proposed. If not currently supported, would it be possible to write a custom plugin or monkeypatch that call?

Posts: 4

Participants: 3

Read full topic

Pinned topic not appearing when navigating away and back to latest

DISCOURSE_ENABLE_CORS not impacting Nginx config

0
0

@ckamps wrote:

I was able to modify the /etc/nginx/conf.d/discourse.conf file to include several Access-Control-... headers to avoid the Unknown error during log in when using SSO.

Now I want to trigger these Nginx settings via app.yml so that we don't have to manually modify the Nginx config. However, when I specify the following settings in the environment section of app.yml and bootstrap via launcher, the Nginx config does not get updated.

Any idea as to what I am missing?

 ## Enable Cross-origin resource sharing so that SSO works properly
 DISCOURSE_ENABLE_CORS: true
 DISCOURSE_CORS_ORIGIN: '*'

Posts: 4

Participants: 2

Read full topic

Viewing all 60309 articles
Browse latest View live




Latest Images