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

Google auth with https

0
0

Michael wrote:

One of our customers is trying to use https in conjunction with Google SSO.
The following happens:

Yes, https:// and an explicit port 80 !

  • user is presented an error message stating bad HTTPS, which is logical, given the fact that it is forced to port 80.

How to solve this? I can't really find where this port 80 is coming from. use_https does not fix it.

Posts: 3

Participants: 3

Read full topic


Entering titles on mobile

0
0

Johan wrote:

When creating new topics on a mobile phone (Galaxy S3 in my case), the title bar is invisible when the keyboard is brought up.
Before selecting:

https://www.dropbox.com/s/aqsekuqw2pepkpr/Screenshot_2014-02-27-10-53-03.png

When selected:

https://www.dropbox.com/s/7gnw3f5m842a5sf/Screenshot_2014-02-27-10-53-16.png

Possible fix would be shrinking the post input when title is selected? smile

Edit: It seems the images are not loading.. linking instead

Posts: 1

Participants: 1

Read full topic

ActionView::Template::Error: undefined method `strip' for #

0
0

Graeme Stuart wrote:

I'm getting this error in my sidekiq retries log and it seems to be stopping me from sending emails.

Worker: Jobs::UserEmail
Arguments: {"type"=>"digest", "user_id"=>12, "current_site_id"=>"default"}

I'm getting 78 failed jobs, with various user_ids (about 10 unique ids repeated) but the same type and current_site_id.

The stack trace from sidekiq:

/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/nokogiri-1.6.1/lib/nokogiri/html/document_fragment.rb:27:in `initialize'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/nokogiri-1.6.1/lib/nokogiri/html/document_fragment.rb:14:in `new'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/nokogiri-1.6.1/lib/nokogiri/html/document_fragment.rb:14:in `parse'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sanitize-2.0.6/lib/sanitize.rb:113:in `clean!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sanitize-2.0.6/lib/sanitize.rb:106:in `clean'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sanitize-2.0.6/lib/sanitize.rb:53:in `clean'
/var/www/discourse/app/helpers/user_notifications_helper.rb:63:in `email_excerpt'
/var/www/discourse/app/views/user_notifications/digest.html.erb:20:in `block in _app_views_user_notifications_digest_html_erb__424476827_113700390'
/var/www/discourse/app/views/user_notifications/digest.html.erb:15:in `each'
/var/www/discourse/app/views/user_notifications/digest.html.erb:15:in `each_with_index'
/var/www/discourse/app/views/user_notifications/digest.html.erb:15:in `_app_views_user_notifications_digest_html_erb__424476827_113700390'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.0.2/lib/action_view/template.rb:143:in `block in render'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/notifications.rb:161:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.0.2/lib/action_view/template.rb:141:in `render'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.0/lib/mini_profiler/profiling_methods.rb:79:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.0.2/lib/action_view/renderer/template_renderer.rb:49:in `block (2 levels) in render_template'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.0.2/lib/action_view/renderer/abstract_renderer.rb:38:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/notifications.rb:159:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/notifications.rb:159:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.0.2/lib/action_view/renderer/abstract_renderer.rb:38:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.0.2/lib/action_view/renderer/template_renderer.rb:48:in `block in render_template'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.0.2/lib/action_view/renderer/template_renderer.rb:56:in `render_with_layout'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.0.2/lib/action_view/renderer/template_renderer.rb:47:in `render_template'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.0.2/lib/action_view/renderer/template_renderer.rb:17:in `render'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.0.2/lib/action_view/renderer/renderer.rb:42:in `render_template'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.0.2/lib/action_view/renderer/renderer.rb:23:in `render'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.0.2/lib/abstract_controller/rendering.rb:127:in `_render_template'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.0.2/lib/abstract_controller/rendering.rb:120:in `render_to_body'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.0.2/lib/abstract_controller/rendering.rb:97:in `render'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.0.2/lib/action_mailer/base.rb:755:in `block in collect_responses'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.0.2/lib/action_mailer/base.rb:769:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.0.2/lib/action_mailer/base.rb:769:in `each_template'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.0.2/lib/action_mailer/base.rb:751:in `collect_responses'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.0.2/lib/action_mailer/base.rb:691:in `mail'
/var/www/discourse/lib/email/message_builder.rb:9:in `build_email'
/var/www/discourse/app/mailers/user_notifications.rb:55:in `digest'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.0.2/lib/abstract_controller/base.rb:189:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.0.2/lib/abstract_controller/callbacks.rb:18:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/callbacks.rb:373:in `_run__787781354__process_action__callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/callbacks.rb:80:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.0.2/lib/abstract_controller/callbacks.rb:17:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.0.2/lib/abstract_controller/base.rb:136:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.0.2/lib/abstract_controller/rendering.rb:44:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.0.2/lib/action_mailer/base.rb:503:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.0.2/lib/action_mailer/base.rb:497:in `initialize'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.0.2/lib/action_mailer/base.rb:480:in `new'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.0.2/lib/action_mailer/base.rb:480:in `method_missing'
/var/www/discourse/app/jobs/regular/user_email.rb:58:in `execute'
/var/www/discourse/app/jobs/base.rb:130:in `block (2 levels) in perform'

