Anton wrote:

On the home page, category links are like this:

http://kozovodstvo.info/category/potrebitelyam

On the categories page, however, category links are like this:

http://kozovodstvo.info/category/26-category/9-category

The most strange thing is that for some categories it is still okay on the categories page.
Why does it happen so?

Posts: 1

Participants: 1

Read full topic

Anton wrote:

When 2 colors are the same, it looks as a GUI-bug:

Posts: 1

Participants: 1

Read full topic

Anton wrote:

Currently it looks as if I (the admin) close the topic, the English message is posted automatically despite global forum language is set to Russian.

Posts: 1

Participants: 1

Read full topic

Anton wrote:

I find it very difficult to find the best text which will fit both the dropdown list (where I want it shorter to easy finding in the list) and the Categories page (where I want it more descriptive to ease user navigation, and because I have unused space anyway).

Posts: 1

Participants: 1

Read full topic

Anton wrote:

Is there a way to do it for the dropdown lists in the Topic Editor? Thanks.

Posts: 1

Participants: 1

Read full topic

Anton wrote:

My moderators find it very important to setup Categories page as the home page for our specific case; and, as a consequence, they want a few very important and attractive topics to be always shown in the list of topics in front of some categories.

Is it possible to do so?

Posts: 2

Participants: 2

Read full topic

Anton wrote:

Posts: 1

Participants: 1

Read full topic

Мария Сергеева wrote:

There is a badge (Nice/Good/Great Post) for a post that received many likes. I believe there should be something like badge that is awarded for topic that received many replies, or views, or likes, or some combination of them to inspire good topic creation.

Posts: 2

Participants: 2

Read full topic

Marlon Wiebe wrote:

Hi there! Love Discourse, just installed it on it's own Ubuntu 14.04 Digital Ocean droplet with Docker. A friend of mine installed an oauth Doorkeeper plugin so that we can use our own account system.

Everything's working great, it will save drafts of posts and save them for the next time, but when I click create post, it hits me with an internal server error 500. I'm not a ruby developer at all, so pretty new at all this. I just upgraded to the most recent version of Discourse from the Admin tab, but hadn't tried posting before the update, so I'm not sure if that's the cause or not.

After a bit of googling and looking around the Discourse Meta, the only thing I could find was that I can get logs from forum.winnitron.com/logs in the URL bar. Here's some errors that pop up when I go to /logs:

--

I thought the backtrace tab might be helpful as well:

at /var/www/discourse/plugins/discourse-doorkeeper-sso/assets/doorkeeper.js:4:23
at /var/www/discourse/plugins/discourse-doorkeeper-sso/assets/doorkeeper.js:48:4
/var/www/discourse/lib/pretty_text.rb:93:in block in create_new_context'
/usr/local/lib/ruby/2.0.0/set.rb:232:ineach_key'
/usr/local/lib/ruby/2.0.0/set.rb:232:in each'
/var/www/discourse/lib/pretty_text.rb:87:increate_new_context'
/var/www/discourse/lib/pretty_text.rb:114:in block in v8'
/var/www/discourse/lib/pretty_text.rb:112:insynchronize'
/var/www/discourse/lib/pretty_text.rb:112:in v8'
/var/www/discourse/lib/pretty_text.rb:134:inblock in markdown'
/var/www/discourse/lib/pretty_text.rb:299:in block in protect'
/var/www/discourse/lib/pretty_text.rb:297:insynchronize'
/var/www/discourse/lib/pretty_text.rb:297:in protect'
/var/www/discourse/lib/pretty_text.rb:133:inmarkdown'
/var/www/discourse/lib/pretty_text.rb:172:in cook'
/var/www/discourse/lib/composer_messages_finder.rb:31:incheck_education_message'
/var/www/discourse/lib/composer_messages_finder.rb:10:in find'
/var/www/discourse/app/controllers/composer_messages_controller.rb:9:inindex'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_controller/metal/implicit_render.rb:4:in send_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/abstract_controller/base.rb:189:inprocess_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_controller/metal/rendering.rb:10:in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/abstract_controller/callbacks.rb:20:inblock in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:113:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:113:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:in block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:in block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:in block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:in block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:in block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:in block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:in block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:in block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:in block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:in block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:in block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:in block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:229:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:229:in block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:in block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:86:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:86:in run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/abstract_controller/callbacks.rb:19:inprocess_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_controller/metal/rescue.rb:29:in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_controller/metal/instrumentation.rb:31:inblock in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/notifications.rb:159:in block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/notifications/instrumenter.rb:20:ininstrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/notifications.rb:159:in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_controller/metal/instrumentation.rb:30:inprocess_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_controller/metal/params_wrapper.rb:250:in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.4/lib/active_record/railties/controller_runtime.rb:18:inprocess_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/abstract_controller/base.rb:136:in process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.4/lib/action_view/rendering.rb:30:inprocess'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.1/lib/mini_profiler/profiling_methods.rb:79:in block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_controller/metal.rb:196:indispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_controller/metal/rack_delegation.rb:13:in dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_controller/metal.rb:232:inblock in action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_dispatch/routing/route_set.rb:82:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_dispatch/routing/route_set.rb:82:indispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_dispatch/routing/route_set.rb:50:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_dispatch/journey/router.rb:71:inblock in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_dispatch/journey/router.rb:59:in each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_dispatch/journey/router.rb:59:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_dispatch/routing/route_set.rb:678:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-protection-1.5.2/lib/rack/protection/frame_options.rb:31:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/builder.rb:59:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/conditionalget.rb:25:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/head.rb:11:in call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:119:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_dispatch/middleware/params_parser.rb:27:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_dispatch/middleware/flash.rb:254:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:225:in context'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:220:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_dispatch/middleware/cookies.rb:560:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-0.9.4/lib/message_bus/rack/middleware.rb:55:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.4/lib/active_record/query_cache.rb:36:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:621:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_dispatch/middleware/callbacks.rb:29:in block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:82:inrun_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_dispatch/middleware/callbacks.rb:27:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_dispatch/middleware/remote_ip.rb:76:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_dispatch/middleware/debug_exceptions.rb:17:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.4/lib/action_dispatch/middleware/show_exceptions.rb:30:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-0.1.2/lib/logster/middleware/reporter.rb:23:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.4/lib/rails/rack/logger.rb:38:incall_app'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.4/lib/rails/rack/logger.rb:22:in call'
/var/www/discourse/config/initializers/quiet_logger.rb:10:incall_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.4/lib/action_dispatch/middleware/request_id.rb:21:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/methodoverride.rb:21:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/runtime.rb:17:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/sendfile.rb:112:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.1/lib/mini_profiler/profiler.rb:193:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.4/lib/rails/engine.rb:514:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.4/lib/rails/application.rb:144:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.4/lib/rails/railtie.rb:194:in public_send'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.4/lib/rails/railtie.rb:194:inmethod_missing'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:138:in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:65:inblock in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:50:incall'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.2/lib/unicorn/http_server.rb:572: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.2/lib/unicorn/http_server.rb:666:in worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.2/lib/unicorn/http_server.rb:521:inspawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.2/lib/unicorn/http_server.rb:140:in start'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.2/bin/unicorn:126:in'
/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'

--

And here's what pops up in Chrome's console:

Screen Shot 2014-08-04 at 11.20.13 AM.png1065x341 101 KB

--

Thanks in advance for any help! I really would like to get this working soon and I feel like we're so close!

Posts: 1

Participants: 1

Read full topic

wrote:

Is it possible to detect if a user is logged into Discourse from a PHP page and get a unique ID for that user?

Posts: 5

Participants: 4

Read full topic

Lisa Wess wrote:

We are interested in pulling out metrics on search terms - what is being searched for, with what frequency, and by whom? Most importantly: trending search terms.

Is there any current way to do this? Looking through the tables I wasn't able to locate anywhere that searches themselves were logged.

Is this something that is either currently possible or possible via plugin? Or even a planned feature, perhaps?

Thank you!

Posts: 1

Participants: 1

Read full topic

Anton wrote:

This happens right now in Discourse Meta.
I've even tried to switch between Latest and then again New a few times, but it does not help.

Posts: 5

Participants: 3

Read full topic

Anton wrote:

Looking to the forum from outside, I see very few busy elements and a very easy design, no matter which page:
the header, the menu, the table, and just a few types of updatable fields.

Could someone hint me to better understand why the whole templating language and that emberjs framework is in use?

I'm curious because [I've read somewhere here] they both are slow and all devs are waiting for updates with the hope the speed will increase considerably.

Is the main purpose of these libs to allow for easy templating and plugin writing?
If not, then what is the purpose of using both of them?

