@will_io wrote:

Current Ember Release(s): 1.13.0, 2.0 beta (2015-06-12)
Current Discourse Ember version: 1.11.3

I was at an interesting talk in Chicago last night given by Erik Bryn, member of the core Ember team. He made it sound like the beta 2.0 released just last month was really meant to meet a self-imposed deadline they promised to their users and that version 2.1's release will be where we start to see a number of significant changes. Among other things here were some key highlights from the talk about 2.1:

Version 2.1:

• Angle bracket components: mustaches {{my-component}} will become angle brackets < my-component >
• Ember CLI will have more prominence (inspired by ReactJS, future collaboration with AngularJS)
• Will not support anything below IE9. Current version supports IE versions 7+

So in conjunction with these tid bits I wanted to bring a question to the Discourse team. Given that there is a new release of Ember every six weeks and the fact that Discourse is also updating at an extremely rapid rate, is it in the plans to keep 1.11.3 for a while until 2.x irons itself out? Or will you be updating incrementally toward 1.13 before you jump into 2.x? From reading other topics it was a mere 2 months ago Discourse moved to version 1.11 so even though I feel bad jumping the gun and "asking" -- not intending to push -- I feel it is relevant.

Posts: 2

Participants: 2

Read full topic

@Seungmin_Kim wrote:

Hello,

I have joined Korean translation, and it is now 99% and I'm acutally kind of afraid if there are some awkward, incorrect or improper translations among my works. As I only worked on less than 20%, I want to review others and also want others to review my works too. And, I have no idea how to review them in transifex. I wonder If I don't have permission to review now, or cannot find something like review buttons. (Sorry for poor english)

And if possible, I want to use unreviewed Korean translation at my Discourse, which is on DigitalOcean and using docker, to review this within public, before pull. Is there a right way to update translation files into docker?

Posts: 4

Participants: 2

Read full topic

@illspirit wrote:

If you search for anything with % in it and hit Enter, you get an error page.

Posts: 1

Participants: 1

Read full topic

@trandatnh wrote:

I've just upgraded discourse to latest version (53b0b70) and all the likes were missing from my posts

This topic on my forum has 241 likes but all the likes are disappeared from the posts

Note: I also upgrade discourse-solved and discourse-tagging

Pasted image692x432 23.9 KB

Posts: 7

Participants: 6

Read full topic

@cpradio wrote:

So there is a couple of us at SP who have been playing with a print media css queries to try and make Discourse more "printer friendly", so far we've come up with

@media print {
/* remove items N/A for print
** visual clutter etc. */
  .avatar,
  .topic-avatar,
  header,
  div.ember-view.topic-above-post-stream-outlet.topic-above-post-stream,
  div.ember-view.topic-map,
  section.ember-view.post-menu-area.clearfix,
  div#topic-footer-buttons,
  div#suggested-topics,
  div#progress-topic-wrapper,
  #topic-progress-wrapper,
  div.nums,
  ._flyout,
  .ember-view.btn,
  #topic-progress,
  .quote-controls,
  #topic-closing-info,
  div.lazyYT,
  .post-info,
  .saving-text,
  .draft-text,
  #discourse-modal,
  div.read-state,
  div.read-state.read,
  .edit-topic,
  a.reply-to-tab,
  a.reply-new,
  div.has-pending-posts,
  div.time-gap {
    display: none !important;
  }
/* bottom border to help separate posts */
  div.row {
    border-bottom: 1px solid #888;
    margin-bottom: -1px;
  }
  .cooked pre code { max-height: none; }
  #main-outlet { padding: 0 !important; }
  html,body { min-width: 0; height: auto; }
  .lightbox-wrapper img { max-width: 500px !important; height: auto !important; }
  .topic-body { width: auto; margin: 0; padding: 0; float: none; }
  .topic-post article.boxed .select-posts { width: auto; left: auto; right: 0; }
  .gap { width: auto; }
  .gutter { padding: 0; }
/* restyle div#topic-title */
  #topic-title {
    margin: 0;
    padding: 0;
  }
  #topic-title div div h1 {
    margin: 0 1em 0 0;
    padding: 0;
    float: left;
    font-weight: normal;
    font-size: normal;
  }
/* hide OP Solved plugin stuff */
  div.ember-view.topic-after-cooked-outlet.solved-panel {
    display: none;
  }
