@jupper wrote:

Hello,

is it possible to turn off the search function for non members?

Posts: 2

Participants: 2

Read full topic

@Senthil wrote:

Started GET "/" for 8.25.197.27 at 2015-06-06 19:05:51 +0000

PG::ConnectionBad (FATAL:  the database system is shutting down
):
  config/initializers/quiet_logger.rb:10:in `call_with_quiet_assets'
  config/initializers/silence_logger.rb:26:in `call'
  lib/middleware/request_tracker.rb:64:in `call'

This is the failure I see the production.log.

I could not restart the postgresql database too. Any suggestions for troubleshooting and fixing this? I dont have a backup, yet.

Here is more information from the apache error log.

App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/postgresql_adapter.rb:888:in `initialize'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/postgresql_adapter.rb:888:in `new'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/postgresql_adapter.rb:888:in `connect'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/postgresql_adapter.rb:568:in `initialize'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/postgresql_adapter.rb:41:in `new'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/postgresql_adapter.rb:41:in `postgresql_connection'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:435:in `new_connection'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:445:in `checkout_new_connection'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:416:in `acquire_connection'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:351:in `block in checkout'
App 28223 stderr:   /opt/bitnami/ruby/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:350:in `checkout'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:265:in `block in connection'
App 28223 stderr:   /opt/bitnami/ruby/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:264:in `connection'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:541:in `retrieve_connection'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_handling.rb:113:in `retrieve_connection'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_handling.rb:87:in `connection'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/associations/join_dependency.rb:96:in `initialize'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/relation/finder_methods.rb:355:in `new'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/relation/finder_methods.rb:355:in `construct_join_dependency'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/relation/finder_methods.rb:286:in `exists?'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/lib/permalink_constraint.rb:4:in `matches?'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/routing/mapper.rb:37:in `block in matches?'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/routing/mapper.rb:36:in `each'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/routing/mapper.rb:36:in `all?'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/routing/mapper.rb:36:in `matches?'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/routing/mapper.rb:45:in `call'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/journey/router.rb:73:in `block in call'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/journey/router.rb:59:in `each'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/journey/router.rb:59:in `call'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/routing/route_set.rb:678:in `call'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/middleware/show_exceptions.rb:46:in `render_exception'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/middleware/show_exceptions.rb:35:in `rescue in call'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/logster-0.1.6/lib/logster/middleware/reporter.rb:23:in `call'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/rack/logger.rb:38:in `call_app'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/rack/logger.rb:22:in `call'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/config/initializers/quiet_logger.rb:10:in `call_with_quiet_assets'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/config/initializers/silence_logger.rb:26:in `call'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/middleware/request_id.rb:21:in `call'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/methodoverride.rb:21:in `call'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/runtime.rb:17:in `call'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/sendfile.rb:112:in `call'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.2/lib/mini_profiler/profiler.rb:193:in `call'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/lib/middleware/request_tracker.rb:64:in `call'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/engine.rb:514:in `call'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/application.rb:144:in `call'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/railtie.rb:194:in `public_send'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/railtie.rb:194:in `method_missing'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:138:in `call'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:65:in `block in call'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in `each'
App 28223 stderr:   /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in `call'
App 28223 stderr:   /opt/bitnami/ruby/lib/ruby/gems/2.0.0/gems/passenger-5.0.6/lib/phusion_passenger/rack/thread_handler_extension.rb:85:in `process_request'
App 28223 stderr:   /opt/bitnami/ruby/lib/ruby/gems/2.0.0/gems/passenger-5.0.6/lib/phusion_passenger/request_handler/thread_handler.rb:149:in `accept_and_process_next_request'
App 28223 stderr:   /opt/bitnami/ruby/lib/ruby/gems/2.0.0/gems/passenger-5.0.6/lib/phusion_passenger/request_handler/thread_handler.rb:110:in `main_loop'
App 28223 stderr:   /opt/bitnami/ruby/lib/ruby/gems/2.0.0/gems/passenger-5.0.6/lib/phusion_passenger/request_handler.rb:414:in `block (3 levels) in start_threads'
App 28223 stderr:   /opt/bitnami/ruby/lib/ruby/gems/2.0.0/gems/passenger-5.0.6/lib/phus
App 28223 stderr: ion_passenger/utils.rb:111:in `block in create_thread_and_abort_on_exception'
App 28223 stderr: Error during failsafe response: FATAL:  the database system is shutting down

Posts: 5

Participants: 2

Read full topic

@pl3bs wrote:

ProDiscourse Hosting

Battle tested and ready for prime time, went through the rounds all day and am ready to have some people check this out.

Visit: www.prodiscourse.com

• Low cost

  • Value Package: $7/m 7gb SSD

  • Deluxe Package: 11/m 11gb SSD

  • Professional Package: $15/m 15gb SSD

• Safe and reliable

  • SSL with all paid plans on our subdomains

  • Daily backups with all paid plans

  • Failover hosts