Any ideas?

Posts: 5

Participants: 3

Read full topic

POST to /admins/user/:user_id/generate_api_key requires X-CSRF-Token?

0
0

Stephen Birarda wrote:

We're planning on using discourse as a discussion forum for alpha users of our software.

Currently I've hooked up the official SSO plugin so that sign on is completed via our main site.

I want to be able to create an API key for the user to pass down to our application so that they can create posts from the application. I've figured out how to add users via the REST api (using the honeypot values) but can't seem to use the generate_api_key method in the Admin::UsersController.

It's telling me the route doesn't exist, but I've verified that it definitely does by looking at the request made from chrome when clicking on "Generate API key" for that user - although that request uses the CSRF token.

Is it possible to POST to the same API via JSON with a master API key?

Posts: 3

Participants: 2

Read full topic

Locally hosted images/theming with docker installed discourse

0
0

Brandon Mathis wrote:

Hi guys! Just got my Discourse instance up and running for my meetup Triangle.rb and I am in administration setup process.

I used Docker to install Discourse per the instructions here: https://github.com/discourse/discourse/blob/master/docs/INSTALL-digital-ocean.md

My question is, if I want to customize the layout of my site how would I go about doing that? Where is the code actually installed to?

If I want to do this much customization should I go ahead and do the advanced install?

Posts: 6

Participants: 4

Read full topic

Don't need a modal after flagging a topic

0
0

Kane York wrote:

After flagging a topic, an unnecessary modal pops telling me that I have "successfully flagged the topic". Yeah, thanks, I already knew that.

Posts: 8

Participants: 3

Read full topic

Please visit our Discourse Forum! (Directory)

0
0

F. Randall Farmer wrote:

I know I'd like to visit various new Discourse servers once in awhile as they come up. As you'd like a visitor or two, please post your URL here and a description of the purpose of your site and any other notes...

Posts: 77

Participants: 60

Read full topic

Ability to remove "in reply to" when editing posts

0
0

Gweebz wrote:

While using the http://discuss.atom.io/ instance of Discourse, I was reading through a topic. I thought I had reached the end and I wanted to reply to the topic as a whole. I hit the "Reply" button at (what I thought was) the bottom of the page. I quickly typed out my short reply and posted it. It wasn't until then that I noticed I actually clicked a "Reply" button on someone's specific post, not the topic as a whole. I tried to edit the post to remove the "in reply to" but I couldn't figure out how to do it.

I ended up deleting my original reply and creating a new one, using the correct button this time. When I went to post that reply (which I had just copied and pasted), I got the message "Body is too similar to what you recently posted."! I had to add an extra sentence at the end just to get around this.

I would like to see a feature added to allow us to change the "in reply to" of posts after they are posted, or remove it all together. If this feature does exist, I could not figure out how to do it, so maybe it could use some UI improvement to be more intuitive?

Posts: 2

Participants: 2

Read full topic


Odd browser in-page search behavior

0
0

Patrick Klug wrote:

I was just trying to search inside a topic using Chrome's own search feature (Ctrl+F) and got some very odd results.

Example:

  1. Go here. (using Chrome on Windows)
  2. Press Ctrl+F and search for 'quality'.

When I do this the result ranges from finding the first q, then stopping to closing the browser tab completely. Is this just a bug in Chrome or does Discourse incorrectly react to some keyboard shortcuts?

Posts: 3

Participants: 2

Read full topic

Global favourites aka "the best of"

0
0

Amit Friedmann wrote:

Hello, I've been running my own instance of the great and mighty Discourse and loving it! It's a website targeted to the Israeli community so I did some funky RTL and floating customisation to give it a better look and feel in hebrew and it works great. I've stumbled upon a missing feature that I was thinking as implementing myself as another custom UI, but before doing that I was thinking to raise it as a feature request: a global favourites drop down list in the header menu. A placeholder to put the best of the best posts anyone entered the forum should absolutely read. These are not pinned topics (that can be cleared) IMO that used more of of a set rules for the forum, but posts that had or still have mass effect. This is also not hot topics since those post can be already old and not updated frequently.
Some forums call it 'taglines', some just add custom menu with links.
Am I mixing too many different behaviours or does it makes sense?

Posts: 10

Participants: 5

Read full topic

Did a user delete themselves or did Discourse do it

0
0

eriko wrote:

So I am trying to figure out how 4 users were deleted. I have four records in the log that look like the image below.

