@Aaditya_Agrawal wrote:

Post for getting ratings plugin for discourse.

Posts: 3

Participants: 3

Read full topic

@karussell wrote:

In this thread I’ve created a simple process to download the backups from a different server, but this seems to be broken as the URLs are not available (bad request) even with credentials.

Now I tried to see how the potentially new URL structure looks like but when I tried manually downloading the backup there seems to be a ruby exception:

Message (397 copies reported)

Sidekiq heartbeat test failed, restarting

Backtrace

/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/logster-1.2.7/lib/logster/logger.rb:93:in `add_with_opts'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/logster-1.2.7/lib/logster/logger.rb:50:in `add'
/usr/local/lib/ruby/2.3.0/logger.rb:498:in `warn'
config/unicorn.conf.rb:173:in `check_sidekiq_heartbeat'
config/unicorn.conf.rb:190:in `master_sleep'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:294:in `join'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.0/bin/unicorn:126:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:22:in `load'
/var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:22:in `<main>'

and then

Recent
Message (7 copies reported)

ActionController::ParameterMissing (param is missing or the value is empty: token)
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_controller/metal/strong_parameters.rb:368:in `rescue in fetch'

Backtrace

/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_controller/metal/strong_parameters.rb:368:in `rescue in fetch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_controller/metal/strong_parameters.rb:366:in `fetch'
/var/www/discourse/app/controllers/admin/backups_controller.rb:61:in `show'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/abstract_controller/base.rb:198:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_controller/metal/rendering.rb:10:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:117:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:505:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:778:in `_run_process_action_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/notifications.rb:164:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/notifications.rb:164:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/abstract_controller/base.rb:137:in `process'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.8/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/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'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_controller/metal.rb:237:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/routing/route_set.rb:74:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/routing/route_set.rb:43:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/routing/mapper.rb:49:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/journey/router.rb:43:in `block in serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/journey/router.rb:30:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/journey/router.rb:30:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/routing/route_set.rb:817:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/builder.rb:63:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/conditionalget.rb:25:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/head.rb:13:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:136:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/flash.rb:260:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/session/abstract/id.rb:225:in `context'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/session/abstract/id.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/cookies.rb:560:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:653:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:88:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:778:in `_run_call_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/logster-1.2.7/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/rack/logger.rb:22:in `call'
/var/www/discourse/config/initializers/100-quiet_logger.rb:17:in `call_with_quiet_assets'
/var/www/discourse/config/initializers/100-silence_logger.rb:29:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/methodoverride.rb:22:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/runtime.rb:18:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/sendfile.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.4/lib/mini_profiler/profiler.rb:171:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus/rack/middleware.rb:62:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:73:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:518:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/application.rb:165:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/railtie.rb:194:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/urlmap.rb:66:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/urlmap.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/urlmap.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:606:in `process_client'
/var/www/discourse/lib/scheduler/defer.rb:85:in `process_client'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:702:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:549:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:142:in `start'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.0/bin/unicorn:126:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:22:in `load'
/var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:22:in `<main>'

Env
application_version	8b6e4d18672ae6b97ba68dda2b69031a506ee457
HTTP_HOST	discuss.graphhopper.com
REQUEST_URI	/admin/backups/graphhopper-forum-2017-09-16-033144-v20170831180419.tar.gz?api_key=[key]&api_username=karussell

I’m currently using v1.8.7

And will downloading the files work with API key? Jeff said ‘no’ here

Posts: 3

Participants: 2

Read full topic

@jack2 wrote:

When trying to delete a non-existent topic with the API, I get this (somewhat) understandable error:

status=403
content={"errors":["You are not permitted to view the requested resource."],
    "error_type":"invalid_access"}

When trying to delete a non-existent tag, I get this:

status=500
content=NoMethodError in TagsController#destroy -
    undefined method `destroy' for nil:NilClass

Posts: 1

Participants: 1

Read full topic

@RBoy wrote:

I noticed for the past few days no emails were being sent for posts on the forum. I checked the dashboard and found 0 emails for the past 3 days. No idea why, I had to reboot the server and then it started sending emails but here are a few issues I am noticing:

1. There was no notification provided on the admin account that it’s having issues sending emails, even the logs didn’t show any errors
2. After the reboot it starting sending the backlog of emails but the problem is after sending the initial batch of 100 emails now I’m getting an error Job exception: 454 4.7.0 Too many login attempts, please try again later and it’s stuck in that loop continuously trying to login to sending the remaining emails but the server is rejecting it.
   It looks like for EACH email it’s trying to login to the SMTP server. This IMHO is a bug, it should not login to the server for each email when there is more than one email to send, it should reuse the existing connection.
3. Now it’s stuck in this trying to login loop even few seconds, how do I stop it and ask it to back off for 10-15 minutes and try again?

Posts: 1

Participants: 1

Read full topic

@jomaxro wrote:

You can now send a PM to an email address, even if the user does not exist on your site! Email addresses sent to in this way will become staged users, and will have full access to their PM history if they sign up for the site.

Thank you @nbianca for the PR!

Posts: 2

Participants: 2

Read full topic

@eviltrout wrote:

It’s been a long time since we revisited the flagging and moderator tools in Discourse. The interface worked well enough, but on some forums that dealt with a large volume of flags, things could get a little unruly.

Improved Flagging Interface

If you get the latest version of Discourse, you’ll find a modified flagging interface:

Screen Shot 2017-09-25 at 1.41.08 PM.png2048x388 66.2 KB

• It’s a single column layout, and flaggers are listed below the post to allow room for displaying many more.

• You can click to expand the post’s full contents.

• You can suspend directly from the flags page. If you do, it will be logged and associated with the post you flagged.

Suspension Improvements

There are also some changes to the suspension modal:

Screen Shot 2017-09-25 at 1.45.10 PM.png1272x710 36.6 KB

• There’s now a rich timeframe picker to choose a timeframe for your suspension, with some default values to make suspending faster.

• You can optionally input a message to the user you’re suspending. If you do so, the message will be emailed to the user when they are suspended.

• There is a new site setting hide suspension reasons that will hide suspension reasons from a user’s public profile.

Flagged Topics View

Screen Shot 2017-09-25 at 1.48.12 PM.png2054x536 102 KB

There’s a brand new view that groups flags by topic. This is useful in high traffic sites where the same topic might have many changes. The view will try to give you a bird’s eye view of all the flags in all the topics on your site. If you click the magnifying glass button you’ll get a filtered list of flags restricted to that topic.

Supercharged discourse-assign

We’ve heard feedback that some forums have several moderators who work on the same flag queue simultaneously.

If you install the latest version of the discourse-assign plugin, extra functionality will be attached to flags:

Screen Shot 2017-09-25 at 1.56.14 PM.png2054x284 61.5 KB

Clicking the “claim” button will assign the topic to you, and prevent other moderators from operating on its flags. This gives you time to look into things without worrying and stepping on another moderator’s toes.

Screen Shot 2017-09-25 at 2.04.11 PM.png1916x408 55 KB

It will even sync claims across our message bus so that you can see who is claiming topics without refreshing your browser:

As always, please use this topic to provide feedback and report bugs! Cheers and happy moderating.

Posts: 1

Participants: 1

Read full topic

@tobiaseigen wrote:

Here’s what the ALL ACTIVITY page looks like for this new user when I visit it directly from the usercard - note the blue line with no text in it. It should say something like NO ACTIVITY in that blue line.

Screen Shot 2017-09-25 at 11.08.25 AM.png1146x647 48.1 KB

Here’s the same ALL ACTIVITY page after selecting REPLIES and then selecting ALL again. Note it says NO REPLIES in the blue line on the ALL ACTIVITY page. The same behavior happens when switching to any of the other menu items and then switching back to ALL - except for TOPICS.

Screen Shot 2017-09-25 at 11.12.52 AM.png1158x651 49.7 KB

Posts: 1

Participants: 1

Read full topic

@ckshen wrote:

Has anyone come across a situation where

• larger images are uploaded into a post
• and the post is not ‘parsed’ by the software like it normally is after the reply/ post button is clicked, to generate the optimized images?

It seems it has stopped entirely for me. I just updated to the v1.9.0.beta10 +17 this Saturday. The images are hosted on S3. Rebaking the individual post within the GUI doesn’t generate the optimized images. Rebooting the server doen’t help the situation.

Clues, anyone?

Posts: 1

Participants: 1

Read full topic

@Jesusdlg wrote:

Hello everyone,

Just found today this awesome forum script and really loved, congratulations!

However, I’m trying to figure it a few things… but 1st things come 1st. I’ve been around the internet for a long time and I used before forums scripts like (UBB, VBulletin, IPBoard (current) and others) so…

1. I’ll like to know server requirements in order to put my own Discourse installation (I know it doesn’t use mySQL)

2. Is there a theme/design guide or some examples in order to see what I can do with my forum install?

3. Does anyone knows if there’s an importer from IPBoard to Discourse?

4. Any how-to guide to use this properly or some videos will also help

Thank you in advance for pointing me or helping me solve this questions and sorry if I didn’t use the proper forum to post my message, this one seemed the more appropriate to do so.

Looking forward to read your answers/suggestions

Jesus

Posts: 3

Participants: 2

Read full topic

@Stranik wrote:

[2017-09-25T19:22:59.759723 #14]
INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate'
rake aborted!

Summary

/var/www/discourse/plugins/discourse-voting/app/controllers/discourse_voting/votes_controller.rb:3:in `<class:VotesController>'
/var/www/discourse/plugins/discourse-voting/app/controllers/discourse_voting/votes_controller.rb:2:in `<module:DiscourseVoting>'
/var/www/discourse/plugins/discourse-voting/app/controllers/discourse_voting/votes_controller.rb:1:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-5.1.3/lib/active_support/dependencies.rb:292:in `require'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-5.1.3/lib/active_support/dependencies.rb:292:in `block in require'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-5.1.3/lib/active_support/dependencies.rb:258:in `load_dependency'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-5.1.3/lib/active_support/dependencies.rb:292:in `require'
/var/www/discourse/plugins/discourse-voting/plugin.rb:268:in `block in activate!'
/var/www/discourse/lib/plugin/instance.rb:248:in `block in notify_after_initialize'
/var/www/discourse/lib/plugin/instance.rb:246:in `each'
/var/www/discourse/lib/plugin/instance.rb:246:in `notify_after_initialize'
/var/www/discourse/config/application.rb:211:in `each'
/var/www/discourse/config/application.rb:211:in `block in <class:Application>'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-5.1.3/lib/active_support/lazy_load_hooks.rb:43:in `execute_hook'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-5.1.3/lib/active_support/lazy_load_hooks.rb:52:in `block in run_load_hooks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-5.1.3/lib/active_support/lazy_load_hooks.rb:51:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-5.1.3/lib/active_support/lazy_load_hooks.rb:51:in `run_load_hooks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-5.1.3/lib/rails/application/finisher.rb:73:in `block in <module:Finisher>'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-5.1.3/lib/rails/initializable.rb:30:in `instance_exec'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-5.1.3/lib/rails/initializable.rb:30:in `run'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-5.1.3/lib/rails/initializable.rb:59:in `block in run_initializers'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-5.1.3/lib/rails/initializable.rb:58:in `run_initializers'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-5.1.3/lib/rails/application.rb:353:in `initialize!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-5.1.3/lib/rails/railtie.rb:185:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-5.1.3/lib/rails/railtie.rb:185:in `method_missing'
/var/www/discourse/config/environment.rb:5:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-5.1.3/lib/active_support/dependencies.rb:292:in `require'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-5.1.3/lib/active_support/dependencies.rb:292:in `block in require'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-5.1.3/lib/active_support/dependencies.rb:258:in `load_dependency'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-5.1.3/lib/active_support/dependencies.rb:292:in `require'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-5.1.3/lib/rails/application.rb:329:in `require_environment!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-5.1.3/lib/rails/application.rb:445:in `block in run_tasks_blocks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rake-12.0.0/exe/rake:27:in `<top (required)>'
/usr/local/bin/bundle:22:in `load'
/usr/local/bin/bundle:22:in `<main>'
Tasks: TOP => db:migrate => environment
(See full trace by running task with --trace)
I, [2017-09-25T19:23:10.352672 #14]  INFO -- :
I, [2017-09-25T19:23:10.353695 #14]  INFO -- : Terminating async processes
I, [2017-09-25T19:23:10.353865 #14]  INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/9.5/bin/postmaster -D /etc/postgresql/9.5/main pid: 44
2017-09-25 19:23:10.354 UTC [44] LOG:  received fast shutdown request
2017-09-25 19:23:10.354 UTC [44] LOG:  aborting any active transactions
2017-09-25 19:23:10.354 UTC [51] LOG:  autovacuum launcher shutting down
I, [2017-09-25T19:23:10.354255 #14]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 157
157:signal-handler (1506367390) Received SIGTERM scheduling shutdown...
2017-09-25 19:23:10.358 UTC [48] LOG:  shutting down
157:M 25 Sep 19:23:10.371 # User requested shutdown...
157:M 25 Sep 19:23:10.371 * Saving the final RDB snapshot before exiting.
2017-09-25 19:23:10.376 UTC [48] LOG:  database system is shut down
157:M 25 Sep 19:23:10.572 * DB saved on disk
157:M 25 Sep 19:23:10.572 # Redis is now ready to exit, bye bye...


FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 10774 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle install --deployment --verbose --without test --without development'", "su discourse -c 'bundle exec rake db:migrate'", "su discourse -c 'bundle exec rake assets:precompile'"]}
4ab8ca560a347103e631a7f30084ed2495b005d825145a61b9fbbe72e8c17453
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one

Posts: 1

Participants: 1

Read full topic

@JohnMHarrisJr wrote:

I can’t enable mailing list mode, when I go back to the settings for email after saving I just see it’s not ticked and I don’t get emails for posts other than what I’m watching.

Posts: 4

Participants: 3

Read full topic

@achamess wrote:

I just installed the wp-discourse plugin.

I followed the instructions on both my forum and blog.

I was able to create a new topic in the forum from the Wordpress blog:
So the plugin talks with the forum.
But then when I made a test comment in the topic in the forum, there was no reflection of that on the blog. For example, it still says “Start a conversation at…”

Blog: The best value reels on the market | Go Fish Carolinas
Forum: The best value reels on the market - Equipment - Go Fish Carolinas

What I’m looking to see is the Forum comments, like at this example:

What might I be doing wrong?

Also, if this is relevant, I’m using the Divi theme from Elegant themes. It’s a bit non-standard, but it should work, I think.

Posts: 3

Participants: 2

Read full topic

@djcyry wrote:

Hi ,
I want to test ovh ssd or cloud vps servers.
I am thinking about ssd2 or cloud2 package .
So , as i know , the panel of ovh and dns setting are a little hard to understand , so my question is :

Can i use/create cloudflare dns with the vps ip ?
Can i use also mailgun with cloudflare ?
Any recomendation / review ?!
Actually , DO client .

Thanks in advance .

Posts: 1

Participants: 1

Read full topic

@pfaffman wrote:

Hey, @gerhard. I’m still doing an import with a bunch of mailing lists sucked in to nabble.

There are a bunch of posts that are announcements and have a line of dashes near the top, so the whole post gets truncated by trim since the line is a delimiter:

I think I’m just going to edit out those lines for this import and move on with my life.

But is there a better way?

Posts: 2

Participants: 2

Read full topic

@schungx wrote:

Currently, if a user is anonymous, the locale is take from the HTTP accept-language:

This does not happen for logged in users.

For new users who first came to the site, their language is set to the site default. This may not be optimal, as the user can be from any world region.

It would be nice to detect whether user.effective_locale is default, and if so set it to locale_from_header. This way, new users will automatically see the site from his/her own language.

They can, of course, change it themselves in their profile, but not every new user knows how to do this, they being “new”. And language is such a significant part of the user experience.

Posts: 6

Participants: 2

Read full topic

@abangmanja wrote:

Hi,

I want to show first few images in each topic on topic listing. For example. In topic listing, first 2-3 images that uploaded into each topic will be shown under the title of the topic. Is if possible?

89136967-DCA2-4CA6-B965-A64DF4BA5EB4.jpeg1242x2084 551 KB

Posts: 2

Participants: 2

Read full topic

@tophee wrote:

Is anyone else having trouble with getting people to like posts they obviously find useful?

I have been posting dozens of canned replies over the past weeks encouraging people to like posts whenever someone said “thank you” etc but didn’t the post. I can see some results, but overall, I think it could be better.

Or perhaps it’s normal? But if I take meta for comparison, it had roughly 10k posts over the past 30 days and also 10k likes. So roughly 1 like per post. We had 2.8k posts but only 733 likes. So about 1 like per 4 posts. Both forums are support forums.

Any ideas? Strategies? Similar experiences? Should I stop posting my canned replies to make people aware of the button? Or should I change it? Here is what it says:

BTW: A good way of showing your appreciation for a post is to like it: just press the button under the post.

If you asked the original question, you can also mark an answer as the accepted answer which solved your problem using the tick-box button you see under each reply.

All of this also helps the forum software distinguish interesting from less interesting posts when compiling summary emails.

Posts: 8

Participants: 6

Read full topic

@barryvan wrote:

Just noticed this here on meta a few seconds ago:

image.png824x89 11.5 KB

As the most recent replier, I’d expect to see my avatar appear in the stats bar immediately; the “last reply” and number of replies updates automatically.

It also looks like the number of likes doesn’t update automatically.

I’d imagine that this should be more all-or-nothing than it is at present…?

Posts: 2

Participants: 2

Read full topic

@tophee wrote:

I wonder if something was forgotten when the syntax formatting for uploaded images was changed some time ago. I received a reply to a PM which was created from an email. The good thing is: the breakpoint between the post and the previous email was identified correctly. But an image which was included at the bottom of the email rendered like this in the post:

Note also the “301 Moved Permanently” link. The URL behind it is: https://forum.mydomain.com/letter_avatar_proxy/v2/letter/f/58f4c7/45.png and it correctly brings up my avatar if clicked. Since that part of the email is hidden anyway, I’m just bringing that up as an aside and because the breakpoint is not always identified correctly so that this strange link may show up from time to time.

Anyway, my main concern here is with the image from the email which was correctly uploaded (it is accessible via the url shown in the screenshot) but failed to be rendered correctly in the actual post.

Posts: 1

Participants: 1

Read full topic

@tophee wrote:

Am I missunderstanding something about how oneboxing works or why do some forum links render as a mini onebox and others as a full onebox:

Notify on every like should be the default

And on an external discourse forum, these same urls render like this:

image.png714x233 46.2 KB

And on yet another external discourse forum, the first link doesn’t even produce a mini-onebox, it’s just rendered as an ordinary link…

Posts: 2

Participants: 2

Read full topic