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

Enable voting just for certain group of people

0
0

@leog wrote:

Hello.

I was wondering if there is a way, even if it’s not official, to enable the plugin for just a few users.

We have a specific need to enable voting for affiliates, who fulfills certain criteria. Would be nice to be able to create some kind of group and just enable the plugin for them only.

Thanks a lot in advance.

Posts: 2

Participants: 2

Read full topic


How to set the /categories page as the homepage

Custom reason flagging UI issue using iPhone SE/5x

0
0

@ljpp wrote:

Raising a flag with more than one row of issue description causes issues with iPhones that have the classic low-res display. This includes the rather recent SE model (still sold) and the 5x series that has a huge install base.

The button to send the report falls below the screen and scrolling is impossible.

Posts: 1

Participants: 1

Read full topic

Problem about name and surname information after import

0
0

@bekircem wrote:

Hi,

I’ve imported my forum Mybb to Discourse. Before the “@” mark on users email addresses automaticly fill the name and surname information. And these informations can be seem on the users profile page. This is a little problem for privacy. Because user’s email addresses predictably by other users. How can i delete this in a mass?

Posts: 1

Participants: 1

Read full topic

Enterprise Theming for Discourse

0
0

@CarsonWeitnauer wrote:

What would you like done?

I am considering using Discourse for our organization’s community platform. We are a global nonprofit with professional branding and a commitment to excellence. I am looking for an established design firm that specializes in Discourse installations. It would be helpful to see a portfolio of completed work and testimonials from clients. I would appreciate referrals and/or people letting me know that they or their organization does professional Discourse installation and theming.

When do you need it done?

Once the right firm is selected, we can agree on a timeline that fits your availability.

What is your budget, in $ USD that you can offer for this task?

I am accustomed to working through a design brief and receiving a quote from the designer/firm on the cost of implementing the design.

Posts: 4

Participants: 4

Read full topic

Subfolder with SSL and nginx reverse proxy

0
0

@Ironclad14 wrote:

Hey guys,

I looked around but I couldn’t see a guide on how to host Discourse on domain.com/forum with SSL, using nginx as a reverse proxy. Currently, I’m running the forum on a subdomain - forum.domain.com and What I have in mind is, I’ll use nginx to secure the connection between the user and my server, and then call discourse locally unsecured via reverse proxy since they’re on the same machine, as per the latest set up tutorial.

I already have Ghost running the same way, and it works flawlessly.

This is my old location statement for the reverse proxy for forum.domain.com and it worked, though not securely.

#       location / {
#               proxy_pass http://unix:/var/discourse/shared/standalone/nginx.http.sock:;
#               proxy_set_header Host $http_host;
#               proxy_http_version 1.1;
#               proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
#               proxy_set_header X-Forwarded-Proto $scheme;
#       }
}

When I set this same proxy pass on location /forum in the main server block, I’m getting 404 errors for all assets, even though they’re being loaded via /forum/

location /forum {
        proxy_pass http://unix:/var/discourse/shared/standalone/nginx.http.sock:;
        proxy_set_header Host $http_host;
        proxy_http_version 1.1;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;

}

The error console shows these assets are missing:

Strangely enough, the 404 pages almost work consistently, but are still missing image assets:

What I also notice is that when I do discourse remap domain.com/ domain.com/forum, there’s an error remapping theme_fields

image

Is there a way I can check these rows specifically and see what the problem is?

The easiest solution would be a wildcard certificate but that’s beyond my budget range at this point.

Any help would be appreciated and I do apologise if this issue was already resolved elsewhere, I just couldn’t find this specific scenario.

Update: Here’s the env variables in app.yml

env:
  LANG: en_US.UTF-8
  # DISCOURSE_DEFAULT_LOCALE: en

  ## How many concurrent web requests are supported? Depends on memory and CPU cores.
  ## will be set automatically by bootstrap based on detected CPUs, or you can override
  UNICORN_WORKERS: 8

  ## TODO: The domain name this Discourse instance will respond to
  DISCOURSE_HOSTNAME: legiochristi.com
  DISCOURSE_RELATIVE_URL_ROOT: /forum

  ## Uncomment if you want the container to be started with the same
  ## hostname (-h option) as specified above (default "$hostname-$config")
  DOCKER_USE_HOSTNAME: true

Posts: 8

Participants: 2

Read full topic

Mixed up urls in emails with multiple discourse instances

0
0

@Christoph_Holtermann wrote:

I’ve installed two discourse sites on one server.

