Quantcast
Channel: Discourse Meta - Latest topics
Viewing all 60721 articles
Browse latest View live

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

$
0
0

@dandv wrote:

I'm getting the following error when calling the /posts.json API function with my admin API key:

NoMethodError (undefined method `title' for nil:NilClass)
/var/www/discourse/app/serializers/post_serializer.rb:93:in `topic_title'

If I call /posts/json without an API key, or with the API key of a non-admin user, the call succeeds. Using the API key of an admin user causes the API call to fail. Regenerating the key didn't help.

Error log trace:

Message (33 copies reported)

NoMethodError (undefined method `title' for nil:NilClass)
/var/www/discourse/app/serializers/post_serializer.rb:93:in `topic_title'
Backtrace

/var/www/discourse/app/serializers/post_serializer.rb:93:in `topic_title'
(eval):23:in `_fast_attributes'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:467:in `rescue in attributes'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:455:in `attributes'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:479:in `_serializable_hash'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:361:in `serializable_hash'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/array_serializer.rb:89:in `block in _serializable_array'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/array_serializer.rb:79:in `map'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/array_serializer.rb:79:in `_serializable_array'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/array_serializer.rb:73:in `serializable_array'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/array_serializer.rb:49:in `as_json'
/var/www/discourse/app/controllers/application_controller.rb:218:in `serialize_data'
/var/www/discourse/app/controllers/posts_controller.rb:57:in `block (2 levels) in latest'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_controller/metal/mime_responds.rb:217:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_controller/metal/mime_responds.rb:217:in `respond_to'
/var/www/discourse/app/controllers/posts_controller.rb:48:in `latest'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/abstract_controller/base.rb:198:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_controller/metal/rendering.rb:10:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.4/lib/active_support/callbacks.rb:117:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.4/lib/active_support/callbacks.rb:117:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.4/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.4/lib/active_support/callbacks.rb:505:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.4/lib/active_support/callbacks.rb:505:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.4/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.4/lib/active_support/callbacks.rb:778:in `_run_process_action_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.4/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.4/lib/active_support/notifications.rb:164:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.4/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.4/lib/active_support/notifications.rb:164:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.4/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/abstract_controller/base.rb:137:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.2.4/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.7/lib/mini_profiler/profiling_methods.rb:77:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_controller/metal.rb:237:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_dispatch/routing/route_set.rb:76:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_dispatch/routing/route_set.rb:76:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_dispatch/routing/route_set.rb:45:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_dispatch/journey/router.rb:43:in `block in serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_dispatch/journey/router.rb:30:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_dispatch/journey/router.rb:30:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_dispatch/routing/route_set.rb:821: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/builder.rb:59:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/conditionalget.rb:25:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/head.rb:13:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:122:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_dispatch/middleware/flash.rb:260:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.16/lib/message_bus/rack/middleware.rb:60:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:225:in `context'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_dispatch/middleware/cookies.rb:560:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.4/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:653:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.4/lib/active_support/callbacks.rb:88:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.4/lib/active_support/callbacks.rb:778:in `_run_call_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.4/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.4/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-1.0.0.3.pre/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.4/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.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.2.4/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/methodoverride.rb:22:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/runtime.rb:18:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/sendfile.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.7/lib/mini_profiler/profiler.rb:170:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:73:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.4/lib/rails/engine.rb:518:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.4/lib/rails/application.rb:165:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.4/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.4/lib/rails/railtie.rb:194:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/urlmap.rb:66:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:580: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.9.0/lib/unicorn/http_server.rb:674:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:529:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:140:in `start'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.9.0/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>'
Env

hostname	localhost-app
process_id	[113, 120]
application_version	fb4a40e628fab3489c145726706692f9d8332105
HTTP_HOST	discourse.quantifiedselfforum.com
REQUEST_URI	[/posts.json?api_key=xxx&api_username=dandv]
REQUEST_METHOD	GET
username	[dandv]
HTTP_USER_AGENT	[null, Wget/1.11.4]
HTTP_ACCEPT	[null, */*]
params
api_key	[xxx]
api_username	[dandv]

What I've done since the last successful use of the API:

  1. Upgraded Discourse to v1.5.0.beta2 +69
  2. Ran a bunch of failed imports.

Might the failed imports have left Discourse in an inconsistent state? How can I identify the culprit record?

How can I get the API working again?

Posts: 1

Participants: 1

Read full topic


How to search and filter solved/unsolved topics?

Is there any api to import discourse details using ruby

$
0
0

@boopathi_s wrote:

I have to import the discourse user details such as groups,categories,topics to discourse from Excel sheets.Is there any API for this.or any other way to do this.
Please suggest some ideas to do this.

Posts: 2

Participants: 2

Read full topic

Creating a survey for self-hosted Discourse communities

$
0
0

@erlend_sh wrote:

I'd like to put together a little survey for projects that are managing their own Discourse forum. Published results will be 100% anonymous.

I wanna know things like:

  • Who's their hosting provider?
  • How beefy is their hosting tier?
  • How much are they paying?
  • Who's paying the bills? (company, donations, private person)
  • What release channel are they on?
  • Are they using any plugins?
  • What's the rest of their web stack like?

There's no ETA for this yet.

Do you have any other questions in mind for such a survey?
Please note: I don't want it to take more than roughly 5 minutes to complete.

I run one such community myself, so I am genuinely curious to know how we match up against other communities such as ours. Are we the only ones using the Stable branch? I wanna know!

It'll also be beneficial for the Discourse team to learn more about how the trends of self-hosted installs match up against their own offering.

Posts: 3

Participants: 3

Read full topic

Combining wp-discourse with embed code?

$
0
0

@Swissendo wrote:

Hi! I've been using wp-discourse as a replacement for the default comments, and while the flexibility of the plugin is great for creating topics for new articles and associating the correct author to it, there's been some problems with syncing the comments back to Wordpress (responses aren't marked as such, certain images aren't displaying, groups aren't synced). Now, the plugin hasn't been updated for a while, so I've played around with the embed function of Discourse. This would indeed solve all of the mentioned problems, but falls short on linking the correct autor to the topic, a feature I'm quite fond of. Would it be possible to continue using the plugin for creating the topics, while using the embed code to pull the comments from them? With the current page URL in discourseEmbedUrl, the script wasn't able to do that for existing topics, so I'm not shure if I'm doing something wrong or if it's simply not possible. Thanks in advance for your help.

Posts: 1

Participants: 1

Read full topic

Report statistics

$
0
0

@ber-64 wrote:

Is there a doc describing each row of statistics page? Where should I look for uniq visit from not logged client? In the API section?

page_view_*reqs -- its mean number of open posts/profile page? When the post is long and have to be loaded when user scroll the page it is still one page view?

Posts: 1

Participants: 1

Read full topic

Bold and Italic in Chinese

$
0
0

@11122 wrote:

I am really confused with this editor, perhaps this is because I am a chinese.
Here is my problems:
1. bold and italic work only when the character before is space or paragraph begin. For example:


This seems reasonable in English since that you should bold a word not only part of a word. But, in chinese, all the words are together: 我是**中国人**. So when I want to type chinese, most of the time, bold and italic don't work.
2. image in bullet list always in a new paragraph. This creates problem when I want to realize a inline image like this:

Plus what I found before, I do not think this is a good editor. I think it will confuse most user when I click bold and two ** is added. For people who do not know mark down, what is this **?

I am a developer, not a hard core one, I found this editor hard to use. I love discourse, it is more advanced than most of the BBS. But I just can not understand why we need a geeky editor.

Thanks for your work, any way.

Posts: 7

Participants: 4

Read full topic

Unable to change title and category during moderation

$
0
0

@Mischief wrote:

As an admin for posts which need moderating I can not change the title or category until after moderation.

It would be great if we could if we could do it as part of the moderation process.

Posts: 2

Participants: 2

Read full topic


Returning User Education?

$
0
0

@roarkely wrote:

The "New User' education blocks are great! Could we also get "Returning User" education blocks? We've got two different ideas for how these could work:

Situation 1: User has been inactive in the community
If a user hasn't visited the site or replied by email in X days, the block could be displayed to them on login. They could be used to re-enforce community rules after a period of absence.

Situation 2: User hasn't visited after a set date
If a user hasn't visited the site after a particular date, the block would be displayed at login. This could be used to let them know of changes to the community rules, kind of like a 'terms of service' change, but friendlier.

Posts: 1

Participants: 1

Read full topic

Daily/Weekly email digest for only one category?

$
0
0

@ldecoursy wrote:

I'm confused by the settings for email digests as separate from the Watching/Tracking options.

I have community members that only want to receive an email digest of one category, not our entire Discourse instance.

Is there an easy way to explain how to do this, or to set it up on the backend?

Posts: 3

Participants: 3

Read full topic

Minimum trust level to download posts

$
0
0

@roarkely wrote:

What if the "Download My Posts" feature required a minimum level of user trust, configurable in the admin panel?

Use case:
In private communities, the appearance of these sorts of features can undermine the sense of confidentiality. However, the ability for users to bulk export the content they have contributed to the community is clearly valuable. As a compromise, what if this feature only because available once a user met a specific trust level?

Posts: 4

Participants: 4

Read full topic

10 accepted answer badge giving an error?

$
0
0

@Siraj_M wrote:

Recently we add answered solved plugin in our discourse forum and also add their badges as described here.

1 accepted badges working pretty good but 10 accepted answer badge (Tech Support) not working, it is returning error, see the below snapshot of the error.

We are using this code:

    SELECT id user_id, current_timestamp granted_at
FROM users
WHERE id  IN (
       SELECT p1.user_id
       FROM post_custom_fields pc
       JOIN badge_posts p1 ON p1.id = pc.post_id
       JOIN topics t1 ON p1.topic_id = t1.id
       WHERE p1.user_id <> t1.user_id AND
                    name = 'is_accepted_answer' AND
            p1.user_id IN (
                   SELECT user_id
                   FROM posts
                   WHERE :backfill OR  p1.id IN (:post_ids)
            )
        GROUP BY p1.user_id
        HAVING COUNT(*) > 9
)

Please help me because when we try to preview this code implementation so it is returning an error.
Thank you.

Posts: 5

Participants: 2

Read full topic

What do badge groups and groupings do?

$
0
0

@OnceWas wrote:

Continuing the discussion from Badge Groupings:

I have been adding to our badges, and I wanted to know what the badge groups/groupings do.

I can't find a way to isolate badges by group, I don't know what benefit there is to being able to sort the order of badge groups, and I'm not sure I want to find out what clicking on the 'x' in the badge group modal does by clicking on it :wink: Does the 'x' delete the group, or the group and its badges?

Posts: 3

Participants: 2

Read full topic

Consequences of using or bypassing Trust Levels for company/organization staff?

$
0
0

@jsick wrote:

At the Large Synoptic Survey Telescope we have recently setup a Discourse installation at https://community.lsst.org. We're using it for a dual role of hosting internal project discussions among LSST staff and also for supporting the community who will use our software and data.

Discourse's Trust mechanism is of course great for community users who we don't know. But I've gotten some flak from members of our LSST organization for applying that Trust Level mechanism to them as well (imagine for a moment a tenured astronomer in the project complaining that the forum doesn't 'trust' him enough yet to put an image on his post).

The remedy so far has been to assign all LSST staff to a LSST group, and then give that group a default Trust Level of 2. I'm tempted to relent and give all LSST staff trust level 4. After all, LSST staff have a professional reputation to uphold, so I'm not worried about spam in this case.

However, I also know that the Trust Levels exist to foster a well-functioning community. For instance, trust levels are tied to how much a person read and learns from the posts of others, rather than how loudly/frequently that person speaks. For LSST, this community-building aspect is very important because we're a large organization that works remotely from 5+ sites. Unlike a company, scientific projects like this are somewhat more democratically run, and so sometimes the only way to promote best practices is by example and invisible systems than top-down edicts.

Some my question is: if I bypass the trust levels for project staff, will there be repercussions to how the community of project staff grows on our Discourse site? I'd be curious to hear what @codinghorror thinks since I know he cares deeply about the sociology of online communities.

Posts: 6

Participants: 2

Read full topic

Login Screen Blanked - Help Diagnose


Vagrant based server failing on db:migrate

$
0
0

@kcoop wrote:

I just ran through the instructions in the developer guide to install an environment using a virtual machine with vagrant I found here.

In my newly created instance, after a bundle update, updating the database with rake like so

bundle exec rake db:migrate

generates the following error:

rake aborted!
NameError: uninitialized constant SiteSettings::DbProvider::RailsMultisite
/vagrant/lib/site_settings/db_provider.rb:52:in `current_site'
/vagrant/lib/site_setting_extension.rb:44:in `current'
/vagrant/lib/site_setting_extension.rb:96:in `block in setting'
/vagrant/lib/site_setting_extension.rb:93:in `synchronize'
/vagrant/lib/site_setting_extension.rb:93:in `setting'
/vagrant/lib/site_setting_extension.rb:151:in `client_setting'
/vagrant/app/models/site_setting.rb:18:in `block in load_settings'
/vagrant/lib/site_settings/yaml_loader.rb:29:in `block (2 levels) in load'
/vagrant/lib/site_settings/yaml_loader.rb:20:in `each'
/vagrant/lib/site_settings/yaml_loader.rb:20:in `block in load'
/vagrant/lib/site_settings/yaml_loader.rb:19:in `each_key'
/vagrant/lib/site_settings/yaml_loader.rb:19:in `load'
/vagrant/app/models/site_setting.rb:16:in `load_settings'
/vagrant/app/models/site_setting.rb:25:in `<class:SiteSetting>'
/vagrant/app/models/site_setting.rb:4:in `<top (required)>'
/vagrant/config/initializers/04-message_bus.rb:39:in `<top (required)>'
/var/lib/gems/2.2.0/gems/railties-4.2.4/lib/rails/engine.rb:652:in `block in load_config_initializer'
/var/lib/gems/2.2.0/gems/activesupport-4.2.4/lib/active_support/notifications.rb:166:in `instrument'
/var/lib/gems/2.2.0/gems/railties-4.2.4/lib/rails/engine.rb:651:in `load_config_initializer'
/var/lib/gems/2.2.0/gems/railties-4.2.4/lib/rails/engine.rb:616:in `block (2 levels) in <class:Engine>'
/var/lib/gems/2.2.0/gems/railties-4.2.4/lib/rails/engine.rb:615:in `each'
/var/lib/gems/2.2.0/gems/railties-4.2.4/lib/rails/engine.rb:615:in `block in <class:Engine>'
/var/lib/gems/2.2.0/gems/railties-4.2.4/lib/rails/initializable.rb:30:in `instance_exec'
/var/lib/gems/2.2.0/gems/railties-4.2.4/lib/rails/initializable.rb:30:in `run'
/var/lib/gems/2.2.0/gems/railties-4.2.4/lib/rails/initializable.rb:55:in `block in run_initializers'
/var/lib/gems/2.2.0/gems/railties-4.2.4/lib/rails/initializable.rb:44:in `each'
/var/lib/gems/2.2.0/gems/railties-4.2.4/lib/rails/initializable.rb:44:in `tsort_each_child'
/var/lib/gems/2.2.0/gems/railties-4.2.4/lib/rails/initializable.rb:54:in `run_initializers'
/var/lib/gems/2.2.0/gems/railties-4.2.4/lib/rails/application.rb:352:in `initialize!'
/var/lib/gems/2.2.0/gems/railties-4.2.4/lib/rails/railtie.rb:194:in `public_send'
/var/lib/gems/2.2.0/gems/railties-4.2.4/lib/rails/railtie.rb:194:in `method_missing'
/vagrant/config/environment.rb:5:in `<top (required)>'
/var/lib/gems/2.2.0/gems/railties-4.2.4/lib/rails/application.rb:328:in `require_environment!'
/var/lib/gems/2.2.0/gems/railties-4.2.4/lib/rails/application.rb:457:in `block in run_tasks_blocks'
Tasks: TOP => db:migrate => environment
(See full trace by running task with --trace)

I cloned the github repo from the instructions, and it's pristine. Is this a bug? Any thoughts on what I'm doing wrong?

Posts: 6

Participants: 4

Read full topic

Fresh Clean Install Of Discourse does not load using CloudFlare

$
0
0

@Zelakto wrote:

Hey, i'm using a clean install of Discourse on a droplet. After solving my issues with mail not working correctly, I am now able to login, however, as soon as I login I am prompted with this:

I have no idea what this is called, so I'm not sure what to look up in order to fix it. Any suggestions on what I should do? Thanks guys.

Posts: 4

Participants: 2

Read full topic

Rails Multisite still breaking build

$
0
0

@kcoop wrote:

Continuing the discussion from Upgrade failed after the recent today's commits: «cannot load such file -- rails_multisite»:

Not sure if this is the best way to report it, but I think so. See here:

I'm running in virtual box on OS X 10.11 Beta, FWIW.

Posts: 4

Participants: 3

Read full topic

Make Discourse play nice with the Wayback Machine

Menu items translation bug

Viewing all 60721 articles
Browse latest View live




Latest Images