@SimeonGriggs wrote:

If I add one user to a group, it effects their trust level as intended.

If I bulk add users to a group it does not.

Bug or feature?

Posts: 3

Participants: 3

Read full topic

@Celil wrote:

Hello, I got the error below in logs http://forum.medikalbulut.org/logs/. How can I solve it? Thank you.

Message

(google_oauth2) Authentication failure! csrf_detected: OmniAuth::Strategies::OAuth2::CallbackError, csrf_detected | CSRF detected

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:507:in `error'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:158:in `log'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:474:in `fail!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-oauth2-1.3.1/lib/omniauth/strategies/oauth2.rb:75:in `callback_phase'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:227:in `callback_call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:184:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/builder.rb:63:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/conditionalget.rb:25:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/head.rb:13:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:138:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/flash.rb:260:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/session/abstract/id.rb:225:in `context'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/session/abstract/id.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/cookies.rb:560:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/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.7.1/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:88:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:778:in `_run_call_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/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.7.1/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/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.7.1/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/methodoverride.rb:22:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/runtime.rb:18:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/sendfile.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/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.7.1/lib/rails/engine.rb:518:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/application.rb:165:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/railtie.rb:194:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/urlmap.rb:66:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/urlmap.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/urlmap.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/lib/unicorn/http_server.rb:562: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.2.0/lib/unicorn/http_server.rb:658:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/lib/unicorn/http_server.rb:508:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/lib/unicorn/http_server.rb:519:in `maintain_worker_count'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/lib/unicorn/http_server.rb:283:in `join'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.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

hostname	discourse-2gb-fra1-01-medikalbulut-app
process_id	12035
application_version	a6ebe495bf5916b9d9ff6c475c6838065d0cdb1a
HTTP_HOST	forum.medikalbulut.org
REQUEST_URI	/auth/google_oauth2/callback?state=09b9e9c7ca8dd63d7dcee1824a49a1a73f3c442f7828b806&code=4/-vRn0TipuvnrB2agHPT2XfNE4PIbo1A4mvwmg35iRKQ
REQUEST_METHOD	GET
HTTP_USER_AGENT	Mozilla/5.0 (Linux; Android 6.0.1; SM-G925F Build/MMB29K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Mobile Safari/537.36
HTTP_ACCEPT	text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
HTTP_REFERER	http://forum.medikalbulut.org/t/biyomedikalciler-whatsapp-grubunda-paylasim-icin-saat-sinirlamasi-olsun-mu/318
HTTP_X_FORWARDED_FOR	46.104.52.17
HTTP_X_REAL_IP	46.104.52.17
params
state	09b9e9c7ca8dd63d7dcee1824a49a1a73f3c442f7828b806
code	4/-vRn0TipuvnrB2agHPT2XfNE4PIbo1A4mvwmg35iRKQ

Posts: 2

Participants: 2

Read full topic

@mikechristopher wrote:

Hi,
on and off we are getting errors as per title and image below when Zapier is running an invite via the api - for example the one below ran at 12:07 where as the one before that 17 mins earlier went through ok but this one did not.

I have checked the /logs page and there are no logs coming up at all strangely. I cleared the logs - tried to re-run it and still nothing.

Nothing has changed in the API call all Zapier does is capture the email address out of the mailchimp list and adds it in and then sends it into the API in order to send an invite out to them for the forum.

I have edited out the username and api key and part of the email address - I have checked the email address and it is valid - I have also had the issue with outlook.com email addresses and gmail ones too etc.

Its very odd as two more have gone through since!

error.JPG850x778 37.2 KB

Posts: 1

Participants: 1

Read full topic

@tophee wrote:

Just like it makes sense to distinguish between different types of badges, there should also be different types of groups (in badges, it's called "groups" so I guess I'm talking about "group groups"). Is this something that's already on someone's to-do list?

To be more specific: groups can be based on all kinds of criteria, e.g. geographic location, occupation, special interest etc so it would make sense to list them on the /groups page according to those criteria, right? I would even wish to have separate groups pages for each group group à la /groups/country. (BTW: that would be a nice feature for the badges too: /badges/community, /badges/posting, etc)

Posts: 4

Participants: 3

Read full topic

@huynhthai824 wrote:

How i merge or only select 1 column template for post new a topic? same wordpress, Stack Overfollow or > https://www.digitalocean.com/community/questions/new

Can who tech me design by hand or install a plugin to simple post not HTML code visual ?

so.PNG890x508 13.8 KB

dg.PNG656x620 19.2 KB

Posts: 9

Participants: 3

Read full topic

@LeoMcA wrote:

Currently when using d/sidekiq to run sidekiq in the docker dev image, it starts a sidekiq process only for the critical queue.

The problem line is:

When I change sidekiq -q critical,low,default to sidekiq -q default,critical,low it starts a process only for the default queue, so there's something wrong with the commas.

The workaround I'm using is just removing -q critical,low,default in its entirety, which starts a process servicing every queue.

Posts: 6

Participants: 2

Read full topic

@happybeing wrote:

On mobile, whenever I post a reply, the topic is resumed some way back and my new post is out of view. If I don't then manually scroll it back into view, it remains unread, which is annoying!

Edit: I'm pretty sure this started happening when we upgraded and the new scroll mechanism was introduced. (Which even after months of use I still hate - previous was clunky but much better than this "click to reveal a painful scroll bar" thingy. I preferred typing in a post number).

System: Latest Firefox on Android

Not sure which Discourse version, but we're on your hosting I believe: https://safenetforum.org/t/post-reply-scrolls-thread-backwards/12633?u=happybeing

Posts: 1

Participants: 1

Read full topic

@pmusaraj wrote:

Following up on the discussion here, I have successfully set up a fork of the official Discourse app that can send push notifications via the OneSignal API.

There are two parts to this:
discourse-onesignal - a Discourse plugin that sends Push Notifications to OneSignal's REST API

https://github.com/pmusaraj/discourse-onesignal/

and a DiscourseMobile fork - which is used to build the app
https://github.com/pmusaraj/DiscourseMobile

For now the app works only on iOS. Android version should be coming soon.

Instructions for setting this up for your own app:

1. Register an App ID on the Apple portal (developer.apple.com)
2. Open an account with OneSignal (free), create a new app, and generate certificates for iOS using the OneSignal provisionator (or generate certs on the Apple portal)
3. Create the provisioning profiles on the Apple portal. You need a distribution profile for pushing to TestFlight and the App Store, and likely an ad-hoc profile for testing quickly on your device. (Note that you may also need a development certificate for testing the app on your device. Step 2 above creates only the production certificate.)
4. Create an iCloud container and associate it with your App ID.
5. Checkout Discourse-Mobile locally, and get started using the steps described here: https://github.com/pmusaraj/DiscourseMobile
6. Edit global.js to set your app's configuration variables: the site domain, the app name, the OneSignal App ID and the URL scheme (optional).
7. Make sure you have Node installed, and run node setup.ios.js from your command line. This will use the variables set in globaj.js to update the app files.
8. You can now open XCode, open Discourse.xcodeproj and update your Bundle identifier and your Provisionin profiles.
9. Now, jump over to your Discourse instance. a) make sure you are running your site on https. The OneSignal plugin does not support http at this point.
10. Add the discourse-onesignal plugin to your Discourse instance and configure it: enable notifications, add your OneSignal App ID and the OneSignal REST API key.
11. You should now be ready to build and test the app in Xcode our using react-native run-ios on the command line. (To test push notifications, you need to set up your app on your phone, either via ad-hoc or through TestFlight.)

If anybody is interested in testing this using a demo Discourse instance, I have a demo site set up at white.saloncms.ca. Please respond below with your email address so I can add you to the list of testers for the app.

Upcoming improvements:

• the home screen of the app needs to be improved a little bit. the official Discourse app accepts connections to multiple sites. The whitelisted app is geared towards a single site. So that home screen is a little raw and empty. I'm working on a better UI for it. (PRs and suggestions welcome.)

Posts: 1

Participants: 1

Read full topic

@SwisherSweet wrote:

Google supports structured data, including a forum data type it seems:

http://schema.org/DiscussionForumPosting

I've seen other forums show up in Google search results with comment count, author count, and other structured data.

Does Discourse support this and if not, is it on the roadmap?

Thanks.

Posts: 3

Participants: 2

Read full topic

@trudat wrote:

I have set up WP-Discourse according to the instructions, with WP and Discourse on separate hosts.

Issue

I have activated the 'Publish all new posts to Discourse' setting, but when I visit posts, the 'Publish post to Discourse' checkbox is unchecked, and no discourse topic has been created. On the front-end, there is no comment-related message, it's empty.

Workaround

In order to get a single post to work, I need to manually check 'Publish post to Discourse' and check 'Allow comments' on the post. Once I check those two and update the page, then the topic is created on discourse (see my connection is fine) and the message "Discuss this post at forum.mysite.com" appears on the bottom of the post.
This is the desired behavior, but I want it to happen for all posts at the time of publishing.

Questions

• What settings should be set in Settings > Discussion ? Current settings:
  
• If I have 'Publish all new posts to Discourse' checked and it's not working, how can I debug this feature? Should I be looking for anything in particular in WP or Discourse logs?
• Can't it just work? Why does life have to be so hard? Is it because I am a sinner?

Possibly related topic

Posts: 10

Participants: 2

Read full topic

@tophee wrote:

I edited discourse_narrative_bot.timeout.message under admin/customize/site_texts and thought that was a straight forward and simple job, but either I did something wrong or there is a bug because the discobot no longer displays its timeout message but says instead translation missing: en.discourse_narrative_bot.timeout.message

If this is not a bug, my interpretation is that it is not really missing a translation (since I'm using only one locale and that is the english one) but that it does not recognize the text I edited as legitimate for some reason. Is there something else I need to do to get this working? There are no special characters in my text except for %{site_name}, a link, a dash, two ", two **

When I revert back to the default message text, it works again. Is there a character limit or something, @tgxworld?

Posts: 1

Participants: 1

Read full topic

@tophee wrote:

I would like to add a direct link to the users activity page to the user dropdown menu, either as an icon:

Or as text.

How do I do it?

Posts: 1

Participants: 1

Read full topic

@tophee wrote:

I'm not sure if this is related but it looks like I'm still having issues. I just had another "500 internal server error" and got this error in the logs:

ActionView::Template::Error (Discourse::InvalidAccess)
/var/www/discourse/lib/auth/default_current_user_provider.rb:67:in `rescue in current_user'