They were all done sequentially in the log. They were created as part of a 6,000+ user tranche and not of the others are effected by this. It is possible that the users deleted themselves but in that case I would expect that it would be noted in the log.

Any thoughts.

Posts: 5

Participants: 3

Read full topic

Migrating an old Discourse install to Docker

0
0

Sam Saffron wrote:

Deploying Discourse on Docker is currently our recommended setup. It avoids many pitfalls installations have, such as misconfigured nginx, sub-optimal Ruby defaults and so on.

The Docker based setup ensures we are all on the same page when diagnosing installation issues and completely eradicates a class of support calls.

Today, all sites hosted by Discourse are on Docker.

This is a basic guide on how to move your current Discourse setup to a Docker based setup.

Getting started

First, get a blank site with working email installed. Follow the guide at https://github.com/discourse/discourse_docker and install a new, empty Discourse instance.

Tips:

  • Bind the web to a different port than port 80, if you are on the same box. Eg:

    expose:
      - "81:80"
  • Be sure to enter your email in the developer email section, so you get admin:

    env:
      # your email here
      DISCOURSE_DEVELOPER_EMAILS: 'my_email@email.com'
  • Make sure email is setup and working by visiting /admin/email and sending a test email.

  • Make sure you have ssh access to your container ./launcher ssh my_container must work.

If any of the above is skipped your migration will fail.

At the end of this process you will have a working website. Carry on.

Exporting and importing the old site

  • Ensure you are running the absolute latest version of Discourse. We had bugs in the export code in the past, make sure you are on latest before attempting an export.

  • On your current instance

    • go to /admin/backups and click on the button.
    • once the backup is done, you will be able to it.
  • On your newly installed docker instance

    • enable the allow_restore site setting
    • refresh your browser for the change to be taken into account
    • go to /admin/backups and your backup.
    • once your upload is done, click on the button
  • Destroy old container ./launcher destroy web

  • Change port binding so its on 80

  • Start a new container

Yay. You are done.

Posts: 9

Participants: 4

Read full topic

From where to access Discourse GUI

Funky header logo image bug

0
0

Lowell Heddings wrote:

I dunno what's going on, but a recent update seemed to break something for HTG. The logo is weirdly sized now when you scroll up.

Anyway, figured I'd mention.

Posts: 4

Participants: 3

Read full topic

Replacing Mailing lists: Email-In

0
0

Benjamin Kampmann wrote:

Hello everyone,

Update: I've finished developing this. You can find the entire patchset at the pull-request with the three features as three commits in the same order.

I am on the quest on supporting discourse to replace mailing lists (our internal google group system to be precise). One feature discourse is clearly missing to be able to replace mailing lists is to allow the creation of new topics via email. I call this Email-In. These are the three development steps I currently see:

1. General Email in

  1. let admins enable and define an incoming-email-address
  2. parse every email to the email-address in the POP3-account
  3. if it comes from a user of the forum and that user has a certain configurable trust level, post the message as a new topic in the forum

2. Email-In per Category

  1. to reduce the noise, we are using categories people can mute and such
  2. therefore it makes sense to allow to configure email-addresses per category if the general incoming-email-feature is enabled
  3. an email to that address then will be posted in that category instead of globally
  4. the privacy options for that category apply

3. Allowing "unknown" Email-In

  1. mailing lists are also sometimes configured as "a shared inbox", allowing third parties to post to it
  2. add another configuration option in the email-in-configuration (globally and per category) to allow emails from third-parties (off per default)
  3. when an email arrives in the inbox, that is not by any user known to the system, the header and its content will be posted as a quote in a new topic by the configured "system"-user
  4. also emails by users without the appropriate rights would be handled this way

Any feedback, ideas, features or other uses cases I might should consider, too?

Thanks
Ben

Posts: 10

Participants: 7

Read full topic


"Loading topic..." on /latest

Beginners Guide to Deploy Discourse on Digital Ocean using Docker

0
0

Arpit Jalan wrote:

The Discourse Docker Image makes it easy to set up Discourse on a cloud server. We will use Digital Ocean, although these steps will work on other similar services.

This guide assumes that you have no knowledge of Ruby/Rails or Linux shell. Feel free to skip steps you are comfortable with.

Create New Digital Ocean Droplet

Discourse requires a minimum of 1 GB RAM, and 2 GB RAM is recommended. We'll use "discourse" as the Hostname.

Install Discourse on Ubuntu 12.04.3 LTS x64. We always recommend using the current LTS distribution.

You will receive a mail from Digital Ocean with the root password to your Droplet. (However, if you use SSH keys, you may not need a password to log in.)

Access Your Droplet

Connect to your Droplet via SSH:

ssh root@192.168.1.1

(Alternately, use Putty on Windows)

