@vikaskedia wrote:

I am using the latest docker version of Discourse.

I have tried uploading the profile image multiple times and it still does not show up.

Please see this video demo:

Posts: 9

Participants: 4

Read full topic

@vikaskedia wrote:

When discourse sees a webm file it is smart to understand that it is a video and uses a video tag.

But when the webm file has a media fragment as part of the URL .. discourse gets confused.

Posts: 1

Participants: 1

Read full topic

@jomaxro wrote:

I've been tasked at work with updating a Discourse instance we have that has been sitting at version 1.0.1 since...well...whenever v1.0.1 was released.

Side note: It's so strange to see how Discourse used to look...

Anyway, over the next few days, I'm going to be working to get it up to date. I'm assuming I'll need to use the console to rebuild, not Docker Manager, but other than that anything I should be looking out for? I only started working with Discourse at 1.5, so I won't have read anything about Discourse prior to that.

Posts: 15

Participants: 4

Read full topic

@dmitry_fedyuk wrote:

04.png884x168 11.9 KB

This works

This does not work

I have checked, the letters are the same, not a Unicode trick from another alphabet.

Posts: 1

Participants: 1

Read full topic

@Stranik wrote:

1. There is a discussion that implies accurate enough answers. These answers have already been represented at website, let's say in another branch. How can an administration make an insert with a text immediately after the first post? In this box, the administration can write an arbitrary text, where could be indicated a link to the already prepared answers. I understand that the administration can publish a response with these links at any time or even close the discussion. But it is a kind of unobtrusive recommendation, as a separate independent block, a more correct solution.

2. What could be, to your mind, the system of recommendations at the website? The number of tags coulb be huge, as well as the number of categories. How dcan I recommend categories, tags to users and that invite them to subscribtion?

I really like Discourse, but I'm looking for the possibility of working with a big amount of users by means of this engine

Posts: 2

Participants: 2

Read full topic

@David_James_Ball wrote:

Hi - I've removed avatars from my theme because it will be a private and anonymous forum. On mobile, however, the username does not align/anchor to the left. Can anyone help?

IMG_0481.PNG730x509 42.1 KB

Posts: 2

Participants: 2

Read full topic

@David_James_Ball wrote:

Hi, I've removed the timeline from my theme but the post and reply boxes in the material theme do not fill 100% width. How can I make them fill it?

Screen Shot 2017-06-06 at 6.47.55 pm.png2334x779 78.1 KB

Posts: 5

Participants: 3

Read full topic

@jlippiner wrote:

I'm currently running an invite only discourse forum, which is great. I have a separate google form setup for people to apply to the forum. What I'd like to do is combine these so people can apply for access directly through discourse and I can review and approve them.

Is there anyway to do this?

Posts: 10

Participants: 3

Read full topic

@meldsza wrote:

I need a way to add a donator badge to users by querying a custom api. How can i make this a possibility?
Can i use sso to set badges?

Posts: 4

Participants: 2

Read full topic

@xiasummer wrote:

Hi,

Because most people won't change their "Avatar", if we allow number starting user names, there will be very few "Avatars". So I force the users to use English Character Starting Names.

How can I remind people to use English Names before they apply for a new account?

Yours.

Posts: 1

Participants: 1

Read full topic

@MikesCafe wrote:

Opening admin or settings through right click/new tab or /new window the header does'ttake on the code written in the custom header and therefore turns white.
Is this a bug or something I have done wrong in CSS/HTML?

Posts: 4

Participants: 2

Read full topic

@pfaffman wrote:

Continuing the discussion from Customize subject format for standard emails:

I just had a client as for this too.

Posts: 1

Participants: 1

Read full topic

@needhelp wrote:

Hi All

I see in my Admin section under SPAM category the "no follow" tag is already checked. However when I do view source I do not see nofollow tags in the forum for posts created by Admin.

It appears that the nofollow tags will be not be applied to posts created by Admin, is this correct?

Is there a way to also apply nofollow tags to posts created by Admin?

Thanks

Below is the description for the rel nofollow check box selection in Admin:

"add rel nofollow to user content
_ Add rel nofollow to 'all submitted user content, except for internal links (including parent domains). If you change this, you must rebake all posts with: "rake posts:rebake"_

Posts: 1

Participants: 1

Read full topic

@Nhanderu wrote:

Hello, guys!

I am trying to run Discourse (with discourse_docker) as a "web only" container, with separated Redis and PostgreSQL services. The latter is running with AWS RDS while, for the former, I will use AWS Elasticache, but I am currently running it on my computer (on the host, not inside a container).

