Share Reply as Tweet or Tweet Reply

August 16, 2015, 6:58 am

≫ Next: Unable to resize images after uploading

≪ Previous: YouTube playlist inks are incorrectly oneboxed

Hi, I need a little help.

Is it possible for users to share their replies on Twitter? Like, the content of the tweet is the actual reply and not the thread name alongside a link to the reply.

If not, can user tweets with particular hashtags be fed into a topic?

Thanks!

Posts: 1

Participants: 1

Read full topic

↧

Unable to resize images after uploading

August 16, 2015, 11:24 am

≫ Next: Did this API endpoint break?

≪ Previous: Share Reply as Tweet or Tweet Reply

@ky_metro wrote:

Continuing the discussion from Resize images after uploading:

zogstrip:

This is now done. We'll accept images of up to 10MB and then downsize them to the maximum allowed image size

github.com

FEATURE: automatically downsize large images

by ZogStriP on 04:33PM - 12 Aug 15

changed 3 files with 20 additions and 12 deletions.

github.com/discourse/discourse

I've been looking forward to this feature for a long time. I just upgraded to the current version of Discourse, and it's not working. I've tried to reproduce this in various places with varying results.

This is the test image, 5.48 mb: https://www.ushpa.aero/media/photos/pg_2008_00_hires.jpg

At my main website, uploading this image goes fine until it reaches 100%, then it stays at "Uploading 100%" forever.

On a small dev install (also on current version) it gets to 100% then starts over from 0%. Repeats this indefinitely.

On http://try.discourse.org (and here on meta) it uploads to 100% then says "Sorry, the image you are trying to upload is too big (maximum size is 3072KB), please resize it and try again." Possibly these are not on the latest version?

Steps to repro:

Find an image larger than the image size limit but less than 10MB.

Try to upload it.

Posts: 2

Participants: 2

Read full topic

↧

Did this API endpoint break?

August 16, 2015, 11:52 am

≫ Next: Double click checkbox

≪ Previous: Unable to resize images after uploading

@joshfrank wrote:

I've been using:
/admin/users/list/all.json?api_key={mykey}&api_username={myuser}&filter={some_address}
to look up users by email, and this worked fine for about a year. But recently it started returning an empty array, even when the Discourse app itself returns valid search results. I know the standard advice is to sniff the traffic to see what I need to pass the API, but I'm puzzled about that too, because the app does this:
/admin/users/list/all.json?filter={some_address}&show_emails=false
and passes authentication info in cookies (called _forum_session and _t).

So why would the app's call be working and my API call not be working, and how can I fix this?

Posts: 1

Participants: 1

Read full topic

↧

Double click checkbox

August 16, 2015, 1:42 pm

≫ Next: Embedding not working in Expression Engine page

≪ Previous: Did this API endpoint break?

@Mathias_Jensen wrote:

Hello.

I'm currently on v1.4.0.beta9 +58.

When I want to check a checkbox in the admin panel, I have to click the box twice before it's checked. I guess that's a bug?

Best regards,
Mathias

Posts: 8

Participants: 5

Read full topic

↧

Embedding not working in Expression Engine page

August 16, 2015, 1:50 pm

≫ Next: Pin topic broken

≪ Previous: Double click checkbox

@barryparr wrote:

I'm trying to get embedding set up on my site. Topics are being created in my Discourse forum, but the topic and replies are not showing up on my site.

The site uses Expression Engine. It's a PHP-based CMS. But all pages are cached & delivered as flat html.

Here's the embed code on this page
<div id="discourse-comments"></div>