• Feature packed

  • Web Panel provides remote backups, restores, and reconfigurations of mail or hostname

  • Standard plugins with all packages, premium plugins on deluxe, and custom plugins on professional

FREE STARTER COMMUNITIES!!

Sign up for a free starter community and get your forums deployed in under 5mins. We give you a half year to enjoy the experience of Discourse software with our hosting solution and decide for yourself if it's worth it for you to pony up.

Visit: www.prodiscourse.com

Posts: 5

Participants: 3

Read full topic

@watchmanmonitor wrote:

I think I've posted about this before, but can't find it.

I've signed the CLA, and had pulls accepted, but my PR today is still marked as requiring action.

I made a bad pull request today, saw the bot deny it, so I re-signed again before I made the right PR.. still no change.

Let me know what I need to do to allow PRs from yesthtatallen to be Ok with the CLA?

Posts: 2

Participants: 2

Read full topic

@watchmanmonitor wrote:

I'd love to know.. in the welcome email, how many people have name which need "the" ahead of them?

I have a commit showing the changes I proposed:

Here are my two primary discourse, one does, one doesn't need it:

Watchman Community needs a "the"

Consultants Discuss doesn't need "the"

So, how many people do we have in each boat?

• I want "the "
• "the " would not work for us

0voters

Show results

Assuming this isn't a one-sided set of results, how should it be fixed?

• Make an optional "the "
• Add "the " and " forum"

0voters

Show results

I'd just put The Watchman Community but the t should be lower case in the middle of a sentence.

Posts: 4

Participants: 3

Read full topic

@norbauer wrote:

I'm curious whether there is a feature to allow one to quickly link to an article within one's Discourse forum by just typing part of it's title--something like the "at mention" system, but for existing articles by title rather than members' names.

If not, it could be really cool to have something like that, or even auto-complete in the link menu if you type words rather than a url starting with http.

Posts: 1

Participants: 1

Read full topic

@gordon_ryan wrote:

Is there any way to get a list of posts (not topics) along with the number of likes it's gotten? I want to keep track of which posts are tending to do well.

Posts: 3

Participants: 2

Read full topic

@peternlewis wrote:

It seems that a search for nothing returns no result, and adding qualifiers like category and user still return nothing (this is related to the issues described at Search sometimes tokenizes unique user names and some times does not).

One of my forum users wants to see all their posts in a particular category, so they search for:

username:myname category:mycategory

but that fails because there is no match.

A lousy workaround is to search for:

username:myname category:mycategory mycategory

Since mycategory always appears (or appears to appear) in the search matches, this finds everything.

But it seems to me that the search system should accept a search of only options.

Thanks.

Posts: 3

Participants: 3

Read full topic

@uwe_keim wrote:

When browsing a Discourse forum on iOS (Safari), I would love the share buttons for Twitter and Facebook not simply fire a HTTP(S) URL but instead somehow trigger the "native" built-in sharing to Facebook and Twitter.

I.e. it should launch the installed apps (if any) where I am already logged in.

Is such a thing possible?

Posts: 2

Participants: 1

Read full topic

@paxmanchris wrote:

On my site, lets say example.com, I have a link to my discourse site with a sso payload. For example discourse.com/session/sso_provider?sso=afjakfj&sig=sdjfsdkfj. After the user clicks this link, If the user is not logged on to Discourse, the user is first redirected to the discourse.com/login. When the user successfully enters their username and password, there is an ajax request in the background to the return_sso_url stored in the payload; the page then proceeds to redirect the user to the index of discourse.com. I expect the user to be redirected back to example.com.

For background see Using the Discourse SSO provider feature.

Posts: 2

Participants: 2

Read full topic

@Ajay_Jain wrote:

Does Discourse support delegated SSO. If yes then please share link to the documentation

Posts: 3

Participants: 3

Read full topic

@hoppc wrote:

hey all :),

first, discourse is great!!!
we use discourse since 6 month for a closed discussion. But now we find a problem for us. Because, unregistered users can use the search box / search api to search for users. Has anybody a idea, to deactivate the search box / search api for unregistered people?

thaaaanks a lot for feedback and help!

Posts: 3

Participants: 2

Read full topic

@lihay wrote:

Hi,

I tried to customize the banner topic image size, and couldn'd find a way to do it.
Also tried to find the relevant class in the code - nothing helped.

Tips anyone?

Thanks,
Li.

Posts: 2

Participants: 2

Read full topic

@eriko wrote:

The emails being sent to users are not changing day to day.
There is nothing of interest in the sidekiq logs except for the output of the backup process. It is possible that some task did not get added in a migration or something?

Things that could be wrong but I do not thing are:

• still v1.3.0.beta10 +23 as I only update every other week
• Bare metal install (why the above) but will be moving to docker in a month

Posts: 1

Participants: 1

Read full topic

@dmitry_fedyuk wrote:

Live example here: http://discourse.pro/t/33

The «Restrict Files» plugin allows you to restrict access to downloads (attached files) so only users of permitted groups can download files from your Discourse forum.
So you can sell digital content through your Discourse forum.
To receive payments from your customers you can use my another Discourse plugin «PayPal Buy Now».
Also you can offer your digital content for free, but only to members of permitted groups / trust levels.
So you can motivate your forum members to achieve the specified trust level to gain access to the downloads.

How it works (some screenshots)

1. A case with an anonymous visitor

discourse-restrict-files-plugin-16.png1067x704 98.8 KB

discourse-restrict-files-plugin-17.png1069x705 92.3 KB

discourse-restrict-files-plugin-18.png1060x716 111 KB

2. A case with a registered but not willing to pay forum member

discourse-restrict-files-plugin-20.png1102x660 79.9 KB

discourse-restrict-files-plugin-21.png1103x646 91.3 KB

discourse-restrict-files-plugin-22.png1096x698 89.1 KB

discourse-restrict-files-plugin-23.png1093x683 100 KB

3. A case with a paid forum member

discourse-restrict-files-plugin-11.png1070x527 78.6 KB

discourse-restrict-files-plugin-25.png1122x644 73.1 KB

discourse-restrict-files-plugin-30.png1127x821 113 KB

How to setup

Create a group

discourse-restrict-files-plugin-01.png758x489 52.3 KB

discourse-restrict-files-plugin-02.png693x510 38.2 KB

discourse-restrict-files-plugin-03.png946x775 78.7 KB

... or use an automatic group for a trust level

discourse-restrict-files-plugin-02b.png820x549 41.3 KB

discourse-restrict-files-plugin-02c.png650x803 51.6 KB

Add the paid customers to the group with download access

... either from the group page

discourse-restrict-files-plugin-04.png872x919 88.8 KB

discourse-restrict-files-plugin-05a.png942x890 86 KB

discourse-restrict-files-plugin-05b.png939x938 88.9 KB

... or from a customer page

discourse-restrict-files-plugin-06.png629x670 64.8 KB

discourse-restrict-files-plugin-07.png513x854 85.4 KB

discourse-restrict-files-plugin-08.png1070x672 82.4 KB

discourse-restrict-files-plugin-09.png972x610 70.3 KB

discourse-restrict-files-plugin-12.png1071x540 76.4 KB

Adjust the «Restrict Files» plugin settings

discourse-restrict-files-plugin-13.png1055x741 121 KB

discourse-restrict-files-plugin-14.png855x687 93 KB

discourse-restrict-files-plugin-15.png953x695 96.9 KB

That's all.

Posts: 1

Participants: 1

Read full topic

@BioLogosBrad wrote:

I'm the admin and moderator at discourse.biologos.org, a popular discussion site about faith and science connected to www.biologos.org. I was wondering whether there's any legal issues with the site title using the word "Discourse", and us referring to the page informally as the "Discourse" page. What sort of attribution should we use to make sure people know the Discourse engine isn't our own creation?

Posts: 5

Participants: 4

Read full topic

@andrenit wrote:

I understand the current Docker image has been conceived as a portable installation tool, so every setup is up-to-date, but this choice makes the image kinda useless for those who live behind corporate proxies/firewalls.

Please consider releasing a ready-to-use image (post-install) where particular settings can be provided at run time (actually this is how most images are usually set).

Posts: 2

Participants: 2

Read full topic

@AdamCapriola wrote:

I've had a moderator on my forum notice this happen twice now:

1. I create a message with Users A, B and C
2. I invite User D to the message
3. I invite User E to the message
4. User E receives no notification (bubble or email) of new replies in the message unless User D is the one replying (and it's a blue bubble notification, not green)

I have SSO enabled, which might be relevant, but I'm not sure — I used to temporarily disable SSO so I could invite users to messages and apparently it happened then too.

Posts: 2

Participants: 2

Read full topic

@codinghorror wrote:

Just capturing this as it is a target for Discourse 1.4.

Our hamburger menu should be a full-height, slide out from the right. Sort of how Google Inbox does it:

inbox-slide-out-hamburger.gif384x512 159 KB

This also implies search and notifications should maybe be full height slide outs, too -- search is absolutely a right hand panel in Slack, for example -- but let's cross that bridge when we get there I guess?

Posts: 7

Participants: 5

Read full topic

@strager wrote:

Here on Meta, I clicked on a link for a topic that has apparently been removed ( https://meta.discourse.org/t/category-specific-moderators-phase-2/21897) - the Spinner keeps going round and round as if something is loading and it took me a moment or two to realize that the title said Topic Not Found. Perhaps this could be updated so that SOMETHING loads (maybe an image of some sort and a sentence like "Sorry this topic wasn't found. Perhaps it has been removed or there is a typo in the address.") to help indicate to users that the link is no good?

Posts: 2

Participants: 2

Read full topic