wrote:

Continuing the discussion from Discourse Spoiler Alert:

I managed to get this working on our Test forum (I put the - git clone line in the app.yml file) and it seemed to be working fine. However, on the production instance it doesn't seem to work even though we haven't changed anything. I also set up a new server instance and the only thing I added to the app.yml was the plugin and even on the fresh instance it doesn't seem to work.

## The docker manager plugin allows you to one-click upgrade Discouse
## http://discourse.example.com/admin/docker
hooks:
  after_code:
    - exec:
        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

Am I missing a step somewhere? I see the git get pulled down correctly when building the app but I'm not sure what else I need to do? Thanks.

Posts: 3

Participants: 2

Read full topic

George Kaplan wrote:

I am getting a strange error in translation. [Object object] for the private messages.

any ideas?

Posts: 2

Participants: 2

Read full topic

Rahul Dhingra wrote:

Copy & paste image feature does not work for .png format

thanks

Posts: 4

Participants: 2

Read full topic

Sam Saffron wrote:

We need a name for the bronze Liking badge.

You get this badge right after your first like, it teaches users that liking is important.

Ideas:

"Liker"
"Thank you"

Any others?

Posts: 7

Participants: 4

Read full topic

Karol Radziejewski wrote:

On my website mamydzieci.co.uk I have had pattern background set by:

  body {
  background-color: #E1DDC4;
  background-image:url('/uploads/default/6/8680ad1c602b06d6.jpg');
  background-repeat:repeat;
  }

But since some recent update, background image is being stretched, I can't find out how to fix it? Maybe someone could help?

Posts: 3

Participants: 3

Read full topic

Ordinary wrote:

There has been a problem.
My discourse can't send any e-mail.
I'm quite sure that my smtp host is up and port 994 465 and 25 is reachable.I can use outlook just fine.
I tried to use ./launcher mailtest app
but when I use port 994 or 465,it showed

ERROR: Connection unexpectedly closed: time out

When I use port 25,it showed

