@pitosalas wrote:

I am trying to get a new site going and as expected people are not visiting the site enough to see whatever activity may be happening.

In order to help the ignition of discussion I was thinking that it would be good if all my initial users receive email notifications of traffic.

Is there a way that I as admin can force that? Is there a way for me to change the default setting for email notification for new users? Thanks!

Posts: 1

Participants: 1

Read full topic

@boomzilla wrote:

Recently, when clicking on various navigation controls (i.e., a badge on a user card, red flag bubble above the hamburger menu) I go to that page, but I'm scrolled waaaaay down the page below any actual content. It looks like discourse is still working on building the view or something, and then I realize there's no spinner or anything so I scroll back up to the top.

This is a fairly recent thing, but it's very annoying.

Posts: 3

Participants: 2

Read full topic

@RaceProUK wrote:

This is a weird one.

Originally found at TDWTF. I'd post a link, but for some reason I can't?

Basically, there was a post with the raw of @­RaceProUK, which obviously shows as @­RaceProUK; I highlit that and hit the 'Quote Reply' button, and it created the quote, but didn't turn it into at @mention. But when I manually constructed the quote, I got the @mention.

Since I can't upload images, the ones I posted over on TDWTF will have to suffice; I included shots of both raw and cooked.

Posts: 3

Participants: 1

Read full topic

@gingerling wrote:

In a closed topic about tagger plugins it says there is an official plugin now so the topic is closed... but I can't find any info on "official plugins" and I have been looking for 20 mins..

Posts: 2

Participants: 2

Read full topic

@RaceProUK wrote:

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

Posts: 2

Participants: 2

Read full topic

@LuaTenshi wrote:

Now I am sure many people have heard about the GIFV feature on imgur. I was wondering if it would be a good idea to add this feature onto discourse, because I think it would make using gifs much cleaner and it would also give developers more options when it comes to animated things. (ex. Playback controls.)

Posts: 4

Participants: 3

Read full topic

@jesselperry wrote:

Is there anyway to customize Discourse to change the weekly Digest option to bi-weekly? I find that daily is too often and weekly is too infrequent. It seems bi-weekly would be the best. Indeed, my users have said as much.

Thanks!

Posts: 8

Participants: 3

Read full topic

@sam wrote:

I just released a new discourse docker base image, I recommend you all update to it because it includes a rather important change that ensures logfiles cycle correctly.

To update run:

cd /var/docker
git pull
./launcher rebuild app

Latest includes a special fix that means that in future, when you need to rebuild:

cd /var/docker
./launcher rebuild app

You get to omit the git pull.

Of course I am going to have to wait a year for everyone to get on latest... but hey... it is progress

Posts: 2

Participants: 2

Read full topic

@sam wrote:

I have temporarily set the category style on meta to bullet which @awesomerobot just added

Pasted image733x120 8.22 KB

I want to make sure we have all the styling right and the only way to ensure that is live with it.

Please reply here if you notice any alignment issues etc.

Posts: 7

Participants: 4

Read full topic

@sam wrote:

I am using default theme on meta at the moment while we sort out bullet styling. Of all my changes, the one I am missing most is the suppression of a:visited on the topic list. I just realized why dislike current behavior so much.

It is broken.

Let me explain:

• You visit a new topic
• You scroll all the way to the end and read the topic
• You hit back
• Topic is not considered "a:visited"
• You refresh
• Topic is still not considered "a:visited"
• You click on the topic again.
• You click back
• TADA we have an "a:visited"

I visited those two black topics on this actual browser.

This is plainly broken and confusing. Visited means you visited the topic twice, which is insane.

I think a:visited needs to die, if we have to replace it with a smarter cross browser thing, then ok, but current behavior is just crazy confusing.

(this issue is happening cause we never do a replaceState on the last post in a topic so its just not going to be in history, only way to get it into history is click to it from the topic list AFTER you read it)

cc @awesomerobot

Posts: 6

Participants: 5

Read full topic

@Crackmacs wrote:

hi

Similarly to the security settings, I would like to see a position field so we can easily change the badge positions within the page. I'll probably label them something more-fun in the future, but for now they're just a basic description.

For example I set up some badges for users to earn via their post count.

Pasted image1064x335 22.4 KB

If I add in some additional text, fixes the position where I intended it to be.

Pasted image1130x319 22.8 KB

Would just like more control over where they end up, or, please let me know if there's an easy way of naming things

Thanks guys

I love all the emoticons in Discourse btw

Posts: 3

Participants: 2

Read full topic

@chapel wrote:

All of those blank spots are dropbox image embeds.

This might not show

The Onebox embeds work in the preview pane though.

Posts: 4

Participants: 2

Read full topic

@erlend_sh wrote:

https://medium.com/disqus-words/we-re-still-building-disqus-72c4acd05c81

So far it looks very similar to muut.com. It's like the uncanny valley between Reddit and Discourse if you ask me. I'm probably just in my old internet-age already and "set in my ways", but whenever I see stuff like this I immediately scramble for the "flat/compact view" button.