Currently, there are really few places where the data should be updated dynamically - and it's so easy to do it in just pure JS with JQuery.

I am not criticizing any decisions, but just coming from PHP + JS/JQuery with 10+ years of experience and have built tens of small and medium websites but never used any JS frameworks, and instant page reload was always much much faster than using such frameworks, so I'm just asking why with the hope to better understand the intention of developers.

To compare with what I'm used to seeing with PHP made by my collegues: 20-40ms server side + no or little processing time client side, so it's just super-fast and nobody never moaned about the speed of page load and rendering time.

I believe the same would be easily reachable with Ruby + Jquery, but there might be some drawbacks if the team decided to use additional heavy JS libs. Plus, having no ember would make entry point for potential plugin developers less requiring.

Not trying to be unkind! Please do not get me wrong. Just curious and want to know explanations behind the decisions. Thank you.

Posts: 3

Participants: 2

Read full topic

James Finstrom wrote:

Continuing the discussion from Reply to email - key in subject instead of email address?:

So it seems like an apps accounts don't like willy nilly reply-to: and I am not alone

When I look at the email sent to me it looks like the cookie idea from the first referenced post is somewhat in place:

In-Reply-To: <topic/23477@community.freepbx.org>
References: <topic/23477@community.freepbx.org>

Is there a plan to witch from email address (foo+id@bar.baz) processing to a header style processing for those of us that are protected from our selves by the big G.

Posts: 4

Participants: 2

Read full topic

Michael Downey wrote:

As a user, I want to see who started and/or participated in a topic that appears in my email digest, so I can better determine if I should go and read the topic(s) being described. The author or authors could be shown in the line below the topic title, or some other obvious/easy location.

The above user story came from one of our actual users (not me) but I agree with it so offered to post it here.

Posts: 1

Participants: 1

Read full topic

Thomas Smyth wrote:

Hello. I'm using ActiveAdmin as an admin panel for my plugin. In newer versions of Discourse I'm getting:

File to import not found or unreadable: active_admin/mixins.
Load paths:
  /Users/tomsmyth/Documents/sassafras-local/lena-mamykina/discourse/app/assets/stylesheets
  /Users/tomsmyth/Documents/sassafras-local/lena-mamykina/discourse/app/assets/stylesheets
...

The same path is repeated 37 times.

The offending code is in an app/assets/active_admin.css.scss file that ActiveAdmin added:

@import "active_admin/mixins";
@import "active_admin/base";

From what I can tell, the files are not being found because DiscourseSassImporter has its root parameter hard coded to the above value, so Sass::Tree::ImportNode is searching the same path 37 times. I'm not sure why this was done, but it seems that it's preventing Sass from searching all the correct load paths and resulting in the above error.

@neil, it appears you originally wrote the DiscourseSassImporter, and @eviltrout you've made commits to it. Can either of you offer any suggestions here? I would be much obliged.

Posts: 1

Participants: 1

Read full topic

PJH wrote:

The mobile/desktop swap link is missing from the hamburger menu if the client is thought to be either desktop or ipad.

Ref: http://what.thedailywtf.com/t/category-logo-max-height-not-on-mobile-css/2032/3

Posts: 1

Participants: 1

Read full topic

Michael Downey wrote:

I'm experimenting publishing blog posts to a private category until I can confirm things are working well. So far, I'm not having any luck in getting comments to come back to WordPress. (No problems publishing to Discourse.)

What's the best way to troubleshoot why comments aren't coming back? I don't see anything in the Discourse /logs page. Thanks in advance!

Posts: 4

Participants: 3

Read full topic

Jeff Atwood wrote:

Before any large scale changes I think we should first tone down the indicators on the "category" column of the categories page.

Of all the pain we have with these indicators this is the most egregious problem and unquestionably needs fixing.

Pasted image1069x1158 183 KB

We should start there.

Posts: 18

Participants: 7

Read full topic

wrote:

I'm confused on the process of changing the hostname?

I edited app.yml file with the new hostname but I don't know what to do next. I tried these instructions but my forums are unresponsive now.

When I ran ./launcher rebuild app I got these errors.

WARNING: No swap limit support
Updating discourse docker
error: cannot open .git/FETCH_HEAD: Permission denied

failed to update
Stopping old container

Posts: 4

Participants: 2

Read full topic