The problem

After executing ./launcher bootstrap app, I received the following message:

FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 187 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'"]}
19a40972edaa2d70f5a58c2748591b7cd1cd0d6b15c50072977a17453a8dcf4b
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one

I have found some messages that could represent the cause of the error, but I know neither their meaning, nor how to fix them.

• Error during bundle install

Bundler::HTTPError: Net::HTTPTooManyRequests: <html>
<head><title>429 Too Many Requests</title></head>
<body bgcolor="white">
<center><h1>429 Too Many Requests</h1></center>
<hr><center>nginx</center>
</body>
</html>

/usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/fetcher/downloader.rb:36:in `fetch'
  /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/fetcher/compact_index.rb:116:in `call'
  /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/compact_index_client/updater.rb:43:in `block in update'
  /usr/local/lib/ruby/2.4.0/tmpdir.rb:89:in `mktmpdir'
  /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/compact_index_client/updater.rb:30:in `update'
  /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/compact_index_client.rb:81:in `update'
  /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/compact_index_client.rb:97:in `update_info'
  /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/compact_index_client.rb:54:in `block in dependencies'
  /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/fetcher/compact_index.rb:87:in `block (3 levels) in compact_index_client'
  /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/worker.rb:63:in `apply_func'
  /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/worker.rb:58:in `block in process_queue'
  /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/worker.rb:55:in `loop'
  /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/worker.rb:55:in `process_queue'
  /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/worker.rb:89:in `block (2 levels) in create_threads'
Query List: ["rake", "msgpack", "bootsnap", "i18n", "minitest", "thread_safe", "tzinfo", "activesupport", "builder", "erubis", "mini_portile2", "nokogiri", "rails-deprecated_sanitizer", "rails-dom-testing", "loofah", "rails-html-sanitizer", "actionview", "rack", "rack-test", "actionpack", "globalid", "activejob", "mime-types", "mail", "actionmailer", "activemodel", "arel", "activerecord", "thor", "railties", "concurrent-ruby", "sprockets", "sprockets-rails", "rails", "seed-fu", "hiredis", "redis", "redis-namespace", "active_model_serializers", "fast_blank", "htmlentities", "moneta", "multi_json", "mustache", "crass", "nokogumbo", "sanitize", "onebox", "http_accept_language", "ember-source", "ember-data-source", "execjs", "barber", "ember-handlebars-template", "jquery-rails", "ember-rails", "babel-source", "babel-transpiler", "message_bus", "rails_multisite", "fast_xs", "rake-compiler", "fast_xor", "fastimage", "jmespath", "aws-sdk-core", "aws-sdk-resources", "aws-sdk", "excon", "unf_ext", "unf", "email_reply_trimmer", "exifr", "fspath", "image_size", "in_threads", "progress", "discourse_image_optim", "hashie", "omniauth", "ruby-openid", "rack-openid", "omniauth-openid", "openid-redis-store", "multipart-post", "faraday", "jwt", "multi_xml", "oauth2", "omniauth-oauth2", "omniauth-facebook", "oauth", "omniauth-oauth", "omniauth-twitter", "omniauth-instagram", "omniauth-github-discourse", "omniauth-google-oauth2", "oj", "pg", "coderay", "method_source", "slop", "pry", "pry-rails", "r2", "domain_name", "http-cookie", "netrc", "rest-client", "rinku", "connection_pool", "rack-protection", "sidekiq", "tilt", "sinatra", "libv8", "mini_racer", "highline", "uglifier", "rtlit", "public_suffix", "addressable", "safe_yaml", "crack", "hashdiff", "webmock", "fakeweb", "timecop", "test_after_commit", "rspec-support", "rspec-core", "diff-lcs", "rspec-expectations", "rspec-mocks", "rspec", "mock_redis", "rb-fsevent", "ffi", "rb-inotify", "ruby_dep", "listen", "certified", "fabrication", "discourse-qunit-rails", "metaclass", "mocha", "rspec-rails", "shoulda-context", "shoulda-matchers", "shoulda", "rspec-html-matchers", "spork", "spork-rails", "pry-nav", "byebug", "lru_redux", "flamegraph", "rack-mini-profiler", "kgio", "raindrops", "unicorn", "puma", "trollop", "rbtrace", "gc_tracer", "guess_html_encoding", "ruby-readability", "simple-rss", "stackprof", "memory_profiler", "rmmseg-cpp", "logster", "sass", "sassc"]
Query Gemcutter Dependency Endpoint API: rake,msgpack,bootsnap,i18n,minitest,thread_safe,tzinfo,activesupport,builder,erubis,mini_portile2,nokogiri,rails-deprecated_sanitizer,rails-dom-testing,loofah,rails-html-sanitizer,actionview,rack,rack-test,actionpack,globalid,activejob,mime-types,mail,actionmailer,activemodel,arel,activerecord,thor,railties,concurrent-ruby,sprockets,sprockets-rails,rails,seed-fu,hiredis,redis,redis-namespace,active_model_serializers,fast_blank,htmlentities,moneta,multi_json,mustache,crass,nokogumbo,sanitize,onebox,http_accept_language,ember-source,ember-data-source,execjs,barber,ember-handlebars-template,jquery-rails,ember-rails,babel-source,babel-transpiler,message_bus,rails_multisite,fast_xs,rake-compiler,fast_xor,fastimage,jmespath,aws-sdk-core,aws-sdk-resources,aws-sdk,excon,unf_ext,unf,email_reply_trimmer,exifr,fspath,image_size,in_threads,progress,discourse_image_optim,hashie,omniauth,ruby-openid,rack-openid,omniauth-openid,openid-redis-store,multipart-post,faraday,jwt,multi_xml,oauth2,omniauth-oauth2,omniauth-facebook,oauth,omniauth-oauth,omniauth-twitter,omniauth-instagram,omniauth-github-discourse,omniauth-google-oauth2,oj,pg,coderay,method_source,slop,pry,pry-rails,r2,domain_name,http-cookie,netrc,rest-client,rinku,connection_pool,rack-protection,sidekiq,tilt,sinatra,libv8,mini_racer,highline,uglifier,rtlit,public_suffix,addressable,safe_yaml,crack,hashdiff,webmock,fakeweb,timecop,test_after_commit,rspec-support,rspec-core,diff-lcs,rspec-expectations,rspec-mocks,rspec,mock_redis,rb-fsevent,ffi,rb-inotify,ruby_dep,listen,certified,fabrication,discourse-qunit-rails,metaclass,mocha,rspec-rails,shoulda-context,shoulda-matchers,shoulda,rspec-html-matchers,spork,spork-rails,pry-nav,byebug,lru_redux,flamegraph,rack-mini-profiler,kgio,raindrops,unicorn,puma,trollop,rbtrace,gc_tracer,guess_html_encoding,ruby-readability,simple-rss,stackprof,memory_profiler,rmmseg-cpp,logster,sass,sassc