Still looking forward to following this development though.

Posts: 2

Participants: 2

Read full topic

@SMT wrote:

Hello,

I am running a forum on mybb. I am a student so cant afford much money. Can anyone install discourse on digital ocean and import all the data from mybb?

I can pay $10 for this via PAYPAL.

Thank you.
Discourse is best I liked it very much..

Posts: 3

Participants: 2

Read full topic

@benito_m wrote:

I've followed the various discussions on the whys and wherefores of taking over the standard browser Ctrl-F behaviour and I think I have a slightly different problem.

It's not a beef with the Ctrl-F behaviour as such, but rather when Discourse displays its pop-up list of matches I can't see a way to step through them. Currently I seem to have to click one, committing me and removing the list of matches. I would find it very useful (certainly when Search this topic is checked) to be able to arrow up and down through the matches and have the page scroll underneath the pop-up.

At the moment trying to find the reply that mentions a certain word in a very lengthy topic is painful (unless I've missed some other method of doing this).

Posts: 2

Participants: 2

Read full topic

@ouroboros8 wrote:

I was changing some settings on my install but now I can't access the admin/site_settings page at all, and just get 500s.

The last thing I did before the issue was change the max post size setting to an arbitrarily large number (9999999999999999999).

As far as I can tell, all other pages on the site are working fine, including log pages, which tell me I'm getting an argument error:

ArgumentError (val)

Here's the backtrace:

/var/www/discourse/lib/site_setting_extension.rb:366:in `get_data_type'
/var/www/discourse/lib/site_setting_extension.rb:159:in `block in all_settings'
/var/www/discourse/lib/site_setting_extension.rb:157:in `each'
/var/www/discourse/lib/site_setting_extension.rb:157:in `map'
/var/www/discourse/lib/site_setting_extension.rb:157:in `all_settings'
/var/www/discourse/app/controllers/admin/site_settings_controller.rb:4:in `index'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/abstract_controller/base.rb:189:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_controller/metal/rendering.rb:10:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:229:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:229:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:86:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:86:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/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.9/lib/active_support/notifications.rb:159:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/notifications.rb:159:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/abstract_controller/base.rb:136:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.9/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.3/lib/mini_profiler/profiling_methods.rb:106:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_controller/metal.rb:232:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/routing/route_set.rb:82:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/routing/route_set.rb:82:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/routing/route_set.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/routing/mapper.rb:45:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/journey/router.rb:73:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/journey/router.rb:59:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/journey/router.rb:59:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/routing/route_set.rb:685: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/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.2/lib/rack/conditionalget.rb:25: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:123:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/flash.rb:254:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.6/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.9/lib/action_dispatch/middleware/cookies.rb:562:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/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.9/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:82:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/remote_ip.rb:76:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-0.1.8/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.9/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.9/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.9/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.3/lib/mini_profiler/profiler.rb:276:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:70:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.9/lib/rails/engine.rb:514:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.9/lib/rails/application.rb:144:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.9/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.9/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.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>'

Posts: 1

Participants: 1

Read full topic

@tobiaseigen wrote:

I'd like to find a way to default the view for all users to display "none" rather than "all" subcategories, when in a category. "all" would be an option they could select. Is there any way to achieve this?

Generally, my community is finding "none" as an option to select unintuitive.

Posts: 1

Participants: 1

Read full topic

@optimus wrote:

Hi all, I tried searching existing topics but couldn't find an answer on this. I made a new custom color scheme under /admin/customize/colors and things are almost how I want them but I noticed that the dark grey color I set for "secondary" is filling the entire background. What I would like is a separate color (e.g. white) in the background area behind the topic list. See screenshot. So the red highlighted area (1) I want the background to be white, and the area (2) highlighted in blue I want to be the dark grey color as shown.

Does anyone have any tips or guidance about how I can achieve this?

TIA,
Chris

forum_screenshot.jpg1332x363 64.1 KB

Posts: 1

Participants: 1

Read full topic

@DonGlover wrote:

During dns setup my cname autodiscover record was set to hosted-vh1.discourse.org for other purposes I need to set this to another address. Is there any reason I need to leave autodiscover configured to point to hosted-vh1.discourse.org ?

Posts: 1

Participants: 1

Read full topic

@Maestra_Powers wrote:

Wanna ask about phpBB 3 importer. It works fine, but I have a lot of posts on my forum.

And after about 60% it starts to go very slow. And it goes slower and slower. I tried this converter on test server before, it worked 4 days and I got to 74.8%. Over last night it was 0.3% progress so I aborted it.

My questions:
1. Will it start over and duplicate already converted posts if I'll abort it now and run again?
2. What's the best way to split this operation in half? I can split my phpBB database in half, but will importer work in two runs like this, and not messup first imported part when I'll start to import second one?

I think this questions adressed to @neil. Thanks.

Posts: 2

Participants: 2

Read full topic