Replace 192.168.1.1 with the IP address of your Droplet.

You will be asked for permission to connect, type yes, then the root password, which is in the email Digital Ocean sent you when the Droplet was set up. Enter it.

Install Git

apt-get install git

Generate SSH Key

We strongly recommend setting a SSH key because you may need to access the Rails console for debugging purposes. This cannot be done after bootstrapping the app.

ssh-keygen -t rsa -C "your_email@example.com"

(We want the default settings, so when asked to enter a file in which to save the key, just press enter. Via GitHub's SSH guide.)

Install Docker

apt-get update
apt-get install linux-image-generic-lts-raring linux-headers-generic-lts-raring

Reboot the server:

reboot

This will log you out from your SSH session, so reconnect:

ssh root@192.168.1.1

Finish installing Docker:

wget -qO- https://get.docker.io/ | sh

Install Discourse

Create a /var/docker folder where all the Docker related stuff will reside:

mkdir /var/docker

Clone the Official Discourse Docker Image into this /var/docker folder:

git clone https://github.com/discourse/discourse_docker.git /var/docker

Switch to your Docker folder:

cd /var/docker

Copy the samples/standalone.yml file into the containers folder as app.yml, so the path becomes containers/app.yml:

cp samples/standalone.yml containers/app.yml

Edit app.yml:

nano containers/app.yml

(We recommend Nano because it works like a typical GUI text editor, just use your arrow keys. Hit CtrlO then Enter to save and CtrlX to exit. However, feel free to choose whatever text editor you like. In the below screenshot we use Vim.)

Edit as desired, but at minimum set DISCOURSE_DEVELOPER_EMAILS and DISCOURSE_HOSTNAME.

We renamed DISCOURSE_HOSTNAME to discourse.techapj.com, this means that we want to host our instance of Discourse on http://discourse.techapj.com/. You'll need to modify your DNS records to reflect the IP address and preferred URL address of your server.

Mail Setup

Email is critical to Discourse. We strongly recommend configuring mail settings before bootstrapping.

  • If you already have a mail server, put your existing mail server credentials in the app.yml file.

  • Otherwise, create a free account on Mandrill (or Mailgun, or Mailjet), and put your mail credentials (available via the Mandrill dashboard) in the app.yml file. The settings you want to change are DISCOURSE_SMTP_ADDRESS, DISCOURSE_SMTP_PORT, DISCOURSE_SMTP_USER_NAME, DISCOURSE_SMTP_PASSWORD.

  • Be sure you remove the comment character # from the beginning of these mail configuration lines!

Add Your SSH Key

If you successfully generated the SSH key as described earlier, get it:

cat ~/.ssh/id_rsa.pub

Copy the entire output and paste it into the ssh_key setting in the app.yml file.

Bootstrap Discourse

Be sure to save the app.yml file, and begin bootstrapping Discourse:

./launcher bootstrap app

This command may take some time, so be prepared to wait. It is automagically configuring your Discourse environment.

After that completes, start Discourse:

./launcher start app

Congratulations! You now have your own instance of Discourse, accessible via the domain name you entered in app.yml earlier.

You can also access it by visiting the server IP address directly, e.g. http://192.168.1.1.

Log In and Become Admin

Sign into your Discourse instance. If you configured DISCOURSE_DEVELOPER_EMAILS and your email matches, your account will be made Admin by default.

If your account was not made admin, try SSH'ing into your container (assuming you entered your SSH key in the app.yml file):

./launcher ssh my_container
sudo -iu discourse
cd /var/www/discourse
RAILS_ENV=production bundle exec rails c
u = User.last
u.admin = true
u.save

This will manually make the first user an admin.

If anything needs to be improved in this guide, feel free to ask on meta.discourse.org, or even better, submit a pull request.

Posts: 94

Participants: 25

Read full topic

Body is too similar to what you recently posted

Administration interface and testing admin

0
0

jbn wrote:

As the WordPress of the discussion world Discourse will have a lot of expectations on the admin functionality and the admin UI. Or at least that's why many clients I've met like WP, the admin UI is easy.

I've a setup started thanks to the "Error connecting to Redis on localhost:6379" thread. Now I have no idea how to set up an admin account as this is pretty much the first time I've touched Rails in a meaningful way. Any help getting in touch with the admin interface is much appreciated smile

Posts: 4

Participants: 2

Read full topic

Discourse on FreeBSD

0
0

Michael Brown wrote:

Hi @supermathie ,

That sounds like the voice of experience. I have been working on getting Discourse installed on my FreeBSD dedicated server with no luck. I'm running into issues mostly with gems not building. Would you happen to remember what changes you made to get it running on FreeBSD.

Thanks for your time.

John

Posts: 8

Participants: 4

Read full topic

Viewing all 60309 articles
Browse latest View live




Latest Images