Backtrace:

/var/www/discourse/lib/auth/default_current_user_provider.rb:67:in `rescue in current_user'
/var/www/discourse/lib/auth/default_current_user_provider.rb:64:in `current_user'
/var/www/discourse/lib/current_user.rb:34:in `current_user'
/var/www/discourse/app/helpers/application_helper.rb:71:in `html_classes'
/var/www/discourse/app/views/layouts/application.html.erb:2:in `_app_views_layouts_application_html_erb__4368751605286005619_70046462450740'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/template.rb:145:in `block in render'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/notifications.rb:166:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/template.rb:333:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/template.rb:143:in `render'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/lib/mini_profiler/profiling_methods.rb:76:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/renderer/template_renderer.rb:66:in `render_with_layout'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/renderer/template_renderer.rb:52:in `render_template'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/renderer/template_renderer.rb:14:in `render'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/renderer/renderer.rb:46:in `render_template'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/renderer/renderer.rb:27:in `render'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/rendering.rb:100:in `_render_template'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/streaming.rb:217:in `_render_template'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/rendering.rb:83:in `render_to_body'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rendering.rb:32:in `render_to_body'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/renderers.rb:37:in `render_to_body'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/abstract_controller/rendering.rb:43:in `render_to_string'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rendering.rb:21:in `render_to_string'
/var/www/discourse/app/controllers/application_controller.rb:549:in `build_not_found_page'
/var/www/discourse/app/controllers/application_controller.rb:158:in `rescue_discourse_actions'
/var/www/discourse/app/controllers/application_controller.rb:141:in `block in <class:ApplicationController>'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/rescuable.rb:112:in `instance_exec'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/rescuable.rb:112:in `block in handler_for_rescue'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/rescuable.rb:80:in `rescue_with_handler'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rescue.rb:15:in `rescue_with_handler'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rescue.rb:32:in `rescue in process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/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.7.1/lib/active_support/notifications.rb:164:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/notifications.rb:164:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/abstract_controller/base.rb:137:in `process'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/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.7.1/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal.rb:237:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/routing/route_set.rb:74:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/routing/route_set.rb:43:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/journey/router.rb:43:in `block in serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/journey/router.rb:30:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/journey/router.rb:30:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/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.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/builder.rb:63:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/conditionalget.rb:38:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/head.rb:13:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:138:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/flash.rb:260:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/session/abstract/id.rb:225:in `context'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/session/abstract/id.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/cookies.rb:560:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/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.7.1/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:88:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:778:in `_run_call_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/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.7.1/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/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.7.1/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/methodoverride.rb:22:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/runtime.rb:18:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/sendfile.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/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.7.1/lib/rails/engine.rb:518:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/application.rb:165:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/railtie.rb:194:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/urlmap.rb:66:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/urlmap.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/urlmap.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/lib/unicorn/http_server.rb:562: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.2.0/lib/unicorn/http_server.rb:658:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/lib/unicorn/http_server.rb:508:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/lib/unicorn/http_server.rb:132:in `start'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.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>'