• Error on rake db:migrate

INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate'
Rails Error: Unable to access log file. Please ensure that /var/www/discourse/log/production.log exists and is writable (ie, make it writable for user and group: chmod 0664 /var/www/discourse/log/production.log). The log level has been raised to WARN and the output directed to STDERR until the problem is fixed.
rake aborted!
Errno::EEXIST: File exists @ dir_s_mkdir - /var/www/discourse/public/uploads
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/seed-fu-2.3.5/lib/seed-fu/runner.rb:46:in `eval'
/var/www/discourse/lib/file_store/local_store.rb:75:in `copy_file'
/var/www/discourse/lib/file_store/local_store.rb:8:in `store_file'
/var/www/discourse/lib/file_store/base_store.rb:7:in `store_upload'
/var/www/discourse/lib/upload_creator.rb:93:in `block (2 levels) in create_for'
/var/www/discourse/lib/upload_creator.rb:92:in `open'
/var/www/discourse/lib/upload_creator.rb:92:in `block in create_for'
/var/www/discourse/lib/distributed_mutex.rb:21:in `synchronize'
/var/www/discourse/lib/distributed_mutex.rb:5:in `synchronize'
/var/www/discourse/lib/upload_creator.rb:34:in `create_for'
/var/www/discourse/app/models/user_avatar.rb:83:in `import_url_for_user'
(eval):21:in `block (2 levels) in run_file'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/seed-fu-2.3.5/lib/seed-fu/runner.rb:46:in `eval'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/seed-fu-2.3.5/lib/seed-fu/runner.rb:46:in `block (2 levels) in run_file'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/seed-fu-2.3.5/lib/seed-fu/runner.rb:58:in `block in open'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/seed-fu-2.3.5/lib/seed-fu/runner.rb:57:in `open'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/seed-fu-2.3.5/lib/seed-fu/runner.rb:57:in `open'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/seed-fu-2.3.5/lib/seed-fu/runner.rb:36:in `block in run_file'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `block in transaction'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/abstract/transaction.rb:184:in `within_new_transaction'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:220:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/seed-fu-2.3.5/lib/seed-fu/runner.rb:35:in `run_file'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/seed-fu-2.3.5/lib/seed-fu/runner.rb:26:in `block in run'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/seed-fu-2.3.5/lib/seed-fu/runner.rb:25:in `each'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/seed-fu-2.3.5/lib/seed-fu/runner.rb:25:in `run'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/seed-fu-2.3.5/lib/seed-fu.rb:29:in `seed'
/var/www/discourse/lib/tasks/db.rake:8:in `block in <top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rake-11.3.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
(See full trace by running task with --trace)

YAML file

templates:
  - "templates/web.template.yml"
  - "templates/web.ratelimited.template.yml"

expose:
  - "80:80"
  - "2222:22"

docker_args: ' --net=host --add-host localhost:<lo0 alias> '

params:

env:
  LANG: en_US.UTF-8

  DISCOURSE_DB_SOCKET: ''
  DISCOURSE_DB_HOST: <postgresql url>
  DISCOURSE_DB_USERNAME: <postgresql username>
  DISCOURSE_DB_PASSWORD: <postgresql password>

  DISCOURSE_REDIS_HOST: <lo0 alias>

  DISCOURSE_DEVELOPER_EMAILS: <my email>
  DISCOURSE_HOSTNAME: <my hostname>

  DISCOURSE_SMTP_ADDRESS: <smtp url>
  DISCOURSE_SMTP_PORT: <smtp port>
  DISCOURSE_SMTP_USER_NAME: <smtp username>
  DISCOURSE_SMTP_PASSWORD: <smtp password>

volumes:
  - volume:
      host: /var/discourse/shared/app
      guest: /shared
  - volume:
      host: /var/discourse/shared/app/log/var-log
      guest: /var/log

hooks:
  after_code:
    - exec:
        cd: $home/plugins
        cmd:
          - git clone https://github.com/discourse/docker_manager.git

run:
  - exec: awk -F\# '{print $1;}' ~/.ssh/authorized_keys | awk 'BEGIN { print "Authorized SSH keys for this container:"; } NF>=2 {print $NF;}'

Some (maybe) useful information:

• I have passed through many other errors before reaching this one, but I have managed to solve them

• I have defined an lo0 alias to make Redis accessible inside the container

• On my Linux, I executed the "standalone" version, the "web_only" + "data" version and a custom "web_only" + "cache" + "db" version and all of them worked, but I tested it neither with Redis running on the host nor with the PostgreSQL on the cloud

• On my Mac, I could not run Discourse in any way, but the error logs and some researches led me to believe it was a problem with the database on this specific OS

• Software versions

  • Docker: 17.03.1-ce
  • PostgreSQL: 9.6.2
  • Redis: 3.2.9

Final thoughts

Am I missing something or doing something wrong? Do you need any missing information? Please, let me know!

I want to set it running as fast as possible, but I have been stucked in this the whole day.

Thank you all in advance for any help!

Posts: 6

Participants: 3

Read full topic

@tophee wrote:

I noticed that the summary part in [details=Summary]This text will be hidden[/details] is rendered as ordinary text in emails with nothing hinting at the hidden details.

This is what it looks online:

And this is what it looks like in the email

I think it would be great to somehow convey to email recipients that what they are seeing is only the summary of a larger chunk of text.

To start with, it would be good if the black triangle that is shown before the summary online would also be included in the email. In addition, it might even be good to add a link after the summary saying "Click here to see details online" which would open the post online with that particular detail segment expanded (if that is possible at all).

Posts: 1

Participants: 1

Read full topic

@daath wrote:

Continuing the discussion from Did onebox change? They're not showing for my main site any longer:

@eviltrout was totally awesome and made it work again - but it's still not entirely back to normal. It no longer follows a 302 redirect:

should yield the same as:

The first one, results in a HEAD => 501 then GET => 302 redirect, which should finally lead to a GET => 200

You guys rock

Posts: 3

Participants: 2

Read full topic

@Rob_Burkman wrote:

A few months ago, I inherited a discourse site that we use internally, so I am pretty new to all of this. In the past, I've been able to upgrade smoothly via the one-click browser upgrade feature, but today it failed with the following message. Any help is appreciated!

rake aborted!
Excon::Error::Certificate: SSL_connect returned=1 errno=0 state=error: certificate verify failed (OpenSSL::SSL::SSLError) Unable to verify certificate. This may be an issue with the remote host or with Excon. Excon has certificates bundled, but these can be customized:

            `Excon.defaults[:ssl_ca_path] = path_to_certs`
            `ENV['SSL_CERT_DIR'] = path_to_certs`
            `Excon.defaults[:ssl_ca_file] = path_to_file`
            `ENV['SSL_CERT_FILE'] = path_to_file'
            `Excon.defaults[:ssl_verify_callback] = callback`
                (see OpenSSL::SSL::SSLContext#verify_callback)
or:
            `Excon.defaults[:ssl_verify_peer] = false` (less secure).

The full log.pdf (376.0 KB).

Posts: 4

Participants: 4

Read full topic

@tophee wrote:

Continuing the discussion from Admins can clearly see all private messages of all users:

A while ago, the team has addressed privacy concerns by not allowing moderators to read other users PMs. Requests for adding "administrative friction" to when admins access these PMs have so far been turned down.

My intention with this topic is not to try and change their minds but to inquire whether such a functionality could be added via a plugin and if so, to specify what such a plugin should look like.

To start with, I would like to keep it as simple as possible and here is my suggestion how in very broad terms:

1. Disallow admins from reading PMs
2. Specify Super-admins who are allowed to read PMs

(Personally, the way I would use this on my site is that I create a separate super-admin account which I will only use to access PMs in those cases where it is necessary.)

So, how to implement this?

Step 1 should not be a problem, but if system user or discobot need to read access, it may get a bit tricker.

Step 2 should obviously not be possible via the UI but will need to be hardcoded into the plugin source code so that adding or revoking super-admin privileges will require upgrading the plugin.

Posts: 13

Participants: 7

Read full topic

@chrisgalpin wrote:

Version v1.9.0.beta1 +63

/var/www/discourse/app/controllers/users_controller.rb:132:in `username'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/abstract_controller/base.rb:198:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_controller/metal/rendering.rb:10:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:117:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.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.4.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:505:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:778:in `_run_process_action_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.4.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.4.0/gems/activesupport-4.2.8/lib/active_support/notifications.rb:164:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/notifications.rb:164:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-4.2.8/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/abstract_controller/base.rb:137:in `process'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionview-4.2.8/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-mini-profiler-0.10.4/lib/mini_profiler/profiling_methods.rb:102:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_controller/metal.rb:237:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/routing/route_set.rb:74:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/routing/route_set.rb:43:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/journey/router.rb:43:in `block in serve'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/journey/router.rb:30:in `each'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/journey/router.rb:30:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/routing/route_set.rb:817:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/builder.rb:63:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/conditionalget.rb:38:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/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.4.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/flash.rb:260:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/session/abstract/id.rb:225:in `context'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/session/abstract/id.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/cookies.rb:560:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-4.2.8/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.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.4.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:88:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:778:in `_run_call_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/logster-1.2.7/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-4.2.8/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.4.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.4.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/methodoverride.rb:22:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/runtime.rb:18:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/sendfile.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-mini-profiler-0.10.4/lib/mini_profiler/profiler.rb:282:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.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.4.0/gems/railties-4.2.8/lib/rails/engine.rb:518:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-4.2.8/lib/rails/application.rb:165:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-4.2.8/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-4.2.8/lib/rails/railtie.rb:194:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/urlmap.rb:66:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/urlmap.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/urlmap.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.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.4.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:702:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:549:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:142:in `start'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.3.0/bin/unicorn:126:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.4.0/bin/unicorn:22:in `load'
/var/www/discourse/vendor/bundle/ruby/2.4.0/bin/unicorn:22:in `<main>'

/upgrade just asked me to do a git pull and a rebuild. Did so, but same error (most recent log above).

Posts: 8

Participants: 3

Read full topic

@kara-todd wrote:

I've been trying to add an interactive nav icon to our top menu bar.

So far I have:
1. created a widget
2. found the addHeaderPanel and called api.addHeaderPanel('custom-menu-button', 'customMenu')

However, this is where I get stuck... it looks like (according to the code) the panel will only show if the header widget state has {customMenu: true} in it... and for the life of me I cannot figure out how to set/override the state...

This panel will ultimately need to toggle it's own state property (open/closed) to change the icon state, and also to send an action out to render a component with the menu. (unfortunately, it's full-screen so I can't nest it in the header Panel)

I had this working with a component pretty quickly, but the new virtual DOM is taking some adjustment mentally.

Posts: 1

Participants: 1

Read full topic