/* localhost  - MOOT for production */
  div.ember-view.topic-category-outlet.show-topic-category-location,
  div.alert.alert-info.alert-emails-disabled,
  div.profiler-results.profiler-left.profiler-no-controls {
    display: none;
  }
}

Is this something the Discourse Team would accept in a PR on common.scss? (or desktop.scss)

Posts: 19

Participants: 6

Read full topic

@Madhouse_ wrote:

I have a standalone authentication server that implements IdentityServer3 as an OpenID provider. It works well with existing clients and resources. I have an Angular-based application and a .NET API that both rely on it.

I am attempting to create a custom provider for Discourse that will allow users to login via this authentication server, or simply consent if already authenticated. To date, I have tried four different implementations:

1. Custom OmniAuth OAuth gem and provider (inheriting Auth::Authenticator)
2. Custom OmniAuth OpenID gem and provider (inheriting Auth::Authenticator)
3. Third-party OmniAuth OpenID gem (openid-reconnect)
4. Built-in Discourse OpenID Authenticator (Auth::OpenIdAuthenticator)

All fail with varying degrees of severity. I'm more than happy to post some of my defunct code to be judged by the community, but I'm hoping that someone here - and I'm guessing there's someone - has already done the research and implementation of this use case, and will be willing to go through it with me.

As all four of my attempts have failed, I am guessing that I am just missing some valuable, epiphany-spewing detail due to the lack of documentation. Kudos to the group working on the community documentation effort, by the way

Posts: 1

Participants: 1

Read full topic

@watchmanmonitor wrote:

It is not yet possible to update the image in a topic that's been moderated.

Pasting in a new (cleaned up) image doesn't work, and dragging the new image just replaces the current page.

Wanted to post this so it can get sorted in the queue.

Posts: 1

Participants: 1

Read full topic

@joshmings wrote:

What is the recommended process here?

Changing from something like forum.mysite.com to new.mysite.com.

Posts: 3

Participants: 3

Read full topic

@jeffwidman wrote:

Just got an email from meta for a thread I'm following. I'm no longer interested in this thread. So I looked for the unsubscribe link. I click it, and the only option I see results in unsubscribing from all emails, when all I want to do is unsubscribe from emails for that thread.

Yes, I am very aware this can be solved by just going to the thread itself and changing the 'watching' status, but I think using this messaging is confusing to users unfamiliar with Discourse. As an admin, I don't want users who are involved at the periphery of my community accidentally unsubscribing from all emails... those threads they're watching are the most likely hooks to bring them back to my community.

I much prefer how Quora solves this with two unsubscribe links. If I remember right, they have a big one that says 'to stop receiving emails for this thread, click here', followed by two line breaks followed by 'to unsubscribe from all emails from Quora click here.' That feels like a much more intuitive option for the end user, and as an admin I'm not worried about someone accidentally unsubscribing from all emails ever just because they couldn't find the button to unsubscribe from a particular thread.

Thoughts?

Posts: 3

Participants: 3

Read full topic

@RaceProUK wrote:

Whether you're searching for posts in a topic, a category, or made by a particular user, when you select the 'show more' link to go to the full-page search, that context is lost; it should be preserved, otherwise you're not doing the same search.

Posts: 4

Participants: 3

Read full topic

@dleung wrote:

Hi
Can someone tell me how (or is it possible) I can have all JS and CSS served from S3?
I'm currently hosted by Discourse.
Thanks!

Posts: 7

Participants: 2

Read full topic

@nigelb wrote:

I'm looking for a plugin that will allow a new user to sign up to a mailing list as part of their sign up process. I discussions elsewhere about something like this, but no one seems to have built it.

I'm probably going to give a shot at building it. Does anyone have pointers/gotcha's on how to go about this?

Posts: 2

Participants: 2

Read full topic

@strategeek wrote:

Hello. Our client is demanding functionality that a topic can be attached to more than one category. And then this topic should be repeatedly visible in all different categories pages that it is attached to.

I saw a big discussion here about this issue and I understand that this feature is not a part of Discourse forum and there are no plans to add it. Also we have considered tags, but it is far from perfect.

So we are left with the only option - to write a multiple categories plugin ourselves. As I have no experience in Ruby it means we will need to hire Ruby developer.

Can you write your opinion what can be the scope of this project, how difficult is it? Approximately how many hours it can take to develop a simple multi categories plugin for discourse?

Posts: 9

Participants: 2

Read full topic

@Mohit_Joshi wrote:

I have latest version of discourse installed. I am continuously getting memory error messages in logs:

Message

Errno::ENOENT (No such file or directory - tmp/letter_avatars/5_fcf819f9b3791cb8c87edf29c8984f83/S/241_157_191/20.png)Share Protect
Backtrace

/var/www/discourse/app/controllers/user_avatars_controller.rb:33:in ctime'
/var/www/discourse/app/controllers/user_avatars_controller.rb:33:inshow_letter'
/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:inprocess_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:inblock 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:incall'
/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:incall'
/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:inrun_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:inprocess_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:inblock 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:ininstrument'
/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:inprocess_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:inprocess'
/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:inblock 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:indispatch'
/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:incall'
/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:incall'
/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:ineach'
/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:incall'
/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:incall!'
/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:incall!'
/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:incall!'
/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:incall!'
/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:incall!'
/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:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/conditionalget.rb:25:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/head.rb:11:incall'
/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:incall'
/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.13/lib/message_bus/rack/middleware.rb:60:incall'
/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:incall'
/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:incall'
/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:inblock 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:incall'
/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:incall'
/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.3/lib/logster/middleware/reporter.rb:31:incall'
/var/www/discourse/config/initializers/silence_logger.rb:24:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/request_id.rb:21:incall'
/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:incall'
/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:incall'
/var/www/discourse/lib/middleware/request_tracker.rb:73:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/engine.rb:514:incall'
/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:inpublic_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:incall'
/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:ineach'
/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:inprocess_client'
/var/www/discourse/lib/scheduler/defer.rb:85:in process_client'
/var/www/discourse/lib/middleware/unicorn_oobgc.rb:95:inprocess_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:inspawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:536:in maintain_worker_count'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:294:injoin'
/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:inload'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in `'Share Protect
Env

HTTP_HOST: community.vuniquehotels.com
REQUEST_URI: /letter_avatar/subhasis121/20/5_fcf819f9b3791cb8c87edf29c8984f83.png
REQUEST_METHOD: GET
HTTP_USER_AGENT: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.132 Safari/537.36
HTTP_ACCEPT: image/webp,/;q=0.8
HTTP_REFERER: http://community.vuniquehotels.com/admin/email/all
HTTP_X_FORWARDED_FOR: 122.162.249.237
HTTP_X_REAL_IP: 122.162.249.237
username: rakesh

Rebuilding only temporarily solves problem. Also when this happens I am getting other errors also such as, blank dashboard, avatars/images are broken.

Sidekiq also shows that multiple processes are failing due to memory allocation.

Please help!!!

Posts: 5

Participants: 2

Read full topic

@manvfat wrote:

As described - del tags used to create strikethrough in the About Me section display in the profile view but not in the User Card view which pops up.

Example: This is my profile - http://www.talk.manvfat.com/users/admin/activity but go to the main forum http://www.talk.manvfat.com/ and pop my User Card and it doesn't display - links are fine but other HTML maybe not?

Posts: 2

Participants: 2

Read full topic

@Emily wrote:

Hi-

We've had a customer report that the 'new' tab isn't showing any posts when the running list of 'latest' topics has a number of topics she hasn't read, marked as 'new' in that view.

Any idea why this is happening? See image.

Pasted image1600x1200 108 KB

Thanks

Posts: 4

Participants: 3

Read full topic

@alefattorini wrote:

Continuing the discussion from Badges feedback:

Is it a plugin? I need it for my community! How can I add it to my installation? Does it work currently?
Thanks

Posts: 2

Participants: 2

Read full topic

@jtbayly wrote:

1. Create a group
2. Create a new category, and before saving it, try to limit permissions to the new group you just created.

You won't see the new group as an option, despite the fact that it's actually saved. It is not a reloading issue. The only way to do it is to create the category, then go in and edit it. Once you do that, the group will show up in the permissions list.

Posts: 1

Participants: 1

Read full topic

@jtbayly wrote:

1. When viewing a category, click the search button and type a word
2. Check the "search within "whatever" category
3. Hit enter (or click the "Show more" link)

The results are not limited to within the category, like you selected.

Posts: 4

Participants: 2

Read full topic

@jtbayly wrote:

1. do a search
2. On the results page, click the "Category" column header

It will not sort by category, like it should.

NOTE: This bug also affects the Replies column. However, the views and activities columns seem to work fine.

Posts: 6

Participants: 3

Read full topic