Posts: 7

Participants: 3

Read full topic

@jomaxro wrote:

Requests for admins to be able to add links to the topnav come up reasonably often here on Meta.

There's this one:

There's also this one, with discussion spanning 3 years!

Back in 2015, Jeff said:

Sam responded:

At the moment, the solution for this issue seems to be adding custom JS to the </body>. While this works, it's not exactly user friendly (you need a basic JS understanding to add or change links), and could break at any time with a code change to Discourse.

I'd like to suggest the following 3-stage rollout:

1. Provide a site setting for admins to add external links to the topnav. The site setting will need 3 values, I propose a comma separated list. title,tooltip,URL
2. Provide a site setting for admins to add internal links to the topnav - without handling breadcrumbs.
3. Improvinate #2 by handling certain cases where breadcrumbs make sense, like Tags, Users, Groups, Badges, etc.

The benefit to the 3-stage rollout is that external links require no routing by Discourse, nor breadcrumb support. They should simply be an href. Keeping steps 2 & 3 separate will allow for complaint driven development. Roll-out internal link support, see if there are complaints about the lack of breadcrumbs. Meta already has 2 internal links without breadcrumb support, and I've never seen a complaint.

Posts: 5

Participants: 2

Read full topic

@jomaxro wrote:

In order to target a user's title with CSS, they must have an assigned primary group. Once assigned a primary group, their title links to the group per

