David Krcek wrote:

Hi,

i'm unable to finish the installation. Discourse don't send any email to my mailserver.

./launcher testmail app
finished successfully, i've received the mail with the current configuration.
The following resent of admin confirmation fails and there are no entries in /var/log/mail.log

Env: Ubuntu 12.04 LTS, installation with docker. Any hint howto get the email working?

Posts: 4

Participants: 3

Read full topic

Christian Stewart wrote:

Hi,

I'm getting extreme CPU usage on my forum http://forum.d2modd.in

I've got a dedicated server with 8 CPU cores, and 64GB of ram. Every single core is maxed out with a unicorn worker (I'm running 8). Why is my very small forum using so much CPU?

Thanks,
Christian

Posts: 9

Participants: 5

Read full topic

Christian Stewart wrote:

Hi all,

I enabled SSO accidentally and logged off, now I can't log back in. How can I reset this setting without being logged in?

Thanks!

Posts: 5

Participants: 3

Read full topic

omfg wrote:

It seems it's the old issue that was closed here:

I get the same error and a workaround is to login, then topics can be accessed.
Without that,
I tried both Safari (latest on iOS 7) and Atomic Browser (same issue, same workaround works).

Posts: 3

Participants: 2

Read full topic

Rahul Dhingra wrote:

I am using Wordpress SSO plugin and just updated my instance and saw new "sign up" button but the issue is new account credential won't be recognised by wordpress user DB as a result user won't be able to sign in with his/her new account. So when using SSO, signup button should be disabled by default.

Pasted image912x97 148 KB

Posts: 8

Participants: 4

Read full topic

Alankrit Choudhary wrote:

Login button has Login via Facebook, google etc. which is basically a signup method. But the new signup button does not provide that ?

Posts: 2

Participants: 2

Read full topic

James Milligan wrote:

Repro:

1. Edit a category
2. Go to the settings tab
3. Link for Categories will be displayed in order of activity. To control the order of categories in lists, enable the "fixed category positions" setting points to /admin/site_settings/category/email

Should point to /admin/site_settings/category/basic

Posts: 3

Participants: 2

Read full topic

Martin Mac Donald wrote:

Hey good folks, I'm considering making the switch to discourse (from vB), my site relies on the user table in wordpress. (Thats something I'm not going to switch as I have SSO with a number of pieces of sofware on my site, and subscriptions, and billing etc.)

Im looking over options at the moment, but just a quick note here that the current implementation of the wordpress bridge causes some SEO issues, in that its just manufacturing duplicate content between multiple pages on your root domain and the discussion subdomain (or same domain if you're reverse proxying discourse in).

Has anyone worked out how to canonicalise discourse entries made by wordpress automation back to the original source, or at least add a noindex,follow tag?

(before anyone chips in with SEO advice, saying that dupe content isnt an issue, trust me, it is).

thanks!
M

Posts: 5

Participants: 5

Read full topic

Theron Boerner wrote:

Not a huge deal, but the icon set is pretty blurry. Are we not using svgs?

Posts: 7

Participants: 3

Read full topic

lid wrote:

View mode: Desktop

Only maximum of 18 avatars can be visible on the dekstop view on 1920x1080 screen. 24 avatars are added to the DOM and loaded in the json.

I am not sure if there is much benefit of loading 6 extra participants and render 6 extra views in the DOM if the elements will never be visible to the end user.

Pasted image713x167 54.1 KB

In this screenshot css modifications reval the hidden avatars on the 2nd line

Pasted image707x376 88.3 KB

Option 1:

make css modification that all loaded avatars will be visible, you can see how it will look on the 2nd image attachment above

section.avatars{
overflow:visible !important;
}
section.links{
clear:left;
}

Option 2:

Change the number of participants in the JSON to the ~maximum capacity of the container.

ps
The mobile view is actually capable of making all the avatars visible given the window width is sufficient.

Posts: 1

Participants: 1

Read full topic

James Milligan wrote:

Repro
1. User accepts invitation
2. Expand message list on your own account
3. Unable to mark notification as read since there's no link to follow (see this topic for why)

I wonder if it might make sense to point to /my/invited, the intention being the user can check the status of their invites (see when it was redeemed, and so on)?

Posts: 2

Participants: 2

Read full topic

wrote:

Hello, I've tried searching but I couldn't seem to find the info.

Is there a way to manually add users from the Admin page? LIke when you want to populate the forum with many users at once? Or does everyone have to go through the registration and verification process?

Posts: 3

Participants: 2

Read full topic

Travis wrote:

I can't seem to get the custome CSS/HTML changes I want to work. It seems like it's just straight up ignoring any body or html CSS (specially, a background-image).

Is this the case?

Posts: 1

Participants: 1

Read full topic

Phillip Kuoch wrote:

Hi,

I've just installed the Discourse plugin on my Wordpress and don't have any issues sending the posts over.

I was wondering if it was possible to show the full post instead of an excerpt? Also, would it be possible to show the featured image and images in the post as well? How would one do that?

Thanks!

Posts: 3

Participants: 3

Read full topic

Ahmad Suhendri wrote:

For now, default trust level description on badges page have a links to meta discourse.
I have non-english Discourse install, have a dedicated topic about trust level and have different settings on TL requirement.

Is there any simple way to remove the links or replace it to my own topic? or maybe it would be more awesome if we can edit all of the default badges description.

Posts: 3

Participants: 3

Read full topic

Anton wrote:

Being able to change CSS for the very first post in any topic might help to make pages look more like a blog with right comments.

I've noticed that the outer-most containers for posts in topics have ID = post-cloak-N N=1,2,3,...

Can I rely on this? Will the very first post always have id post-cloak-1?

Pasted image700x226 48.7 KB

Posts: 2

Participants: 2

Read full topic

Thomas Wilson wrote:

I'd like to use discourse comments in my ghost blog (using eviltrout's instructions here) -- until recently, this has been working smoothly as expected. After re-importing my blog content with slightly different slugs, it started complaining that the X-Frame-Options header on discourse was set to 'SAMEORIGIN', preventing any x-site communication.