I’ve got these containers

  • web-only 1
  • web-only 2
  • redis
  • database

Emails coming from one site somtimes contain urls of the other site. For example an email about making a user an administrator had a link to the other site. When I manually changed the link I could confirm the administrator.

Could it be something about redis mixing up contents ?

Posts: 1

Participants: 1

Read full topic

Botched upgrade left me locked out

0
0

@Fsantiago wrote:

Hello,

i ran git pull on /var/discourse

then ran ./launcher rebuild app

no problem.

some time later, i visited /admin/upgrade, and started an upgrade from there manually. i closed my browser window before it finished.

now, while i was still “logged in” to my site as admin, and trying to visit my preferences page, i receive a page not found or private message. i logged out.

now, on trying to re-login, i receive unknown error.

i enter my app, tail the production log and see this:

Started GET “/session/csrf?=1504731633203" for 108.53.239.102 at 2017-09-06 21:00:36 +0000
Processing by SessionController#csrf as /
Parameters: {"
”=>“1504731633203”}
Completed 200 OK in 2ms (Views: 0.3ms | ActiveRecord: 0.0ms)
Started POST “/session” for 45.33.82.183 at 2017-09-06 21:00:36 +0000
Processing by SessionController#create as /
Parameters: {“login”=>"<user_ID>", “password”=>"[FILTERED]"}
Completed 500 Internal Server Error in 234ms (ActiveRecord: 28.1ms)
NoMethodError (undefined method alias_level' for #<Group:0x007f1a80e14a50>) /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activemodel-4.2.9/lib/active_model/attribute_methods.rb:433:inmethod_missing’

what could have happened? Thanks.

the site is still up & running otherwise but i cannot login.

Posts: 5

Participants: 3

Read full topic


Arabic translation

0
0

@Mohamed_farahat wrote:

hi @codinghorror
i need to launch my site quickly, but Arabic translation suffers from several issues.
first: it’s not complete
second: some word translated badly
third: Anas Ajlan not the perfect person for reviewing the translations :disappointed:

as you know i can’t change reviewed word but some of it translated very badly by Anas Ajlan
i want to make my translation without any restrictions, i does not mind to share it with the community by i can’t wait for reviewing and updating

please tell my how i can do that and make a poll about Anas Ajlan behavior.

Posts: 1

Participants: 1

Read full topic

Emails not going through

0
0

@gaurav18 wrote:

Dear Discourse experts, Can you please help me with this.

I installed discourse on Ubuntu. Discourse has come up in http.
However emails are not going through and I am not able to register as admin.

my container/app.yml has

DISCOURSE_SMTP_ADDRESS: smtp.gmail.com
DISCOURSE_SMTP_PORT: 465
DISCOURSE_SMTP_USER_NAME:
DISCOURSE_SMTP_PASSWORD: “…”
#DISCOURSE_SMTP_ENABLE_START_TLS: true # (optional, default true)

and email logs says something like this
Any help is highly appreciated.

Started PUT “/finish-installation/resend-email” for 127.0.0.1 at 2017-09-06 22:53:15 +0000
Processing by FinishInstallationController#resend_email as HTML
Parameters: {“authenticity_token”=>“8SGQcDAZ2FxoBv7g5IVY2z6j2uuJu6ieJQjJaBeBen6fbxf40PJnXCav59DTqHdXIGEGuW5NoArYD4SpIkCK/A==”}
Rendered finish_installation/resend_email.html.erb within layouts/finish_installation (0.5ms)
Rendered common/_special_font_face.html.erb (0.1ms)
Rendered layouts/_head.html.erb (7.8ms)
Completed 200 OK in 183ms (Views: 10.1ms | ActiveRecord: 3.2ms)

Sent mail to gaurav.negi@gmail.com (10124.8ms)
Job exception: end of file reached

Posts: 3

Participants: 3

Read full topic

Brand new instance consuming 35GB

0
0

@nixie wrote:

Hi,

I created a new staging instance at DigitalOcean.
Initially I bought the 20GB instance.
2 hours ago, when I was doing a “./launcher rebuild app” it said I have less than 5GB free in root.

I tried:
apt-get autoclean
apt-get autoremove
cd /var/discourse
./launcher cleanup

But it didn’t make any difference. So I went ahead and upgraded my droplet to 30GB SSD droplet.
After the resize, I was having 14 GB free.

I started using it.
After 1 hour, its again showing me the same message while doing "./launcher rebuild app"
It says there is less than 5GB free. (And that is correct, there is just 3.5 GB free now)

In the last 1 hour or so, all I did was making some changes in one of my custom plugins and I was just doing an app rebuild. The changes that I was doing in the custom plugin was tiny code changes which won’t be consuming any storage space at all. So, I’m wondering if doing app rebuild is eating up the free space?

It is this directory that consumes 34 GB:
/var/lib/docker/aufs/diff

What was I actually doing:
I have a custom plugin, that adds few extra buttons in the composer toolbar.
And few minutes before this happened, all I did was this:

  1. Make code changes
  2. Do ./launcher app rebuild
    (I would have done this like 10 times in 30 minutes, anyone think this is what caused free space to be gone?)

Posts: 3

Participants: 2

Read full topic

Only showing the default avatar?

0
0

@Ironclad14 wrote:

Hey guys,

I recently migrated my discourse from a subdomain to a subfolder and all other assets work properly apart from the user avatars - no matter what image I upload, I always get this avatar - image

There are no errors on the profile page, it says the update is successful

I get the following errors in my error log:

Here’s the full stack trace of the last one:

/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/data_streaming.rb:68:in `send_file'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/instrumentation.rb:52:in `block in send_file'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/notifications.rb:164:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/notifications.rb:164:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/instrumentation.rb:50:in `send_file'
/var/www/discourse/app/controllers/uploads_controller.rb:64:in `block in show'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rails_multisite-1.0.6/lib/rails_multisite/connection_management.rb:71:in `with_connection'
/var/www/discourse/app/controllers/uploads_controller.rb:52:in `show'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/abstract_controller/base.rb:198:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/rendering.rb:10:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/callbacks.rb:117:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/callbacks.rb:505:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/callbacks.rb:778:in `_run_process_action_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/notifications.rb:164:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/notifications.rb:164:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/abstract_controller/base.rb:137:in `process'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.9/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.5/lib/mini_profiler/profiling_methods.rb:76:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal.rb:237:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/routing/route_set.rb:74:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/routing/route_set.rb:43:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/journey/router.rb:43:in `block in serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/journey/router.rb:30:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/journey/router.rb:30:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/routing/route_set.rb:817:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/builder.rb:63:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/conditionalget.rb:25:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/head.rb:13:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:149:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/flash.rb:260:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/session/abstract/id.rb:225:in `context'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/session/abstract/id.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/cookies.rb:560:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_record/connection_adapters/abstract/connection_pool.rb:653:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/callbacks.rb:88:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/callbacks.rb:778:in `_run_call_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/logster-1.2.7/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.9/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.9/lib/rails/rack/logger.rb:22:in `call'
/var/www/discourse/config/initializers/100-quiet_logger.rb:17:in `call_with_quiet_assets'
/var/www/discourse/config/initializers/100-silence_logger.rb:29:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/methodoverride.rb:22:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/runtime.rb:18:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/sendfile.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.5/lib/mini_profiler/profiler.rb:171:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.5/lib/message_bus/rack/middleware.rb:63:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:73:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.9/lib/rails/engine.rb:518:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.9/lib/rails/application.rb:165:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.9/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.9/lib/rails/railtie.rb:194:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/urlmap.rb:66:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/urlmap.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/urlmap.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:606:in `process_client'
/var/www/discourse/lib/scheduler/defer.rb:85:in `process_client'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:702:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:549:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:142:in `start'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.0/bin/unicorn:126:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:22:in `load'
/var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:22:in `<main>'

I just hope this isn’t the suffering @codinghorror referred to in my previous thread. :slight_smile:

Using the latest Discourse, no third party plugins, I have plenty of RAM available.

One more thing: Uploading images does appear to work (the file is on the system) but I get a 500 error code when I try to open it. Where can I check the specific error logs so I can put them here if needed?

Posts: 3

Participants: 2

Read full topic

The option to enforce tagging

0
0

@HAWK wrote:

I’ve requested in the past that there be a setting to enforce the use of at least one pre-existing tag when creating a topic.

I’m now aware of 3 separate use cases for this requirement (all current Discourse clients). More community structures are becoming reliant on tagging.

  • Communities that rely on tags for surfacing content.
  • Large communities that use complex tags and tag groups for their AI.
  • I’ve forgotten the details of the third one but I’ll edit it in.

These are creating a heavy mod load which feels a bit like an ambulance at the bottom of a cliff.

I’d love to see an optional setting to enforce tagging for new topics (from a dd-list of existing tags that are associated with the category).

I know that at least some of my colleagues are unconvinced but I’m keen to hear whether that’s because it’s a considerable amount of work or because no one has successfully put the case forward.

Other requests:
How to force a user to specify at least 1 tag?
Ability to require tags on new posts and ban certain tags
Require Tag to Post New Topic

Posts: 3

Participants: 3

Read full topic

Onebox links with ampersands don't encode correctly

0
0

@Chopper wrote:

Hello,
Is this a bug related to discourse or not ?

I try to past this link https://starcitizen.fr/Forum/viewtopic.php?f=33&t=7068&p=106852#p106852, but the onebox encode the & and the link is broken

Thanks

Posts: 1

Participants: 1

Read full topic

Show if I've responded to a topic?

0
0

@Stranik wrote:

I’m interested in the opportunity to show I answered or not . How best to implement this?

There is something simple that can be used immediately or necessary to make the request to the database plugin?

Posts: 1

Participants: 1

Read full topic


Admin/upgrade page not showing up

0
0

@jack2 wrote:

I’ve just deployed my first Discourse instance with docker.
Everything seems to be working fine, except the admin/upgrade page, which shows up blank and has the following error:

Uncaught TypeError: Discourse._registerPluginScriptDefinition is not a function
    at docker-manager-vendor-4dd192655476ad4a9594bf218c3aab34ac1ad23cf54be7bb7174b6f475e67e86.js:1
Uncaught TypeError: Discourse._registerPluginScriptDefinition is not a function
    at docker-manager-app-05126b4030cfb026187ab683ad137e7eb9ce4d8cd69e33734d1d17cf2171f7eb.js:1

Any hint?

Posts: 1

Participants: 1

Read full topic

Link to sub-category in group activity feed leads to an error page

0
0

@BaldvinTh wrote:

Greetings!

It appears that if a group feed includes a post from a sub-category, the category link itself will point to /c/:sub-cat instead of the intended /c/:parent-cat/:sub-cat. An example:

Team Activity feed includes a post from techAPJ in developers under howto. The link points to /c/devs instead of the intended /c/howto/devs

Repro steps:

  • Have a user in a group post in any sub-category
  • Go on to group’s activity feed
  • Click on category link for post
  • See error page Oops! That page doesn’t exist or is private.
  • Double check link, see it’s missing parent category from path

Posts: 2

Participants: 2

Read full topic

Change in tracking behaviour

0
0

@LeoMcA wrote:

Just noticed this today here on meta (though I might have no been paying enough attention previous days):

  • Set a category to tracking
  • Open a topic from /new from that category
  • Observe its tracking state is “Normal”
    • Previous behaviour was for this topic to now be “Tracking” - like the parent category

Not sure if this was intentional, but it smells like a regression to me.

Posts: 1

Participants: 1

Read full topic

Category copy in topic notification dropdown

Blank page after upgrade and javascript error

0
0

@hellekin wrote:

Hello. Latest build (commit 0adaa7c) brings it back after some years :wink:

It comes right after the discourse-presence plugin is integrated and enabled by default. Should I remove it from the list? I have renamed it so it looks like

I thought it failed because I changed the container configuration without running ./launcher rebuild app but then I ran it and:

I, [2017-09-07T12:41:47.226058 #14]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/discourse-presence.git
fatal: destination path 'discourse-presence' already exists and is not an empty directory.
I, [2017-09-07T12:41:47.232919 #14]  INFO -- :


FAILED
--------------------
Pups::ExecError: cd /var/www/discourse/plugins && git clone https://github.com/discourse/discourse-presence.git failed with return #<Process::Status: pid 159 exit 128>
Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn'
exec failed with the params {"cd"=>"$home/plugins", "cmd"=>["mkdir -p plugins", "git clone https://github.com/discourse/docker_manager.git", "git clone https://github.com/discourse/discourse-spoiler-alert.git", "git clone https://github.com/discourse/discourse-voting.git", "git clone https://github.com/discourse/discourse-solved.git", "git clone https://github.com/discourse/discourse-assign.git", "git clone https://github.com/discourse/discourse-presence.git", "git clone https://github.com/lidel/discourse-openstreetmap.git"]}
6cdaf8b12114762b0bc1f96f3f014e0ad5e356c24b49370812bd4513a147ce0f
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one

On the server-side nothing’s wrong. The /logs/report_js_error contains only OK which gives a syntax error. See screenshot below.

Posts: 11

Participants: 3

Read full topic

Viewing all 60309 articles
Browse latest View live




Latest Images