This is great if the user's title is related to the group - however, if the only reason for the primary group is to allow CSS targeting, the link is unwanted.

This is currently handled using JS:

<script>
$(document).on("ajaxComplete", function( event ) {
    $('a.user-group').each(function() {
        $(this).replaceWith("<div class='user-group'>" + $(this).html() + "</div>" );
    });
});
</script>

However, JS can be broken with any Discourse update. I'd like to see a new group setting to disable linking the title to a group.

Posts: 1

Participants: 1

Read full topic

@tophee wrote:

By default, the system user has no_mailas it's email address. I would like to change this to a real email address to make sure if users PM system, someone receives those messages.

So I impersonated system and went to user preferences to change the email address. After I entered the new email address, it stated something like "Sending confirmation email to this address". However, from the email log (and from Sparkpost's error log) I can see that it actually tried to send those emails to no_mail. Shouldn't it be sent to the new email address? At least it is saying that.

Posts: 4

Participants: 2

Read full topic

@tolkin wrote:

Hey there Discourse Team!

I would like to know if there is an option to change the Titles & Descriptions of categories and subcategories.
For example, if I go inside Bug section the title will be "Latest Bug Topics" and the same will happen in support etcetera.

I have read an older thread saying that this was not available but that was Oct 2015.

The value behind this is simple.

Meta Titles & Descriptions are not just valuable for rankings (description actually is not a ranking factor at all) but it gives you the chance of getting a better CTR by having something more optimized.

Regards!

Posts: 4

Participants: 2

Read full topic

@Pad_Pors wrote:

as an admin, the only place in the latest topic list that I can use to tell something more important to users, is the top of the list. where I can pin topics or use banners.

usually users want to discover what exists for them, and so in the first glance they try not to click on any topic and scroll down to see more.

as a result the admin lose its chance to be seen again, unless if they have got clicks in the beginning.

the feature request: some predicted positions inside the topic list where admin can use to show the highlights every while as users scroll down. for example every 20 topics admin can add some topics that are highlighted or pinned.

I tried to make a mock up, but my imagination and visualization is not good at all . excuse me for the bad redrawing!

topic list with extras.png1232x692 74.3 KB

Posts: 1

Participants: 1

Read full topic

@SimeonGriggs wrote:

Again not sure if this is a bug or a feature.

As an admin I cannot seem to edit a user's email address or trigger a password reset. Unless I enter 'impersonate'.

However if you:
- Edit Username
- Enter same username user already has

It brings up a version of the page where I can trigger an email change and password reset.

Why can't I do this without editing the username first?

Posts: 2

Participants: 2

Read full topic

@caub wrote:

image.png632x542 29.3 KB

Nothing more is shown when scrolling to the right, so an element is probably triggering the horizontal scroll bar for some reason

The topic-footer-button element does it after inspecting

topic-closing-info too, both should have max-width:100%

(Just showing discuss.react for example, I've the same issue on my site)

Posts: 3

Participants: 3

Read full topic