ERROR:nobody+launcher-mailtest@discourse.org
Traceback (most recent call last)
  File "/var/docker/scripts/mailtest", line 766, in sendmail
    result = smtp.sendmail('nobody+launcher-mailtest@discourse.org",destemail,msg.as_string())
  File "/usr/lib/python3.4/smtplib.py", line 766, in sendmail
    raise SMTPSenderRefused(code, resp, from_addr)
smtplib.SMTPSenderRefused: (553, b'Mail from must equal authorized user', 'nobody+launcher-mailtest@discourse.org')

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/var/docker/scripts/mailtest", line 172, in <module>
    if 'SMTP AUTH extension not supported by server' in e.args[0]:
TypeError: argument of type 'int' is not iterable

Posts: 6

Participants: 2

Read full topic

Alexandru Chirila wrote:

If you want to use Trac as Single Sign On point for Discourse we've developed a plugin that allows you to do this. It's easily installable and configurable.

After installation simply add the details to you configuration file. For example:

[sso]
sso_secret = thisisatestsecret
sso_redirect = https://my.discourse.example.com/session/sso_login

And grant the SSO_LOGIN permission to any user you deem fit

For more information, sources and downloads see:

https://github.com/SpamExperts/trac-sso

Posts: 1

Participants: 1

Read full topic

Jerre wrote:

I would love to see a plugin to automatically generate bitly style short-links for forum topics. Using the bitly API would be great, since it allows for branded domains and it's widely used.

I read this topic: https://meta.discourse.org/t/shorten-share-links/12558 but it seems like it's only related to the goo.gl service rather than Bitly, and it's not a plugin but an extension of the core.

Posts: 3

Participants: 2

Read full topic

cpradio wrote:

If you visit the profile page, you will see that there is a lot of wasted space.

Can't we align the data below the avatar to the right of the avatar (think two column layout), so the avatar and the information are side by side? Why must I scroll past all data to get to the information I want to view?

Posts: 11

Participants: 3

Read full topic

Caue Rego wrote:

Discourse currently uses YAML, and I think that's just fine.

But Sam seems to disagree. What kind of "more robust and simpler" format could he be talking about? I don't think we got anything better than YAML today. Or do we?

Posts: 7

Participants: 5

Read full topic

Eyal Levin wrote:

Using vagrant for development, when I run

bundle exec rake db:migrate

I get:

== Seed from /vagrant/db/fixtures/005_users.rb
 - User {:id=>-1, :name=>"system", :username=>"system", :username_lower=>"system", :email=>"no_email", :password=>"2db06fedb92f03f6c95390c085c9d04c", :active=>true, :admin=>true, :moderator=>true, :email_direct=>false, :approved=>true, :email_private_messages=>false, :trust_level=>4}
rake aborted!
ActiveRecord::RecordNotFound: Couldn't find Badge with 'id'=9
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/seed-fu-discourse-2.2.1/lib/seed-fu/runner.rb:46:in `eval'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.4/lib/active_record/relation/finder_methods.rb:420:in `find_one'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.4/lib/active_record/relation/finder_methods.rb:404:in `find_with_ids'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.4/lib/active_record/relation/finder_methods.rb:68:in `find'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.4/lib/active_record/querying.rb:3:in `find'
/vagrant/app/models/user.rb:627:in `grant_autobiographer'
/vagrant/app/models/user.rb:614:in `refresh_avatar'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:424:in `block in make_lambda'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:221:in `call'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:221:in `block in halting_and_conditional'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:215:in `call'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:215:in `block in halting_and_conditional'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:86:in `call'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activesupport-4.1.4/lib/active_support/callbacks.rb:86:in `run_callbacks'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.4/lib/active_record/callbacks.rb:302:in `create_or_update'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.4/lib/active_record/persistence.rb:103:in `save'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.4/lib/active_record/validations.rb:51:in `save'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.4/lib/active_record/attribute_methods/dirty.rb:21:in `save'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.4/lib/active_record/transactions.rb:268:in `block (2 levels) in save'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.4/lib/active_record/transactions.rb:329:in `block in with_transaction_returning_status'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.4/lib/active_record/connection_adapters/abstract/database_statements.rb:199:in `transaction'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.4/lib/active_record/transactions.rb:208:in `transaction'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.4/lib/active_record/transactions.rb:326:in `with_transaction_returning_status'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.4/lib/active_record/transactions.rb:268:in `block in save'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.4/lib/active_record/transactions.rb:283:in `rollback_active_record_state!'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.4/lib/active_record/transactions.rb:267:in `save'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/seed-fu-discourse-2.2.1/lib/seed-fu/seeder.rb:74:in `seed_record'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/seed-fu-discourse-2.2.1/lib/seed-fu/seeder.rb:36:in `block (2 levels) in seed'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/seed-fu-discourse-2.2.1/lib/seed-fu/seeder.rb:36:in `map'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/seed-fu-discourse-2.2.1/lib/seed-fu/seeder.rb:36:in `block in seed'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.4/lib/active_record/connection_adapters/abstract/database_statements.rb:199:in `transaction'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.4/lib/active_record/transactions.rb:208:in `transaction'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/seed-fu-discourse-2.2.1/lib/seed-fu/seeder.rb:35:in `seed'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/seed-fu-discourse-2.2.1/lib/seed-fu/active_record_extension.rb:32:in `seed'
(eval):9:in `block (2 levels) in run_file'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/seed-fu-discourse-2.2.1/lib/seed-fu/runner.rb:46:in `eval'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/seed-fu-discourse-2.2.1/lib/seed-fu/runner.rb:46:in `block (2 levels) in run_file'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/seed-fu-discourse-2.2.1/lib/seed-fu/runner.rb:58:in `block in open'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/seed-fu-discourse-2.2.1/lib/seed-fu/runner.rb:57:in `open'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/seed-fu-discourse-2.2.1/lib/seed-fu/runner.rb:57:in `open'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/seed-fu-discourse-2.2.1/lib/seed-fu/runner.rb:36:in `block in run_file'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.4/lib/active_record/connection_adapters/abstract/database_statements.rb:201:in `block in transaction'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.4/lib/active_record/connection_adapters/abstract/database_statements.rb:209:in `within_new_transaction'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.4/lib/active_record/connection_adapters/abstract/database_statements.rb:201:in `transaction'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.4/lib/active_record/transactions.rb:208:in `transaction'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/seed-fu-discourse-2.2.1/lib/seed-fu/runner.rb:35:in `run_file'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/seed-fu-discourse-2.2.1/lib/seed-fu/runner.rb:26:in `block in run'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/seed-fu-discourse-2.2.1/lib/seed-fu/runner.rb:25:in `each'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/seed-fu-discourse-2.2.1/lib/seed-fu/runner.rb:25:in `run'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/seed-fu-discourse-2.2.1/lib/seed-fu.rb:29:in `seed'
/vagrant/lib/tasks/db.rake:3:in `block in <top (required)>'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/bin/ruby_noexec_wrapper:14:in `eval'
/usr/local/rvm/gems/ruby-2.0.0-p0-turbo/bin/ruby_noexec_wrapper:14:in `<main>'
Tasks: TOP => db:migrate
(See full trace by running task with --trace)

EDIT: commit f5a94bf668e44987a9877ccddffac089be89050a

Posts: 5

Participants: 3

Read full topic

Michael Brown wrote:

Seeing a double makes me much sad - I would rather have a !

---

Pasted image769x512 63.8 KB

---

Posts: 3

Participants: 3

Read full topic

BountifulBabyMedia wrote:

When I try uploaded an image for an avatar or profile background, it gives me this error "Sorry, there was an error uploading that file. Please try again." What is the problem!? I've tried different sizes and image formats different images and nothing works. Why doesn't it tell me what the problem is with the image? is the file to large? Wrong file type? etc. ?? Need Help with this! Have customers on my forum that are upset about it.

Posts: 3

Participants: 2

Read full topic

aome wrote:

I'm trying to showcase Discourse to a group of friends. We have a CAD forum that has been independent for 20 years or so. It is being eaten up by the company who makes the CAD system we use. Some of us think this is a dumb move by both the cad company and the "owners" of the forum. So I would like to load the history I have of the forum into a discourse server and then let the guys/gals take a look.

I don't know that discourse is the solution because its really/probably a hosting+money issue. But I see a sort of freedom if we can make our discourse "decentralized". We can probably host it private from home with several backups around the states.

So anyho, I got history in the form of emails in Gmail. I can download it all and parse it using perl. But then is there an easy format that I can load it all into discourse? It would be coming from my user so the users who actually posted would not have accounts yet. how would I deal with that? maybe I could load it all as a word press reference? but then that would not show case discourse. I could maybe make a bunch of fake users and do it that way?

Ideas/Suggestions/comments? anyone?

Posts: 4

Participants: 3

Read full topic

Michael Downey wrote:

I can successfully perform S3 backups to a bucket in the S3 "US Standard" region, but when I try to point Discourse at my bucket in the "Ireland" region (aka eu-west-1?) I get the following failure:

 [2014-07-07 13:41:08] Creating empty archive...
 [2014-07-07 13:41:08] Archiving metadata...
 [2014-07-07 13:41:08] Archiving data dump...
 [2014-07-07 13:41:08] Archiving uploads...
 [2014-07-07 13:41:09] Gzipping archive...
 [2014-07-07 13:41:11] Executing the after_create_hook for the backup
 [2014-07-07 13:41:20] EXCEPTION: Connection reset by peer (Errno::ECONNRESET)
 [2014-07-07 13:41:20] /usr/local/lib/ruby/2.0.0/openssl/buffering.rb:376:in `syswrite_nonblock' /usr/local/lib/ruby/2.0.0/openssl/buffering.rb:376:in `write_nonblock'

... etc.

This fails every time I use a bucket created in S3 region of Ireland, and a Discourse setting of eu-west-1. (Why are these labeled differently?) If I keep all other settings the same, but use the us-east-1 setting in Discourse and an S3 region of US Standard, things work fine.

I'd prefer to keep my backups in Europe, as is the server running my Discourse instance. Any ideas how to get S3 backups to Ireland working, or how to troubleshoot the error further?

BTW: There is a line in the logs at the end of the failed backup process saying a (Discourse) notification will be sent to me, but it never arrives.

Posts: 2

Participants: 2

Read full topic

Eedan wrote:

Hi

I've been looking for a mainly category-less forum, something that depends more on filtering to keep it's stuff organized.

Discourse is the closest thing I've found, but not quite. Reading through the posts I've read up on the issue of going completely user-tags, and for that much I completely agree.

But simply one layer of categories doesn't seem like it'd be enough for my case, and the added "subcategory" option feels like it's out of line with the whole "category-less" thing.

Would it be possible to go somewhere in-between? Something like 2 "families" of categories, working side-by-side. It's not really tags, and we get more layers without depending on subcategories.

An example of how this would work would be for example in a support site. The first family of categories would be the product line, and the second would be the type of support needed. A user well-versed with a specific product can filter by the said product using the first family of categories and leave the second one off. A user who needs specific help can use both families to further filter the topics and find a thread relating to his issue.

Of course this can be done with the current system, but here is where things differ. Since both category families are independent of each other, we could have a user who's well versed in hardware regardless of the product. He could sort using only the second family of categories and leave the first off.

This is of course but one scenario, this system would work even better for my site (it's a gaming community) and I'm sure it will be the same for many others.

I'm certain this small modification won't take long to do from my end so don't take this as a feature request or anything (you can if you want to though). It's just I'm personally curious as to why everyone decided to go with subcategories when it seems like the whole purpose of this structure was to drift away from that mindset... Maybe the idea was never was never brought up? Or maybe there's something I'm completely missing and this might be bad for my site in the long run!

Haha, well other than that I'm real impressed with this innovative design. Kudos~~

Posts: 5

Participants: 4

Read full topic

Neo Lee wrote:

I used Discourse in my community for a while and it worked perfect all the time, but today I found that I cannot 'launcher ssh app' to the container after doing these:

1. Change app.yml config to: "version: tests-passed"
2. Rebuild container by: sudo ./launcher rebuild app
3. Upgrade lxc-docker to 1.1.0

After that the installation works fine as before but "sudo ./launcher ssh app" failed with:

Connection closed by 127.0.0.1

Check the logs with "./launcher logs app" I get this (other info seems irrelevant):

Access denied for user root by PAM account configuration [preauth]

I may be wrong but this error most likely pops out when the public key is not in authorized_keys?

I have double checked the public key I put in the app.yml, it's identical to the content of /root/.ssh/id_rsa.pub.

Any suggestion? Or anyone have met similar issue?

Posts: 6

Participants: 2

Read full topic

The Avatar Changer wrote:

As per the this topic over on TDWTF, spoilers are no longer working on new or edited posts. It appears that whatever code parsed [spoiler]Text[/spoiler] into <span class="spoiled">Text</span> is no longer working.

Posts: 7

Participants: 3

Read full topic

lid wrote:

I haven't really isolated the problem but I will start by how to replicate it.

This issue best can be replicated with a topic that has more then 2 posts that are not visible on the bottom

Tested on: Chrome, Windows 8,i7-4500u

At first I thought the issue was related to the header change ( the move of the logo and the title on the top area when you scroll down a little bit from the top )

But then I realized that I am getting "jump" when the url is changing.
from
topic_id
to
topic_id/1

every time I scroll enough to trigger that url change I experienced the slowness.
the interesting part is that I don't have to scroll thorough the topic, sometimes only scrolling to the 2nd post will cause it(depend on the length of the posts and screen resolution).

It is possible that the "url change" is not the main cause for this issue but perhaps a symptom.

I experience a similar behavior with general scrolling in android, I suspect the mobile and desktop may be affected by the issue.

I wonder if it is possible to disable the url change for testing purposes and see if it improve the scrolling.

this issue might not be noticeable on fast machines

Posts: 8

Participants: 3

Read full topic

Luke Larris wrote:

When you go to a Discourse site for the first time, it can sometimes take about 1 - 3 seconds before the page shows anything but a white background. Call me impatient, but I don't like that. I like my sites to load almost instantly, and Discourse sure doesn't load very fast the first time on every Discourse forum I've visited. However, when it's loaded, browsing the forum is pretty quick, so no complaints there.

The reason it bothers me so much is because that initial page load is very important to me. I believe it really helps my site in the eyes of the user if the site loads instantly. They may not browse around, or even join, but a snappy first page load will leave a positive impression, if only subconsciously.

Is there anything people can do on their host to make that initial page load faster? I know upgrading hardware is one way, but is there any optimizing or caching we can do to improve things?

Also, does the Discourse team have any plans to improve the speed of initial page loads?

Posts: 2

Participants: 2

Read full topic