@fivem wrote:
Hey, I’ve researched for a bit to try and find out, if I could install discourse on a subdomain using Namecheap.
I have a VPS and I was wondering, if I could install it there and forward it to a subdomain on Namecheap?
NOTE: I do not have a Namecheap VPS.
Posts: 6
Participants: 4
@meglio wrote:
Because message revisions are kept, and older removed messages are also kept, and even removed topics are still there in database, how do I make an image orphaned so it gets removed automatically by a sidekiq job?
Posts: 1
Participants: 1
@SidV wrote:
Hello, I’ve got a doubt with the discussion from Force Discourse to use SSL/HTTPS through CloudFlare.
If I have cloudflare working in my domain with FLEXIBLE SSL option, do I have to config https for discourse docker such this topic says?
I have read many topics about cloudflare, but it is not clear to me.
Sorry for the inconvenience.
Posts: 8
Participants: 4
@achu wrote:
Agenda note-taking app integrates Discourse beautifully like this:
Is there a framework for that? I would like to do the same thing and any direction would be greatly appreciated.
Thanks.
Posts: 3
Participants: 3
@cageycat wrote:
Last year, to help Readers become Posters, I posted on our forum about getting badges. It sparked some interest and a couple dozen “new” people started posting. It also prompted some scavenger hunts on Discourse to find just how to obtain said badges. For example, it took a group effort to understand just how to make the Tutorial work
Plus, one of the actions in the Tutorial Failed (one of the “undo” actions); it failed to work for everyone who sought that badge.
Now we are discussing the New User of the Month badge; Outstanding contributions in their first month. hmmm…
From the creators’ post, quote:
“It requires 2 posts in 2 different topics
The score is calculated based on the trust level of the person who liked it, not their account age. You can see the table I came up with here22.”Currently in our community, there are only 14 members with this badge. However, all of the 14 were granted AFTER March 2017, and MOST were in the fall after Sept 2017.
YET, I joined Joined May 13, '15. I became a Moderator/Leader Aug '15, '15.
The other 2 moderators/Leaders became Mods/Leaders at the same time and they never got this badge either. The 3 of us were asked to be leaders because we were so active.We have a small core group of regulars who all started in 2015. They are all asking why they have not gotten the badge / how to get the badge.
Can someone explain to me how to get the badge, so I can explain to members and the other mods what to do?
If I may take a moment to comment on other badges, many of the higher default badges seem unattainable, even the 300 one (way too high). Getting more than 7 to 8 likes per post has rarely if ever happened… 10 or more will be a giant stretch. I wish there were more badges for T2 & T3 but at lower amounts (on all those) and set by default.
I also wish that a couple new badges for each level were added each year, to keep it fresh and let people have something to look forward to doing. .
.
.
Unrelated to badges… Why doesn’t everyone get the birthday acknowledgement on “CakeDay”?Thank you.
Posts: 3
Participants: 3
@David_Taylor wrote:
In the rejected email page, clicking on the error of some emails results in a 500 error.
Encoding::UndefinedConversionError ("\x92" from ASCII-8BIT to UTF-8) /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/core_ext/object/json.rb:36:in `encode'backtrace
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/core_ext/object/json.rb:36:in `encode' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/core_ext/object/json.rb:36:in `to_json' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/core_ext/object/json.rb:36:in `to_json' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/json/encoding.rb:55:in `to_json' /usr/local/lib/ruby/2.4.0/json/common.rb:224:in `generate' /usr/local/lib/ruby/2.4.0/json/common.rb:224:in `generate' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/json/encoding.rb:100:in `stringify' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/json/encoding.rb:33:in `encode' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/json/encoding.rb:20:in `encode' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/core_ext/object/json.rb:39:in `to_json' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:333:in `to_json' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/multi_json-1.12.1/lib/multi_json/adapters/oj.rb:21:in `dump' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/multi_json-1.12.1/lib/multi_json/adapters/oj.rb:21:in `dump' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/multi_json-1.12.1/lib/multi_json/adapter.rb:25:in `dump' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/multi_json-1.12.1/lib/multi_json.rb:139:in `dump' /var/www/discourse/app/controllers/application_controller.rb:365:in `render_json_dump' /var/www/discourse/app/controllers/admin/email_controller.rb:115:in `incoming' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/basic_implicit_render.rb:4:in `send_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/abstract_controller/base.rb:186:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/rendering.rb:30:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/abstract_controller/callbacks.rb:20:in `block in process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:131:in `run_callbacks' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/abstract_controller/callbacks.rb:19:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/rescue.rb:20:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/notifications.rb:166:in `block in instrument' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/notifications/instrumenter.rb:21:in `instrument' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/notifications.rb:166:in `instrument' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/instrumentation.rb:30:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/params_wrapper.rb:252:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/railties/controller_runtime.rb:22:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/abstract_controller/base.rb:124:in `process' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionview-5.1.4/lib/action_view/rendering.rb:30:in `process' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-mini-profiler-0.10.7/lib/mini_profiler/profiling_methods.rb:102:in `block in profile_method' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal.rb:189:in `dispatch' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal.rb:253:in `dispatch' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/route_set.rb:49:in `dispatch' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/route_set.rb:31:in `serve' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/mapper.rb:16:in `block in <class:Constraints>' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/mapper.rb:46:in `serve' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/journey/router.rb:50:in `block in serve' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/journey/router.rb:33:in `each' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/journey/router.rb:33:in `serve' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/route_set.rb:834:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-protection-2.0.0/lib/rack/protection/frame_options.rb:31:in `call' /var/www/discourse/lib/middleware/omniauth_bypass_middleware.rb:24:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/conditional_get.rb:25:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/head.rb:12:in `call' /var/www/discourse/lib/middleware/anonymous_cache.rb:149:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/session/abstract/id.rb:232:in `context' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/session/abstract/id.rb:226:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/cookies.rb:613:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/callbacks.rb:26:in `block in call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:97:in `run_callbacks' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/callbacks.rb:24:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/debug_exceptions.rb:59:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/show_exceptions.rb:31:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/logster-1.2.9/lib/logster/middleware/reporter.rb:31:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/rack/logger.rb:36:in `call_app' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/rack/logger.rb:26:in `call' /var/www/discourse/config/initializers/100-quiet_logger.rb:16:in `call' /var/www/discourse/config/initializers/100-silence_logger.rb:29:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/remote_ip.rb:79:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/request_id.rb:25:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/method_override.rb:22:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/executor.rb:12:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/sendfile.rb:111:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-mini-profiler-0.10.7/lib/mini_profiler/profiler.rb:282:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/message_bus-2.1.2/lib/message_bus/rack/middleware.rb:63:in `call' /var/www/discourse/lib/middleware/request_tracker.rb:138:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/engine.rb:522:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/railtie.rb:185:in `public_send' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/railtie.rb:185:in `method_missing' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/urlmap.rb:68:in `block in call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/urlmap.rb:53:in `each' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/urlmap.rb:53:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.4.0/lib/unicorn/http_server.rb:606:in `process_client' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.4.0/lib/unicorn/http_server.rb:701:in `worker_loop' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.4.0/lib/unicorn/http_server.rb:549:in `spawn_missing_workers' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.4.0/lib/unicorn/http_server.rb:142:in `start' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.4.0/bin/unicorn:126:in `<top (required)>' /var/www/discourse/vendor/bundle/ruby/2.4.0/bin/unicorn:23:in `load' /var/www/discourse/vendor/bundle/ruby/2.4.0/bin/unicorn:23:in `<main>'It looks like the presence of a unicode apostrophe in the email body is breaking something
Posts: 2
Participants: 2
@Dax wrote:
I’m not sure if the problem is specific with Linkedin or is also present with other sites, however:
Raw:
https://www.linkedin.com/company/fcagroup (from https://www.linkedin.com/company/fcagroup) https://www.linkedin.com/ (from https://www.linkedin.com/) https://www.linkedin.com/in/kyle-park-254a?trk=org-employees_mini-profile_cta (https://www.linkedin.com/in/kyle-park-254a?trk=org-employees_mini-profile_cta)Results:
https://www.linkedin.com/company/fcagroup
(from )https://www.linkedin.com/
(from https://www.linkedin.com/)https://www.linkedin.com/in/kyle-park-254a?trk=org-employees_mini-profile_cta
()No JS error in the browser console, however the link title is skipped:
![]()
I can repro only here on Meta both on Firefox and Chrome, the other sites are not yet affected by this problem.
Posts: 5
Participants: 4
@savas wrote:
Hello i like your comunity and i desided to run discourse on my hosting but its confused to install it im runing centos eny help?
stuck on
[root@server public_html]# ./discourse-setup which: no docker.io in (/sbin:/bin:/usr/sbin:/usr/bin) which: no docker.io in (/sbin:/bin:/usr/sbin:/usr/bin) Port 80 appears to already be in use. This will show you what command is using port 80 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME httpd 467 root 4u IPv6 616054 0t0 TCP *:http (LISTEN) httpd 472 nobody 4u IPv6 616054 0t0 TCP *:http (LISTEN) httpd 473 nobody 4u IPv6 616054 0t0 TCP *:http (LISTEN) httpd 474 nobody 4u IPv6 616054 0t0 TCP *:http (LISTEN) httpd 13038 nobody 4u IPv6 616054 0t0 TCP *:http (LISTEN) If you are trying to run Discourse simultaneously with another web server like Apache or nginx, you will need to bind to a different port See meta discourse org/t/17247 If you are reconfiguring an already-configured Discourse, use ./launcher stop app
Posts: 11
Participants: 4
@outofthebox wrote:
Hi, is it possible to automatically send an email to new users 24 hours after they join a Discourse forum?
It would be nice to segment this too.
- Welcome email to new users who created an account but nothing else.
- Welcome email to new users who read for five minutes but no more.
- Welcome email to new users who created a new post.
The goal is to increase the conversion rate of new users into active contributors.
Posts: 6
Participants: 3
@SidV wrote:
Hello.
When a user (or a staff’s member) try to post anything on my forum a pop up shows “413 Error”.
Can you help me?
Posts: 5
Participants: 3
@Daquantics wrote:
I am admin for our community and I have a user complaining about harassment from another user. They said they received negative messages and PMs, but could no longer find the messages… They copy-pasted a quote they said they found in an email notification.
At first, I thought this person (the complainant) was confusing email notifications about public threads with private messages, but the interactions between the two users in public didn’t match the forwarded quote, and hadn’t been edited.
Moreover, the quotes didn’t appear in the “accused” user’s deleted posts, nor in their private messages (sent, archived, inbox).
So, I’m confused. Is it possible for users to send Private Messages, then delete them in a way that Admins can no longer see them?
I know there is no block function for the complainant to use, but before we have a word with the “accused” guy, I wanted to see the actual messages… I’ve asked the complainant to forward me the emails, but some clarification would be great.
Thanks!
Posts: 8
Participants: 5
@supermathie wrote:
When we have a CDN defined, we should be leveraging that for various image assets (e.g.
logo url,logo small url) that are relative URLse.g.:
logo_url='/uploads/default/original/1X/5b5cc13aa92459bb084ca1485bca80c480bfa6f0.gif'
Posts: 1
Participants: 1
@jerdog wrote:
So having some issues in backing up to S3 - I have put in my s3 credentials (it’s a private bucket) and each time I backup I get the following error:
[2018-01-29 21:41:45] Executing the after_create_hook for the backup... [2018-01-29 21:41:45] EXCEPTION: Access Denied [2018-01-29 21:41:45] /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/aws-sdk-core-3.6.0/lib/seahorse/client/plugins/raise_response_errors.rb:15:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/aws-sdk-s3-1.4.0/lib/aws-sdk-s3/plugins/sse_cpk.rb:22:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/aws-sdk-s3-1.4.0/lib/aws-sdk-s3/plugins/dualstack.rb:26:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/aws-sdk-s3-1.4.0/lib/aws-sdk-s3/plugins/accelerate.rb:35:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/aws-sdk-core-3.6.0/lib/aws-sdk-core/plugins/jsonvalue_converter.rb:20:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/aws-sdk-core-3.6.0/lib/aws-sdk-core/plugins/idempotency_token.rb:17:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/aws-sdk-core-3.6.0/lib/aws-sdk-core/plugins/param_converter.rb:24:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/aws-sdk-core-3.6.0/lib/aws-sdk-core/plugins/response_paging.rb:10:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/aws-sdk-core-3.6.0/lib/seahorse/client/plugins/response_target.rb:23:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/aws-sdk-core-3.6.0/lib/seahorse/client/request.rb:70:in `send_request' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/aws-sdk-s3-1.4.0/lib/aws-sdk-s3/client.rb:849:in `create_multipart_upload' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/aws-sdk-s3-1.4.0/lib/aws-sdk-s3/multipart_file_uploader.rb:52:in `initiate_upload' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/aws-sdk-s3-1.4.0/lib/aws-sdk-s3/multipart_file_uploader.rb:43:in `upload' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/aws-sdk-s3-1.4.0/lib/aws-sdk-s3/file_uploader.rb:32:in `upload' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/aws-sdk-s3-1.4.0/lib/aws-sdk-s3/customizations/object.rb:252:in `upload_file' /var/www/discourse/lib/s3_helper.rb:28:in `upload' /var/www/discourse/app/models/backup.rb:55:in `block in upload_to_s3' /var/www/discourse/app/models/backup.rb:54:in `open' /var/www/discourse/app/models/backup.rb:54:in `upload_to_s3' /var/www/discourse/app/models/backup.rb:33:in `after_create_hook' /var/www/discourse/lib/backup_restore/backuper.rb:250:in `after_create_hook' /var/www/discourse/lib/backup_restore/backuper.rb:44:in `run' /var/www/discourse/lib/backup_restore/backup_restore.rb:167:in `block in start!' /var/www/discourse/lib/backup_restore/backup_restore.rb:164:in `fork' /var/www/discourse/lib/backup_restore/backup_restore.rb:164:in `start!' /var/www/discourse/lib/backup_restore/backup_restore.rb:18:in `backup!' /var/www/discourse/app/controllers/admin/backups_controller.rb:32:in `create' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/basic_implicit_render.rb:4:in `send_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/abstract_controller/base.rb:186:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/rendering.rb:30:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/abstract_controller/callbacks.rb:20:in `block in process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:131:in `run_callbacks' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/abstract_controller/callbacks.rb:19:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/rescue.rb:20:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/notifications.rb:166:in `block in instrument' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/notifications/instrumenter.rb:21:in `instrument' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/notifications.rb:166:in `instrument' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/instrumentation.rb:30:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/params_wrapper.rb:252:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/railties/controller_runtime.rb:22:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/abstract_controller/base.rb:124:in `process' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionview-5.1.4/lib/action_view/rendering.rb:30:in `process' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-mini-profiler-0.10.7/lib/mini_profiler/profiling_methods.rb:76:in `block in profile_method' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal.rb:189:in `dispatch' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal.rb:253:in `dispatch' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/route_set.rb:49:in `dispatch' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/route_set.rb:31:in `serve' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/mapper.rb:16:in `block in <class:Constraints>' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/mapper.rb:46:in `serve' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/journey/router.rb:50:in `block in serve' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/journey/router.rb:33:in `each' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/journey/router.rb:33:in `serve' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/route_set.rb:834:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-protection-2.0.0/lib/rack/protection/frame_options.rb:31:in `call' /var/www/discourse/lib/middleware/omniauth_bypass_middleware.rb:24:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/conditional_get.rb:38:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/head.rb:12:in `call' /var/www/discourse/lib/middleware/anonymous_cache.rb:149:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/session/abstract/id.rb:232:in `context' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/session/abstract/id.rb:226:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/cookies.rb:613:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/callbacks.rb:26:in `block in call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:97:in `run_callbacks' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/callbacks.rb:24:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/debug_exceptions.rb:59:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/show_exceptions.rb:31:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/logster-1.2.9/lib/logster/middleware/reporter.rb:31:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/rack/logger.rb:36:in `call_app' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/rack/logger.rb:26:in `call' /var/www/discourse/config/initializers/100-quiet_logger.rb:16:in `call' /var/www/discourse/config/initializers/100-silence_logger.rb:29:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/remote_ip.rb:79:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/request_id.rb:25:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/method_override.rb:22:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/executor.rb:12:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/sendfile.rb:111:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-mini-profiler-0.10.7/lib/mini_profiler/profiler.rb:171:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/message_bus-2.1.2/lib/message_bus/rack/middleware.rb:63:in `call' /var/www/discourse/lib/middleware/request_tracker.rb:138:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/engine.rb:522:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/railtie.rb:185:in `public_send' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/railtie.rb:185:in `method_missing' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/urlmap.rb:68:in `block in call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/urlmap.rb:53:in `each' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/urlmap.rb:53:in `call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.4.0/lib/unicorn/http_server.rb:606:in `process_client' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.4.0/lib/unicorn/http_server.rb:701:in `worker_loop' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.4.0/lib/unicorn/http_server.rb:549:in `spawn_missing_workers' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.4.0/lib/unicorn/http_server.rb:142:in `start' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.4.0/bin/unicorn:126:in `<top (required)>' /var/www/discourse/vendor/bundle/ruby/2.4.0/bin/unicorn:23:in `load' /var/www/discourse/vendor/bundle/ruby/2.4.0/bin/unicorn:23:in `<main>' Notifying '' of the end of the backup... [2018-01-29 21:41:51] Removing old backups...It is saying “access denied” but seeing as I am giving it the correct credentials I am at a loss.
Posts: 3
Participants: 3
@supermathie wrote:
Two things here:
- the anonymous user tries to clear the pin but fails (it shouldn’t even try?)
- the content jumps around (CSS problem?)
Posts: 1
Participants: 1
@RobMeade wrote:
Hi,
I thought I read that once a topic was closed, the votes cast by users are returned to them.
Are there any exceptions to this? For example, if a topic was marked as “Solved” and then was automatically closed, could this leave votes behind?
The reason I ask is that we seem to have exactly that, topics which are closed, which have votes remaining and the only commonality that I can see at the moment is that these topics were marked as solved and subsequently automatically closed.
We have a hosted solution, so if links to the topics in question is of use, please let me know.
Any help would be appreciated.
Posts: 1
Participants: 1
@fredkgb wrote:
My VPS have 10gb. It’s a fresh 16.04 Ubuntu install. I followed this tutorial : discourse/INSTALL-cloud.md at master · discourse/discourse · GitHub
I got this message after doing the ./discourse-setup command.
You have less than 5GB of free space on the disk where /var/lib/docker is located. You will need more space to continue
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 9.7G 5.1G 4.6G 54% /I tried the command for cleaning docker images. But I still goot this message. I assume I could upgrade my VPS space. But wow. 10gb is not enough really? … Is there any other way to solve this?
Posts: 3
Participants: 2
@Ryan_Collins1 wrote:
Hi team,
I have a wordpress website that I connected via SSO to my Discourse forum.
I am currently writing a reply within my Discourse forum and I want to tag a user from my wordpress website, but the user is not showing up when I type @
My guess is this wordpress user has never visited my Discourse forum, which is why they don’t show up when I type @
Is there any way I can mention this user in my post?
I know the user would love to get involved in this particular forum conversation. I just need to figure out how I can ping them with some sort of notification.
Thanks for any advice
Posts: 6
Participants: 3
@fredkgb wrote:
Following this tutorial discourse/INSTALL-cloud.md at master · discourse/discourse · GitHub
I dont have a domain name. Just a VPS hosted in the cloud with and ip adresse.
As an hostname, can I enter the IP adress during the setup?
Posts: 2
Participants: 2
@infered5 wrote:
Every time I try to connect through PuTTy to my DigitalOcean Ubuntu 16.04 x64 droplet to connect to the terminal, it prompts me, in a way I cannot escape, to reinstall Discourse. Since it’s all installed nothing happens and my settings and users are all there, but it’s very annoying and eating up processing power.
It’s the same prompt as the initial startup when you choose the preconfigured Discourse droplet on DigitalOcean. It prompts the email address to use, username and password, mail server API key, etc etc. How do I disable this?
Posts: 5
Participants: 3
@DaBeast_45 wrote:
Can mod’s lock your trust level and how? Can you show me step by step? Pictures included?
Posts: 2
Participants: 2
Plus, one of the actions in the Tutorial Failed (one of the “undo” actions); it failed to work for everyone who sought that badge.