I followed the instructions here: https://meta.discourse.org/t/x-frame-options-sameorigin-header-prevents-embedding/14928/6?u=trilson and the error has since disappeared, only to be replaced by another.

In my developer console, I now see a 403 Forbidden error:

GET http://discourse.muselive.com/embed/comments?embed_url=http%3A%2F%2Fghost.muselive.com%2Falbum-number-7-on-its-way-1393155960%2F 403 (Forbidden)

followed by:

Uncaught TypeError: Cannot read property 'forEach' of undefined
Uncaught TypeError: Cannot read property 'create' of undefined    discourse.muselive.com/assets/vendor-3c0b29078a0c6673dd5ae1991a1fc9a6.js:12

Could this be a problem with my ghost install or with discourse? Has anyone else come across this issue? Example page which doesn't work: http://ghost.muselive.com/album-number-7-on-its-way-1393155960/

Any help would be appreciated - thanks.

Posts: 2

Participants: 2

Read full topic

Sam Saffron wrote:

To repro (in chrome):

1. Open 2 browsers to try homepage
2. (browser 2) click on a topic
3. (browser 2) make a post
4. (browser 1) Click on the "1 new or updated topic"
5. (browser 1) click on topic
6. (browser 1) click back

On step 6 browser no longer makes a json call to "latest" meaning the page is out of date.

@eviltrout can you have a look cause I have been hitting this lots today.

Posts: 8

Participants: 4

Read full topic

Anton wrote:

F5 does not help.

Commit: 45faf07

NoMethodError (undefined method `id' for nil:NilClass)

Backtrace

/var/www/discourse/app/models/post_action.rb:193:in `create_message_for_post_action'
/var/www/discourse/app/models/post_action.rb:197:in `act'
/var/www/discourse/app/controllers/post_actions_controller.rb:17:in `create'
/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:in `process_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:in `block 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:in `call'
/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:in `call'
/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:149:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:149:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:166:in `call'
/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:in `call'
/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:in `call'
/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:in `call'
/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:in `call'
/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:in `call'
/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:in `call'
/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:in `call'
/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:in `call'
/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:in `call'
/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:in `call'
/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:in `call'
/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:in `call'
/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:in `process_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:in `block 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:in `instrument'
/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:in `process_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:in `process_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:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.1/lib/mini_profiler/profiling_methods.rb:108: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:in `dispatch'
/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:in `block 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:in `dispatch'
/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:in `block 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:in `call'
/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:in `call'
/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:in `call'
/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:in `call'
/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:in `call'
/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:in `call'
/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:in `call'
/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:in `call'
/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:35:in `call'
/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:in `call'
/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:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-0.9.5/lib/message_bus/rack/middleware.rb:55:in `call'
/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:in `call'
/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/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:in `call'
/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:in `run_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:in `call'
/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:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-0.1.4/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:in `call_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: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.4/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/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:in `call'
/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:300:in `call'
/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:in `call'
/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:in `method_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:in `block 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:in `call'
/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:in `process_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:in `spawn_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 `<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>'

Posts: 2

Participants: 2

Read full topic

James Milligan wrote:

I've put this as ux as I don't think it's a bug per se, but something that might want to be made a bit more "obvious" to end users.

Clicking "Create Topic" in a category where you don't have permission to do so (for example, blog or plugins here on Meta), still shows the editor, but with uncategorised as the category. Some (most?) end users won't notice this, so their post will end up in the "wrong" place.

Couple of options I can think of:

1. Hide the create topic button where a user doesn't have permission to create a topic
2. Throw up some sort of message (like the "Your topic is similar to..." box) notifying them that they can't post in the category, but can select another one

Thoughts?

Posts: 7

Participants: 3

Read full topic