<script type="text/javascript">
  var discourseUrl = "http://forum.coastsider.com/",
      discourseEmbedUrl = 'http://coastsider.com/site/news/testing_led_lights_on_the_midcoast';

  (function() {
    var d = document.createElement('script'); d.type = 'text/javascript'; d.async = true;
      d.src = discourseUrl   'javascripts/embed.js';
    (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(d);
  })();
</script>

Posts: 5

Participants: 2

Read full topic

↧

Pin topic broken

August 16, 2015, 6:07 pm

≫ Next: Discourse constantly generating invisible welcome topics on its own

≪ Previous: Embedding not working in Expression Engine page

@emanger wrote:

Hi,

When trying to advance on the pin topic system calendar, it does not work properly.

Please fix?

Posts: 17

Participants: 2

Read full topic

↧

Discourse constantly generating invisible welcome topics on its own

August 16, 2015, 6:08 pm

≫ Next: Slack Notification Plugin

≪ Previous: Pin topic broken

@themightychris wrote:

I'm using the discourse-webhooks plugin to push alerts when new topics are created to other mediums and it's caused me to notice that my discourse forum is generating a new welcome topic that isn't discoverable via the UI every 1-4 days. They don't even come up in search but a topic_created event is firing for them and they're reachable via their permalink only if I'm logged in:

http://forum.codeforphilly.org/t/welcome-to-code-for-philly-public-forum/196

http://forum.codeforphilly.org/t/welcome-to-code-for-philly-public-forum/197

http://forum.codeforphilly.org/t/welcome-to-code-for-philly-public-forum/198

http://forum.codeforphilly.org/t/welcome-to-code-for-philly-public-forum/199

http://forum.codeforphilly.org/t/welcome-to-code-for-philly-public-forum/200

http://forum.codeforphilly.org/t/welcome-to-code-for-philly-public-forum/201

They all look like this:
Screen Shot 2015-08-16 at 9.05.53 PM.png935x712 132 KB

What's the deal with these? Can I disable them? Is there a reliable way for me to identify and ignore them? I'm running 1.4.0beta7

Posts: 4

Participants: 3

Read full topic

↧

Slack Notification Plugin

August 17, 2015, 1:56 am

≫ Next: Big header, scroll down, make header small (Like default size)

≪ Previous: Discourse constantly generating invisible welcome topics on its own

@bernd wrote:

I created a plugin to notify a Slack channel about new topics in discourse. The source and setup documentation can be found on GitHub:

https://github.com/bernd/discourse-slack-plugin

The plugin has been written against discourse 1.4-beta and is running in our production setup with version 1.3.

Have fun!

Posts: 3

Participants: 3

Read full topic

↧

Big header, scroll down, make header small (Like default size)

August 17, 2015, 3:00 am

≫ Next: Feature: Add bulk actions to Unlist topics

≪ Previous: Slack Notification Plugin

@AlexTemina wrote:

Hallo hallo!

So I would like to have a header with a bigger size than default (Holding an image) and then reduce it, like the logo, to the default size, when you scroll down. Is that possible?

Thanks!

--Alex

Posts: 1

Participants: 1

Read full topic

↧

Feature: Add bulk actions to Unlist topics

August 17, 2015, 5:42 am

≫ Next: How to embed whole forum in another site

≪ Previous: Big header, scroll down, make header small (Like default size)

@adwiv wrote:

The bulk actions permit Close / Delete / Archive but does not allow Unlist.

The only way right now is to go into each topic and unlist them one by one. It might be useful to add it to the bulk actions, since some people may prefer to Unlist topics instead of deleting them.

Posts: 1

Participants: 1

Read full topic

↧

How to embed whole forum in another site

August 17, 2015, 7:14 am

≫ Next: Plugin-outlet incorrectly handles multiple plugins at the same outlet

≪ Previous: Feature: Add bulk actions to Unlist topics

@renai wrote:

hi all,

really new to Discourse, so please forgive my stupid newbie question

I have a Discourse forum at http://forum.delimiter.com.au.

This is a part of the Wordpress site http://delimiter.com.au.

All I want to do is grab the whole Discourse forum and embed it on a page under my normal Wordpress site header. I have the ability to embed whatever HTML, script etc I want under this on a dedicated page -- I just need the code.

Is there a way to do this? This would go a long way towards making Discourse feel part of the rest of my site.

Cheers!

Renai

Posts: 6

Participants: 4

Read full topic

↧

Plugin-outlet incorrectly handles multiple plugins at the same outlet

August 17, 2015, 9:03 am

≫ Next: Listing users by quarter and All time no longer works

≪ Previous: How to embed whole forum in another site

@dmitry_fedyuk wrote:

Wrong code is:

github.com

discourse/discourse/blob/v1.4.0.beta9/app/assets/javascripts/discourse/helpers/plugin-outlet.js.es6#L158


Ember.HTMLBars._registerHelper('plugin-outlet', function(params, hash, options, env) {
const connectionName = params[0];


if (!_connectorCache) { buildConnectorCache(); }


if (_connectorCache[connectionName]) {
  const childViews = _connectorCache[connectionName];


  // If there is more than one view, create a container. Otherwise
  // just shove it in.
  const viewClass = (childViews.length > 1) ? Ember.ContainerView : childViews[0];


  delete options.fn;  // we don't need the default template since we have a connector
  env.helpers.view.helperFunction.call(this, [viewClass], viewInjections(env.data.view.container), options, env);


  const cvs = env.data.view._childViews;
  if (childViews.length > 1 && cvs && cvs.length) {
    const inserted = cvs[cvs.length-1];
    if (inserted) {
      childViews.forEach(function(cv) {
        inserted.pushObject(cv.create());

Must be Ember.ContainerView.extend({tagName: ''}) instead of Ember.ContainerView.
The current wrong code breaks HTML markup in cases where HTML syntax does not allow wrapper DIV tag.
An example is admin-menu plugin outlet:

github.com

discourse/discourse/blob/v1.4.0.beta9/app/assets/javascripts/admin/templates/admin.hbs#L26


      {{/if}}
      {{nav-item route='adminEmail' label='admin.email.title'}}
      {{nav-item route='adminFlags' label='admin.flags.title'}}
      {{nav-item route='adminLogs' label='admin.logs.title'}}
      {{#if currentUser.admin}}
        {{nav-item route='adminCustomize.colors' label='admin.customize.title'}}
        {{nav-item route='admin.api' label='admin.api.title'}}
        {{nav-item route='admin.backups' label='admin.backups.title'}}
      {{/if}}
      {{nav-item route='adminPlugins' label='admin.plugins.title'}}
      {{plugin-outlet "admin-menu" tagName="li"}}
    </ul>


    <div class='boxed white admin-content'>
      <div class='admin-contents'>
        {{outlet}}
      </div>
    </div>


  </div>
</div>

If there are multiple admin-menu connectors then Discourse wrongly renders them as:

<ul>
	<!-- standard menu items: -->
	<li></li>
	<li></li>
	<!-- admin-menu connectors: -->
	<div>
		<li></li>
		<li></li>
	</div>
</ul>

Posts: 4

Participants: 4

Read full topic

↧

Listing users by quarter and All time no longer works

August 17, 2015, 9:41 am

≫ Next: Splitting topic moves "this topic is closed" post

≪ Previous: Plugin-outlet incorrectly handles multiple plugins at the same outlet

@jmamazo wrote:

Hello Guys

After we upgraded to the latest version (v1.4.0.beta9 +80)
We did notice that listing users by quarter and All time no longer works
it just loads for ages and then
:(
Error
while trying to load
Something went wrong.
Can anyone reproduce?

thanks in advance

Posts: 4

Participants: 3

Read full topic

↧

Splitting topic moves "this topic is closed" post

August 17, 2015, 10:14 am

≫ Next: Top contributor widget

≪ Previous: Listing users by quarter and All time no longer works

@paulkreuzer wrote:

When I want to merge a new topic into an existing one and close the new topic before moving the post(s) the "this topic is now closed" post is always moved too although I didn't select it.

Steps to reproduce:

close a topic

click "topic admin actions" > "select posts..."

select the post(s) you want to move

it will say you have selected X posts, where X is the actual number of posts you selected

click "move to existing topic"

The selected posts will be added to the existing topic followed by the "this topic is now closed" post. But the topic won't really be closed

Posts: 1

Participants: 1

Read full topic

↧

Top contributor widget

August 17, 2015, 11:51 am

≫ Next: Error 500 when we post new message

≪ Previous: Splitting topic moves "this topic is closed" post

@AlexAB wrote:

I would love too showcase our "top contributors" and team members (moderators, admins...etc.) on the side as a widget....any solutions?

Posts: 5

Participants: 3

Read full topic

↧

Error 500 when we post new message

August 17, 2015, 1:39 pm

≫ Next: Signup call-to-action when you read for a while

≪ Previous: Top contributor widget

@GranBen wrote:

Hi,

Since the last update, we get Error 500 when we post new topic.

Log error :

Message (26 copies reported)

PrettyText::JavaScriptError (PrettyText::JavaScriptError)

Backtrace

at /var/www/discourse/plugins/discourse-extra-nav-item/assets/javascripts/discourse-dev-nav-item.js:2:18
at /var/www/discourse/plugins/discourse-extra-nav-item/assets/javascripts/discourse-dev-nav-item.js:3:3
/var/www/discourse/lib/pretty_text.rb:102:in `block in create_new_context'
/usr/local/lib/ruby/2.0.0/set.rb:232:in `each_key'
/usr/local/lib/ruby/2.0.0/set.rb:232:in `each'
/var/www/discourse/lib/pretty_text.rb:96:in `create_new_context'
/var/www/discourse/lib/pretty_text.rb:116:in `block in v8'
/var/www/discourse/lib/pretty_text.rb:114:in `synchronize'
/var/www/discourse/lib/pretty_text.rb:114:in `v8'
/var/www/discourse/lib/pretty_text.rb:164:in `block in markdown'
/var/www/discourse/lib/pretty_text.rb:369:in `block in protect'
/var/www/discourse/lib/pretty_text.rb:367:in `synchronize'
/var/www/discourse/lib/pretty_text.rb:367:in `protect'
/var/www/discourse/lib/pretty_text.rb:163:in `markdown'
/var/www/discourse/lib/pretty_text.rb:221:in `cook'
/var/www/discourse/app/models/post_analyzer.rb:12:in `cook'
/var/www/discourse/app/models/post_analyzer.rb:111:in `cooked_document'
/var/www/discourse/app/models/post_analyzer.rb:49:in `raw_mentions'
/var/www/discourse/app/models/post.rb:157:in `block (2 levels) in <class:Post>'
/var/www/discourse/lib/validators/post_validator.rb:54:in `max_mention_validator'
/var/www/discourse/lib/validators/post_validator.rb:11:in `validate'
/var/www/discourse/lib/post_creator.rb:106:in `valid?'
/var/www/discourse/lib/post_creator.rb:114:in `create'
/var/www/discourse/lib/new_post_manager.rb:150:in `perform_create_post'
/var/www/discourse/lib/new_post_manager.rb:123:in `perform'
/var/www/discourse/app/controllers/posts_controller.rb:114:in `create'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/abstract_controller/base.rb:189:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/rendering.rb:10:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:552:in `block (2 levels) in compile'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:502:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:502:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:86:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/notifications.rb:159:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/notifications.rb:159:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/abstract_controller/base.rb:136:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.10/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.6/lib/mini_profiler/profiling_methods.rb:77:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal.rb:232:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:82:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:82:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/journey/router.rb:73:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/journey/router.rb:59:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/journey/router.rb:59:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:692: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.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/builder.rb:59:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/conditionalget.rb:35:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/head.rb:11:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:124:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/flash.rb:254:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.16/lib/message_bus/rack/middleware.rb:60:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/session/abstract/id.rb:225:in `context'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/session/abstract/id.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/cookies.rb:562:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract/connection_pool.rb:621:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:82:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/remote_ip.rb:76:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-0.8.4.8.pre/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/rack/logger.rb:22:in `call'
/var/www/discourse/config/initializers/quiet_logger.rb:10:in `call_with_quiet_assets'
/var/www/discourse/config/initializers/silence_logger.rb:26:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/methodoverride.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/runtime.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/sendfile.rb:112:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.6/lib/mini_profiler/profiler.rb:170:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:72:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/engine.rb:514:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/application.rb:144:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/railtie.rb:194:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/builder.rb:138:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/urlmap.rb:65:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/urlmap.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/urlmap.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:576: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-4.8.3/lib/unicorn/http_server.rb:670:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:525:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:140:in `start'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/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>'

Do you have any idea ?

Thx

Posts: 3

Participants: 2

Read full topic

↧

Signup call-to-action when you read for a while

August 17, 2015, 4:34 pm

≫ Next: Badge based on User Account Creation Date

≪ Previous: Error 500 when we post new message

@riking wrote:

When people browse around reading topics anonymously, they aren't getting their read time saved to the server, and their visits don't count for promotion. But most importantly, the last read position doesn't get saved, so they don't enter where they left off.

I want to let these people know what they're missing out on.

When logged in as anon, instead of throwing out post read time data, save it to localStorage.

Save visits to localStorage too (one per calendar day).

On the second visit if read time was already >=10 minutes, or immediately when read time is >= 30 minutes, pop up a call-to-action explaning the benefits of logging in and signing up for an account.

This needs to be disabled on sites that are: invite only, login required, must approve users. TODO: Should it be disabled with SSO? Probably not.

Proposed copy

Not sure which style is better. Patches welcome

On a "visit" (full page load >24 hours after the first one)

Hey, welcome back! You've read quite a few posts, but you're not signed up for an account, so you're missing out. Logged-in users get their last post position saved in every topic, and you can track topics so that they're highlighted in the list when there's new posts. Why not create one now?
Click to hide forever.

When read time hits 30 minutes:

Sorry to interrupt your reading, but you've been missing out. If you sign up for an account, when you come back, the page will pick up where you left off, along with lots of other cool features, including notifications for new posts in threads you care about.
Don't worry! We'll remember where you are right now and make sure to bring you right back.
Sign me up! Maybe Later Never show this again

Concerns:

If the activation is too touchy, we'll annoy drive-by visitors.

Need to add a new facility (that's not the bootbox modal) for a popup that doesn't block you from continuing to use the site.

Posts: 5

Participants: 4

Read full topic

↧

Badge based on User Account Creation Date

August 17, 2015, 6:55 pm

≫ Next: What hashing algorithm is used in discourse for hashing passwords?

≪ Previous: Signup call-to-action when you read for a while

@Umbrella wrote:

I wanted to make a badge for every user whose account was created before 7/14/2015. Lurking around Discourse meta has been incredibly helpful, so I figured I'd just hop in and ask for help!

Posts: 1

Participants: 1

Read full topic

↧

What hashing algorithm is used in discourse for hashing passwords?

August 17, 2015, 11:41 pm

≫ Next: Please don't pressure self-installers to be on Beta branch

≪ Previous: Badge based on User Account Creation Date

@Mohit_Gupta wrote:

what hashing algorithm is used in discourse for hashing passwords?

Posts: 2

Participants: 2

Read full topic

↧

Please don't pressure self-installers to be on Beta branch

August 18, 2015, 1:58 am

≫ Next: Meta Documentation - Table of Contents

≪ Previous: What hashing algorithm is used in discourse for hashing passwords?

@erlend_sh wrote:

codinghorror:

(...) But you should be on 1.4 [BETA] anyway, all our customers are.

I've heard this a couple times now, and understand where you're coming from, but being on Beta is not doable for us. We have no dedicated sysadmin or web developer who can attend to the plethora of smaller things that can pop up on the Beta branch:

Theme-breaking updates

UX changes that we'd like reverted

Plugin incompatibilities

I also like knowing what's coming. It allows me to tease new features to our users, and plan new workflows.

Every tech-savvy person knows that "Stable" is the place to be if you want the least amount of surprises, which is ideal if you have very limited resources dedicated to maintenance. As long as Discourse has a Stable branch, that's what we'll be using.

If supporting the Stable branch is a problem for you, it shouldn't exist as an option.

Posts: 5

Participants: 3

Read full topic

↧

Proposed copy

Latest Images