Grippie gone - can't resize composer

March 16, 2016, 3:15 am

≫ Next: Installtion on aws New Cloud Server but not Working

≪ Previous: What's the correct way to reset instance?

@Tia wrote:

Hi guys,
I can no longer resize the composer on my discourse community.
It does however appear here on the meta forum. I'm using the same browser for both..

Posts: 2

Participants: 2

Read full topic

↧

Installtion on aws New Cloud Server but not Working

March 16, 2016, 3:16 am

≫ Next: Swedish? meta just showed me the UI in Swedish

≪ Previous: Grippie gone - can't resize composer

@zinda_xyz wrote:

my domain url is discourse.zinda.xyz

my server is amazone and domain in godaddy

i install discourse on my server steps as https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md but i can not see in my domain

also after ./launcher start app command i give response like

/usr/bin/docker run -d --restart=always -e LANG=en_US.UTF-8 -e RAILS_ENV=production -e UNICORN_WORKERS=3 -e UNICORN_SIDEKIQS=1 -e RUBY_GC_MALLOC_LIMIT=40000000 -e RUBY_HEAP_MIN_SLOTS=800000 -e DISCOURSE_DB_SOCKET=/var/run/postgresql -e DISCOURSE_DB_HOST= -e DISCOURSE_DB_PORT= -e DISCOURSE_DEVELOPER_EMAILS=discourse.zinda.xyz@gmail.com -e DISCOURSE_HOSTNAME=http://discourse.zinda.xyz -e DISCOURSE_SMTP_ADDRESS=smtp.sparkpostmail.com -h ip-172-31-29-0-app -e DOCKER_HOST_IP=172.17.0.1 --name app -t -p 80:80 -v /var/discourse/shared/standalone:/shared -v /var/discourse/shared/standalone/log/var-log:/var/log local_discourse/app /sbin/boot
3e91ea807eb35d303f0d63e5cb322357b724bc371025847ca9cba6a6a04e4b61

also i can create a admin for same
reference link https://meta.discourse.org/t/create-admin-account-from-console/17274

help me
thanks in advance

Posts: 1

Participants: 1

Read full topic

↧

Swedish? meta just showed me the UI in Swedish

March 16, 2016, 6:59 am

≫ Next: Alternatives to Mandrill

≪ Previous: Installtion on aws New Cloud Server but not Working

@kpfleming wrote:

I opened my browser, clicked 'log out' on the drop-down menu (because my browser doesn't recover Discourse sessions properly when I log in), and got the anonymous home page. The buttons and top header were in Swedish ("Logga in" instead of "Login"). I do not have Swedish selected in my browser and never have.

Posts: 1

Participants: 1

Read full topic

↧

Alternatives to Mandrill

March 16, 2016, 8:15 am

≫ Next: Changing ownership updates timestamp

≪ Previous: Swedish? meta just showed me the UI in Swedish

@alwayslookright wrote:

What are the alternatives to using Mandrill?

I work on a lot of sites that are about gambling and for those that don't know, mailchimp has a strict policy that is anti-gambling. After just mentioning the word gambling, I got an email from mandrill they are closing my account.

Posts: 4

Participants: 3

Read full topic

↧

Changing ownership updates timestamp

March 16, 2016, 8:23 am

≫ Next: No content on homepage for Googlebot

≪ Previous: Alternatives to Mandrill

@roarkely wrote:

When you update the owner of a post, it updates the timestamp for that topic.

This was an expected behavior that felt like a bug. If this is not a bug, I suggest we add an option to the change ownership modal dialog to leave the timestamp as-is.

Background
We imported a lot of historical conversations into our Discourse instance. Because of the platform we came from, that included a bunch of duplicate user accounts. As part of a general cleanup, we were de-duping those user accounts and changed ownership of posts. That pushed old topics up to the front page. We had to go back and re-adjust the timestamps for all these topics back to get them back in their expected chronological order.

Posts: 7

Participants: 3

Read full topic

↧

No content on homepage for Googlebot

March 16, 2016, 9:30 am

≫ Next: Change a new post to a comment on an existing topic?

≪ Previous: Changing ownership updates timestamp

@DeanMarkTaylor wrote:

Currently there doesn't appear to be any content output in the #main-outlet element for Googlebot:

HTML for reference:

<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="utf-8">
    <title>Discourse Meta</title>
    <meta name="description" content="Discussion about the next-generation open source Discourse forum software">
    <meta name="author" content="">
<meta name="generator" content="Discourse 1.5.0.beta12 - https://github.com/discourse/discourse version e84d5549efe6c24a6230cfbe2ce8c1b511ffc9d6">
<link rel="icon" type="image/png" href="https://discourse-meta.s3-us-west-1.amazonaws.com/original/3X/c/b/cb4bec8901221d4a646e45e1fa03db3a65e17f59.png">
<link rel="apple-touch-icon" type="image/png" href="https://discourse-meta.s3-us-west-1.amazonaws.com/original/3X/c/b/cb4bec8901221d4a646e45e1fa03db3a65e17f59.png">
<link rel="icon" sizes="144x144" href="https://discourse-meta.s3-us-west-1.amazonaws.com/original/3X/c/b/cb4bec8901221d4a646e45e1fa03db3a65e17f59.png">
<meta name="theme-color" content="#ffffff">
<meta name="viewport" content="width=device-width, minimum-scale=1.0, maximum-scale=1.0, user-scalable=yes">




        <link rel="alternate" type="application/rss+xml" title="Latest posts" href="https://meta.discourse.org/posts.rss" />
    <link rel="alternate" type="application/rss+xml" title="Latest topics" href="https://meta.discourse.org/latest.rss" />

    <style>
        img { max-width: 100%; width: auto; height: auto; }
    </style>
  </head>
  <body>

    <header>
      <a href="/"><img src="https://discourse-meta.s3-us-west-1.amazonaws.com/original/3X/9/d/9d543e92b15b06924249654667a81441a55867eb.png" alt="Discourse Meta" id="site-logo" style="max-width: 400px;"></a>
    </header>
    <div id="main-outlet" class="wrap">




    </div>
    <footer class="container">
      <nav itemscope itemtype='http://schema.org/SiteNavigationElement'>
        <a href='/'>Home</a>
        <a href="/categories">Categories</a>
        <a href="/guidelines">FAQ/Guidelines</a>
        <a href="/tos">Terms of Service</a>
        <a href="/privacy">Privacy Policy</a>
      </nav>
      <p>Powered by <a href="http://www.discourse.org">Discourse</a>, best viewed with JavaScript enabled</p>
    </footer>
    <script type="text/javascript">

  var _gaq = _gaq || [];
  _gaq.push(['_setAccount', 'UA-33736483-2']);


  _gaq.push(['_setCustomVar', 1, 'Anonymous', true, 2]);

  (function() {
    var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
    ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
    var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
  })();

</script>

       <script>
 Discourse.ExternalNavItem = Discourse.NavItem.extend({
    href : function() {
      return this.get('href');
    }.property('href')
  });

  I18n.translations[I18n.locale].js.filters.bugs = { title: "Bugs", help: "Open Bugs" };
  I18n.translations[I18n.locale].js.filters.features = { title: "Features", help: "Open Feature Requests" };

  Discourse.NavItem.reopenClass({
    buildList : function(category, args) {
      var list = this._super(category, args);
      if(!category) {
        list.push(Discourse.ExternalNavItem.create({href: '/category/bug?order=op_likes&status=open', name: 'bugs'}));
        list.push(Discourse.ExternalNavItem.create({href: '/category/feature?order=op_likes&status=open', name: 'features'}));
      }
      return list;
    }
  });
  </script>
  </body>
</html>

I would expect the latest list of topics for meta.

Posts: 8

Participants: 3

Read full topic

↧

Change a new post to a comment on an existing topic?

March 16, 2016, 12:56 pm

≫ Next: Topic missing from digest

≪ Previous: No content on homepage for Googlebot

@watchmanmonitor wrote:

Continuing the discussion from Redirect / convert post from Pending Approval to Direct Message?:

Sometimes the "new" topic really belongs as a comment on an existing thread.

Right now all I can do is login as them, and re-post their comment.. it would be nice to move the pending message to an existing topic.

Posts: 1

Participants: 1

Read full topic

↧

Topic missing from digest

March 16, 2016, 12:58 pm

≫ Next: User gets 500 after authentication

≪ Previous: Change a new post to a comment on an existing topic?

@RalfJung wrote:

The topics of a particular user are missing on the digest. I was so far unable to reproduce this with any of my own users.

Steps to reproduce:

Create a new topic

In the Digest preview in the settings, enter a date two days in the past (there's not much traffic on my site) and check if the topic appears

For my own topics, the topic shows up. If that user (just someone using my site) creates a new topic, it is not shown in the Digest. This is not just an issue in the preview: The topic does not show up in the Digests that are actually sent, either.

I am quite lost; I have no idea how it can even be the case that particular topics do not show up in the digest. I would welcome any help.

This is with the 1.5 beta 12.

Posts: 7

Participants: 3

Read full topic

↧

User gets 500 after authentication

March 16, 2016, 1:54 pm

≫ Next: New user messages not sending/recieving (topic unavalible)

≪ Previous: Topic missing from digest

@Frey wrote:

Hello guys, one of my users experienced following error:

He enters login, password, push 'Login" and get this:

I've checked out forum logs and here is what I found:

NoMethodError (undefined method `enable_quoting' for nil:NilClass)
/var/www/discourse/app/serializers/current_user_serializer.rb:54:in `enable_quoting'

/var/www/discourse/app/serializers/current_user_serializer.rb:54:in `enable_quoting'
(eval):18:in `_fast_attributes'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:467:in `rescue in attributes'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:455:in `attributes'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:479:in `_serializable_hash'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:361:in `serializable_hash'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:349:in `as_json'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/multi_json-1.11.2/lib/multi_json/adapters/oj.rb:21:in `dump'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/multi_json-1.11.2/lib/multi_json/adapters/oj.rb:21:in `dump'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/multi_json-1.11.2/lib/multi_json/adapter.rb:25:in `dump'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/multi_json-1.11.2/lib/multi_json.rb:136:in `dump'
/var/www/discourse/app/controllers/application_controller.rb:348:in `preload_current_user_data'
/var/www/discourse/app/controllers/application_controller.rb:203:in `preload_json'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/callbacks.rb:432:in `block in make_lambda'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/callbacks.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/callbacks.rb:164:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/callbacks.rb:504:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/callbacks.rb:504:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/callbacks.rb:504:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/callbacks.rb:504:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/callbacks.rb:778:in `_run_process_action_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/notifications.rb:164:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/notifications.rb:164:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.2/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/abstract_controller/base.rb:137:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.2.5.2/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.9.2/lib/mini_profiler/profiling_methods.rb:76:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_controller/metal.rb:237:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/routing/route_set.rb:74:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/routing/route_set.rb:74:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/routing/route_set.rb:43:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/routing/mapper.rb:49:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/journey/router.rb:43:in `block in serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/journey/router.rb:30:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/journey/router.rb:30:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/routing/route_set.rb:815:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/builder.rb:63:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/conditionalget.rb:25:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/head.rb:13:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:129:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/middleware/flash.rb:260:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:225:in `context'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/middleware/cookies.rb:560:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.2/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.2/lib/active_record/connection_adapters/abstract/connection_pool.rb:653:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/callbacks.rb:88:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/callbacks.rb:778:in `_run_call_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.2/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-1.1.1/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.5.2/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.5.2/lib/rails/rack/logger.rb:22:in `call'
/var/www/discourse/config/initializers/100-quiet_logger.rb:10:in `call_with_quiet_assets'
/var/www/discourse/config/initializers/100-silence_logger.rb:26:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5.2/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/methodoverride.rb:22:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/runtime.rb:18:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/sendfile.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.9.2/lib/mini_profiler/profiler.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-2.0.0.beta.5/lib/message_bus/rack/middleware.rb:60:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:73:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.5.2/lib/rails/engine.rb:518:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.5.2/lib/rails/application.rb:165:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.5.2/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.5.2/lib/rails/railtie.rb:194:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/urlmap.rb:66:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/lib/unicorn/http_server.rb:562:in `process_client'
/var/www/discourse/lib/scheduler/defer.rb:85:in `process_client'
/var/www/discourse/lib/middleware/unicorn_oobgc.rb:95:in `process_client'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/lib/unicorn/http_server.rb:658:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/lib/unicorn/http_server.rb:508:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/lib/unicorn/http_server.rb:132:in `start'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/bin/unicorn:126:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in `load'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in `<main>'

I'm using the last version of Discourse, can anybody help me with this error? What should I do to fix this error?

Thanks in advance.

Posts: 4

Participants: 2

Read full topic

↧

New user messages not sending/recieving (topic unavalible)

March 16, 2016, 2:20 pm

≫ Next: About page "Site Statistics" doesn't match Admin Dashboard stats

≪ Previous: User gets 500 after authentication

@Should_We_Leave wrote:

For some reason, all users are unable to recieve messages or send them - getting this:

Even as an administrator sending a message to the users, I get this message. Every other aspect of the install works perfectly - just not the message sending!

Point of note: the notification goes through successfully, but when clicked, the error is shown.

Debugging:
- I tried changing the user's role to 1 from 0, made no difference.

Posts: 4

Participants: 2

Read full topic

↧

About page "Site Statistics" doesn't match Admin Dashboard stats

March 16, 2016, 4:49 pm

≫ Next: Inbound gutter post-links are not relative urls

≪ Previous: New user messages not sending/recieving (topic unavalible)

@DeanMarkTaylor wrote:

To me the "Posts" numbers displayed on the About page is actually a count of replies...
... not just replies to public topics but replies to "private messages" too.

I'm thinking that on the About page:

"private message" replies should be excluded from the counts (topic and replies/posts)

AND "Posts" should be renamed to "Replies".

Posts: 4

Participants: 2

Read full topic

↧

Inbound gutter post-links are not relative urls

March 16, 2016, 5:55 pm

≫ Next: Adding content between topic list items

≪ Previous: About page "Site Statistics" doesn't match Admin Dashboard stats

@ryantm wrote:

inbound gutter post-links are not relative urls for example, in this post

Auto-replace emoji like ☺ with Discourse codes feature

Over on TDWTF, I've been using a bot to automatically replace Unicode emoji like [:slight_smile:] with Discourse emoji codes like :smile:; it's useful when posting from mobile. @codinghorror suggests it could be made a Discourse feature; it never occurred to me before, but it does sound like it'd be useful. That way it could also work in PMs, which is something I haven't got working in my bot yet.

there is a gutter post-links link like:

<a class="track-link inbound" href="https://meta.discourse.org/t/emoji-in-topic-names/33852/4"><span>Emoji in topic names 😛💜🍦</span><span class="badge badge-notification clicks">3</span></a>

I think it would be better if the link href were "/t/emoji-in-topic-names/33852/4".

I think this is the same problem I reported in https://meta.discourse.org/t/putting-a-discourse-development-server-behind-proxy-seems-to-mess-up-some-but-not-most-urls/40829 but you cannot see the avatar problem on this site because this site uses a CDN for the avatars, and in that case, it makes sense to use an absolute URL instead of a relative one.

Posts: 2

Participants: 2

Read full topic

↧

Adding content between topic list items

March 16, 2016, 6:05 pm

≫ Next: I installed this plugin and things have gone weird

≪ Previous: Inbound gutter post-links are not relative urls

@aedensixty wrote:

How do I go about using a plugin-outlet or injecting content/ads between a set number of topics in a list. e.g. every 5 topics in the list show an image in between.

Posts: 1

Participants: 1

Read full topic

↧

I installed this plugin and things have gone weird

March 16, 2016, 10:59 pm

≫ Next: Discourse Chinese Localization Pack

≪ Previous: Adding content between topic list items

@David_Buzz wrote:

https://github.com/ntauthority/discourse-cookie-domain

Before: I could manually login to the discourse no problem, do adminy things etc, but the cookie that was created by the discourse instance wasn't being propogated to my other subdomain ( we'll call them discourse.example.com and other.example.com

After: When I attempt to "login" to discourse, it behaves as if I have been successful, in that the login page goes away, and if I'm a new-user registration, I get a welcome email from discourse... but the Banner at the top of discourse still shows "Sign Up" and "Login" buttons, and the GUI clearly thinks I'm not logged in. The cookie that is created during this process IS now accessible from "other.example.com", so that's at least something! .

Thoughts?

Posts: 4

Participants: 2

Read full topic

↧

Discourse Chinese Localization Pack

March 16, 2016, 11:00 pm

≫ Next: Big pictures be trimmed on v1.5.0.beta12 +137

≪ Previous: I installed this plugin and things have gone weird

@fantasticfears wrote:

I found Chinese users are willing to have all related plugins in one place. It also helps them to reduce deployment downloading overhead (many git repos). And it turns out localization features are better to be built in plugin.

Old related plugins will be deprecated when Discourse 1.5 stable releases. They will be deleted when Discourse 1.6 stable releases.

GitHub:
https://github.com/fantasticfears/discourse-chinese-localization-pack

Discourse Chinese community:

meta.discoursecn.org

Discourse 中文本地化服务集合

将随 Discourse 1.5 正式版取代原来的相关的插件，Discourse 1.6 版本发布时原先的几个相关插件将被删除。测试中 https://github.com/fantasticfears/discourse-chinese-localization-pack 这是一个 Discourse 中文本地化插件的集合，一些特性适合增加到 Discourse 的核心代码库中，而这个插件专注于不适用于 Discourse 核心的功能。功能概况登录方法：微博人人豆瓣 QQ 分享链接：（有部分服务的显示尚未有更好的解决办法）微博（weibo）人人（renren）腾讯微博（tencent_weibo）豆瓣（douban）：需要图标微信（wechat）：第三方服务，需要替代品 QQ 空间（qzone）：需要图标安装在 app.yml 的 hooks: after_code: - exec: cd: $home/plugins cmd: - mkdir -p ...

Installation

Edit app.yml.
hooks:
  after_code:
    - exec:
        cd: $home/plugins
        cmd:
          - mkdir -p plugins
          - git clone https://github.com/discourse/docker_manager.git
Add a new line after - git clone https://github.com/discourse/docker_manager.git:

- git clone https://github.com/fantasticfears/douban-login.git

Usage

Open plugin settings and follow the instructions.

Issues:

Visit

GitHub issues

中文社群

Why some plugins are not included?

Wechat login plugin: I don't own a company for registeration. I still want to test the code before publishing.

Chinese username: I considered that it should be an option in the core. I am building related bindings to ICU. Once I pushed ahead of my academic work, I will work on that.

Posts: 1

Participants: 1

Read full topic

↧

Big pictures be trimmed on v1.5.0.beta12 +137

March 16, 2016, 11:24 pm

≫ Next: Migrate from Digital Ocean to OVH?

≪ Previous: Discourse Chinese Localization Pack

@jongnam wrote:

Continuing the discussion from Help us test our new post rendering engine!:

I am running a k-pop fan forum and upgraded to v1.5.0.beta12 +137 jut now. But the big picture is being displayed as trimmed from laptop/tablet browsers. Please take a look at the link below:

mywoohyun.com

이제 진짜 안올리믄 안될것 같은 11시짤ㅋㅋ

이게 뭔가 이제 없음 허전하고 그르네요잉~ ㅎㅎ [이미지] [이미지] [이미지] [이미지] [이미지] [이미지]

Posts: 6

Participants: 3

Read full topic

↧

Migrate from Digital Ocean to OVH?

March 17, 2016, 1:44 am

≫ Next: Login - Can't verify CSRF token authenticity

≪ Previous: Big pictures be trimmed on v1.5.0.beta12 +137

@ljpp wrote:

I run 3 VPS's, two of them for Discourse hosting. Looking at the pricing of OVH and Digital Ocean I could make somewhat significant month savings by moving my business to OVH. Especially the 4-core/8GB plan has a huge difference of 34$ vs 80$.

The OVH reviews on the web however are very mixed and there is a lot of seriously negative feedback included. Digital Ocean customers seem to be 99% positive and so am I - very realiable service and good admin panel with flexible scaling.

What do you think - what is your experience on OVH? I run a high traffic forum so I need performance and reliability.

OVH pricing varies geographically (Ireland, Canada, UK, Germany, etc.). Is there any reason why I should not pick OVH.ie as it seems to be even cheaper than other Euro locations?

Posts: 4

Participants: 2

Read full topic

↧

Login - Can't verify CSRF token authenticity

March 17, 2016, 2:07 am

≫ Next: The Discourse API in GraphQL

≪ Previous: Migrate from Digital Ocean to OVH?

@Steve_Ng wrote:

Hi, when I am logging in, sometimes I get this error. It would result in me unable to login at all. Any idea how does this error come from?

This result in the inability to even login to discourse.

I, [2016-03-17T17:05:20.078871 #4141]  INFO -- : Started POST "/session" for 127.0.0.1 at 2016-03-17 17:05:20 +0800
I, [2016-03-17T17:05:20.134365 #4141]  INFO -- : Processing by SessionController#create as */*
I, [2016-03-17T17:05:20.136184 #4141]  INFO -- :   Parameters: {"login"=>"xx@gmail.com", "password"=>"[FILTERED]"}
W, [2016-03-17T17:05:20.137855 #4141]  WARN -- : Can't verify CSRF token authenticity
I, [2016-03-17T17:05:20.139322 #4141]  INFO -- :   Rendered text template (0.0ms)
I, [2016-03-17T17:05:20.140774 #4141]  INFO -- : Filter chain halted as :verify_authenticity_token rendered or redirected
I, [2016-03-17T17:05:20.142685 #4141]  INFO -- : Completed 403 Forbidden in 5ms (Views: 1.6ms | ActiveRecord: 0.0ms)

Posts: 1

Participants: 1

Read full topic

↧

The Discourse API in GraphQL

March 17, 2016, 2:24 am

≫ Next: No Highlighting of Group mentions in Markdown Preview

≪ Previous: Login - Can't verify CSRF token authenticity

@Sander78 wrote:

@sashko (Meteor developer) wrote a post om Medium about GraphQL, using Discourse as example.

medium.com

Discourse in GraphQL, part 1 — Building Apollo

Mapping REST to GraphQL, login, and more

Reading time: 9 mins

Posts: 2

Participants: 2

Read full topic

↧

No Highlighting of Group mentions in Markdown Preview

March 17, 2016, 2:46 am

≫ Next: Where to see if discourse can do what I want?

≪ Previous: The Discourse API in GraphQL

@rriemann wrote:

I just noticed that while usernames have a different style applied in the markdown preview (bold, gray), this is not the case for group mentions. Is this intentional? I consider this as incoherent and suggest to apply either the same style to group mentions in the preview or a different one.

Advantage: Text author is assured that mention is well recognised and functional.

Posts: 8

Participants: 4

Read full topic

↧

Installation

Usage

Issues:

Why some plugins are not included?

Latest Images