Stephen Paul Weber wrote:

There isn't much in preferences on this. Do I get notified by email of new posts? Can I reply to posts by replying to emails?

Posts: 5

Participants: 5

Read full topic

Watchman Monitoring wrote:

Our site is very close to going live - I'm excited!

The emails that are being sent have a Very long prefix- the very long name of our group.

Where could we define an alternate, shorter email subject line prefix?

Thanks so much!

Posts: 3

Participants: 2

Read full topic

Eli the Bearded wrote:

The bar on the top of some pages that looks like this:

Popular New (11) Unread Read Favorited Categories

I'm not sure what it's called, but it isn't on the top of all pages. Why isn't that functionality available where ever I am on the site? I'd expect all of those links to be available under the "go to another topic list or category" or under the "notifications..." drop down.

Posts: 5

Participants: 2

Read full topic

Ted Strauss wrote:

I would like to host a Discourse site for a bilingual context (en/fr) where users
give their prefered language during registration. Both languages will get mixed
together in the forum.
Is this doable?

Posts: 23

Participants: 13

Read full topic

Julien Dumétier wrote:

At the request from @Maomao, as a translator we've got sometimes issues translating some messages, this thread will try to be the missing link between the dev team and the translators to help them provide the best translation possible.
Please @sam, @codinghorror, @zogstrip and the others... help us

Posts: 5

Participants: 3

Read full topic

nitper wrote:

I just updated to the latest (0.9.8.2), and now I get an error when accessing / or /login from a desktop when logged out and enable_mobile_theme is checked. If I am already logged in, the site works normally.

==> thin.2.log <==
Unexpected error while processing request: undefined method `[]' for nil:NilClass
        /var/www/discourse/lib/mobile_detection.rb:13:in `resolve_mobile_view!'
        /var/www/discourse/lib/middleware/anonymous_cache.rb:28:in `is_mobile?'
        /var/www/discourse/lib/middleware/anonymous_cache.rb:33:in `cache_key'
        /var/www/discourse/lib/middleware/anonymous_cache.rb:37:in `cache_key_body'
        /var/www/discourse/lib/middleware/anonymous_cache.rb:53:in `cached'
        /var/www/discourse/lib/middleware/anonymous_cache.rb:102:in `call'
        /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/engine.rb:511:in `call'
        /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/application.rb:97:in `call'
        /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/railtie/configurable.rb:30:in `method_missing'
        /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:138:in `call'
        /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:65:in `block in call'
        /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in `each'
        /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in `call'
        /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/thin-1.6.1/lib/thin/connection.rb:82:in `block in pre_process'
        /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/thin-1.6.1/lib/thin/connection.rb:80:in `catch'
        /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/thin-1.6.1/lib/thin/connection.rb:80:in `pre_process'
        /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/thin-1.6.1/lib/thin/connection.rb:55:in `process'
        /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/thin-1.6.1/lib/thin/connection.rb:41:in `receive_data'
        /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in `run_machine'
        /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in `run'
        /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/thin-1.6.1/lib/thin/backends/base.rb:73:in `start'
        /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/thin-1.6.1/lib/thin/server.rb:162:in `start'
        /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/thin-1.6.1/lib/thin/controllers/controller.rb:87:in `start'
        /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/thin-1.6.1/lib/thin/runner.rb:200:in `run_command'
        /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/thin-1.6.1/lib/thin/runner.rb:156:in `run!'
        /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/thin-1.6.1/bin/thin:6:in `<top (required)>'
        /usr/local/rvm/gems/ruby-2.0.0-p353@discourse/bin/thin:23:in `load'
        /usr/local/rvm/gems/ruby-2.0.0-p353@discourse/bin/thin:23:in `<main>'
        /usr/local/rvm/gems/ruby-2.0.0-p353@discourse/bin/ruby_executable_hooks:15:in `eval'
        /usr/local/rvm/gems/ruby-2.0.0-p353@discourse/bin/ruby_executable_hooks:15:in `<main>'

If I turn off enable_mobile_theme it works fine. Any ideas?

Posts: 5

Participants: 2

Read full topic

Jp Gordon wrote:

Continuing the discussion from Email notifications:

We have the need to be notified when a post is older than X hours. Any plans for this?

Posts: 1

Participants: 1

Read full topic

Passante wrote:

Hi guys,
our community is trying to move from vbulletin forum to discourse and we need your help!
We just published the discourse forum to test it but we are facing some performance issues.

We need to understand how powerful the server should be to manage our users and tweak the discourse installation to get rid of all errors we are facing.

Here the specs of the server:
VPS on Digital ocean 1 CPU 1GB RAM 30 SSD
Discourse_Docker by sam on Docker 0.7 Ubuntu 13.04 x64

Upgrading to 0.9.8.1 to resolved the overload issue with sidekiq only partially.

As you can see the load is still high but not due anymore to the sidekiq daemons.

cpu_usage1.PNG1097x182 20.5 KB

Right the traffic of the new discourse installation is really small as you can see from stats:

1. We see some worrying errors in the log:

2014-01-11T11:52:36Z 13074 TID-ou7ftz24o INFO: [Sidetiq] Sidetiq is covered by the 3-clause BSD license.
2014-01-11T11:52:36Z 13074 TID-ou7ftz24o INFO: [Sidetiq] See LICENSE and http://opensource.org/licenses/BSD-3-Clause for licensing details.
2014-01-11T11:52:36Z 13074 TID-ou7ftz24o INFO: [Sidetiq] Sidetiq::Supervisor start
2014-01-11T11:52:36Z 13074 TID-ou7fr1d0s INFO: [Sidetiq] Sidetiq::Actor::Clock id: 70073752552160 initialize
2014-01-11T11:52:36Z 13074 TID-ou7frgm90 INFO: [Sidetiq] Sidetiq::Actor::Handler id: 70073753259860 initialize
2014-01-11T11:52:36Z 13074 TID-ou7fri1rg INFO: [Sidetiq] Sidetiq::Actor::Handler id: 70073753368280 initialize
2014-01-11T11:52:36Z 13074 TID-ou7fr1d0s WARN: [Sidetiq] Can't link Sidetiq::Actor::Clock. Sidekiq::Manager not running. Retrying in 5 seconds ...
2014-01-11T11:52:36Z 13074 TID-ou7frgm90 WARN: [Sidetiq] Can't link Sidetiq::Actor::Handler. Sidekiq::Manager not running. Retrying in 5 seconds ...
2014-01-11T11:52:36Z 13074 TID-ou7fri1rg WARN: [Sidetiq] Can't link Sidetiq::Actor::Handler. Sidekiq::Manager not running. Retrying in 5 seconds ...
2014-01-11T11:52:41Z 13074 TID-ou7fr1d0s WARN: [Sidetiq] Can't link Sidetiq::Actor::Clock. Sidekiq::Manager not running. Retrying in 5 seconds ...
2014-01-11T11:52:41Z 13074 TID-ou7frgm90 WARN: [Sidetiq] Can't link Sidetiq::Actor::Handler. Sidekiq::Manager not running. Retrying in 5 seconds ...
2014-01-11T11:52:41Z 13074 TID-ou7fri1rg WARN: [Sidetiq] Can't link Sidetiq::Actor::Handler. Sidekiq::Manager not running. Retrying in 5 seconds ...
[deprecated] I18n.enforce_available_locales will default to true in the future. If you really want to skip validation of your locale you can set I18n.enforce_available_locales = false to avoid this message.
[36] 11 Jan 11:53:31.026 10 changes in 300 seconds. Saving...
[36] 11 Jan 11:53:31.033 Background saving started by pid 13664
[13664] 11 Jan 11:53:31.259 DB saved on disk
[13664] 11 Jan 11:53:31.261 RDB: 1 MB of memory used by copy-on-write
[36] 11 Jan 11:53:31.337 Background saving terminated with success
2014-01-11 11:54:06 UTC LOG: unexpected EOF on client connection with an open transaction
2014-01-11 11:54:17 UTC LOG: unexpected EOF on client connection with an open transaction
2014-01-11 11:54:41 UTC LOG: could not receive data from client: Connection reset by peer
2014-01-11 11:55:06 UTC LOG: could not send data to client: Broken pipe
2014-01-11 11:55:06 UTC FATAL: connection to client lost
2014-01-11 11:56:57 UTC LOG: unexpected EOF on client connection with an open transaction
[36] 11 Jan 11:58:32.081 10 changes in 300 seconds. Saving...
[36] 11 Jan 11:58:32.091 Background saving started by pid 16882
[16882] 11 Jan 11:58:32.372 DB saved on disk
[16882] 11 Jan 11:58:32.376 RDB: 1 MB of memory used by copy-on-write
[36] 11 Jan 11:58:32.394 Background saving terminated with success
[36] 11 Jan 12:03:33.052 10 changes in 300 seconds. Saving...
[36] 11 Jan 12:03:33.063 Background saving started by pid 19647
[19647] 11 Jan 12:03:33.661 DB saved on disk
[19647] 11 Jan 12:03:33.667 RDB: 1 MB of memory used by copy-on-write
[36] 11 Jan 12:03:33.676 Background saving terminated with success
> 2014-01-11 12:14:52 UTC LOG: unexpected EOF on client connection with an open transaction[36] 11 Jan 12:18:36.082 10 changes in 300 seconds. Saving...
[36] 11 Jan 12:18:36.089 Background saving started by pid 27906
[27906] 11 Jan 12:18:36.321 DB saved on disk
[27906] 11 Jan 12:18:36.325 RDB: 1 MB of memory used by copy-on-write
[36] 11 Jan 12:18:36.395 Background saving terminated with success
[36] 11 Jan 12:23:37.032 10 changes in 300 seconds. Saving...
[36] 11 Jan 12:23:37.041 Background saving started by pid 30263
[30263] 11 Jan 12:23:37.456 DB saved on disk
[30263] 11 Jan 12:23:37.468 RDB: 1 MB of memory used by copy-on-write
[36] 11 Jan 12:23:37.550 Background saving terminated with success
> 2014-01-11 12:23:56 UTC LOG: could not receive data from client: Connection reset by peer
2014-01-11 12:23:56 UTC LOG: unexpected EOF on client connection with an open transaction
2014-01-11 12:24:16 UTC LOG: could not receive data from client: Connection reset by peer
2014-01-11 12:24:16 UTC LOG: unexpected EOF on client connection with an open transaction
2014-01-11 12:39:42 UTC LOG: unexpected EOF on client connection with an open transaction*
root@discourse:/opt/discourse_docker#

EOF errors are related to bad gateways errors trying to inserting new posts.

1. Monitoring the CPu of the server while posting, it spikes considerably with one user inserting a post and then we constantly get bad gateway error and some times the server is not responding to pings due to high load.
   

2. After the boostrap phase, we see this king of errors:
   df: Warning: cannot read table of mounted file systems: No such file or directory

I strongly believe docker is the way to semplify the discourse deploy, but as you can see it needs still some improvements. Helping us would help other people how are approching to discourse project without being RoR gurus.

Thanks in advance for any help.

Posts: 15

Participants: 4

Read full topic

Sander Datema wrote:

Continuing the discussion from Export rake task does not include locally stored avatars:

On my forum I never used local upload folders (I use S3). This script will quit with an error if the database folder is missing.

Posts: 1

Participants: 1

Read full topic

mrsentinel wrote:

Why can't you tag a topic with more than one area of emphasis? This seems to take discourse back to a typical forum. What would be cool is to have two menus, one for the primary category and then one for a secondary category or meta tags to help search and filtering.

Thoughts?

Posts: 2

Participants: 1

Read full topic

mrsentinel wrote:

I am really impressed with discourse. I have been hunting for a really good web developer who can integrate discourse into wordpress or another blogging platform and also have the ability to monetize the site with classified ads. I've got a lot more ideas, so I need a pro who has done some really outside the box sites and clever advertising integration schemes. If you meet this description, contact me and shoot me some links to sites you have built.

Posts: 1

Participants: 1

Read full topic

Caio DosAnjos wrote:

I recently set up Discourse on my server using the Ubuntu install tutorial on GitHub. Everything is working fine- except for the email. My tests conclude that it is not a postfix problem; I've sent myself emails from the terminal through postfix and SES and have received them. The logs say don't have any mention of there even being an email request. My current email setup is:

smtp_address = email-smtp.us-east-1.amazonaws.com

# port of smtp server used to send emails. This varies based on your e-mail host.
smtp_port = 25

# domain passed to smtp server
smtp_domain = mydomain.com

 # username for smtp server
smtp_user_name = [My Amazon Public Key]

# password for smtp server
smtp_password = [My Amazon Private Key]

# enable TLS encryption for smtp connections
smtp_enable_start_tls = true

Can anyone help me? Do you need more info? Just ask, I'm new to email servers, so I didn't know how much to post.

Posts: 6

Participants: 4

Read full topic

Michael wrote:

How can I change the invite email text?
I want it to be a bit more specific about the forum you are invited to.
Current text:

USER invited you to FORUM.

If you're interested, click the link below to join:

LINK

You were invited by a trusted user, so you'll be able to join immediately, without needing to log in.

Posts: 6

Participants: 2

Read full topic

Steve Baer wrote:

I'm having trouble upgrading from v0.9.8.1 to v0.9.8.2.

During the upgrade, when I run

RUBY_GC_MALLOC_LIMIT=90000000 RAILS_ENV=production rake db:migrate

I get the following error (note, I haven't changed anything in my database.yml file or my multisite.yml file). Any help would be appreciated.

(in /home/discourse/discourse)
rake aborted!
FATAL:  database "discourse" does not exist
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/postgresql_adapter.rb:831:in `initialize'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/postgresql_adapter.rb:831:in `new'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/postgresql_adapter.rb:831:in `connect'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/postgresql_adapter.rb:548:in `initialize'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/postgresql_adapter.rb:41:in `new'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/postgresql_adapter.rb:41:in `postgresql_connection'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/abstract/connection_pool.rb:440:in `new_connection'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/abstract/connection_pool.rb:450:in `checkout_new_connection'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/abstract/connection_pool.rb:421:in `acquire_connection'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/abstract/connection_pool.rb:356:in `block in checkout'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/abstract/connection_pool.rb:355:in `checkout'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/abstract/connection_pool.rb:265:in `block in connection'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/abstract/connection_pool.rb:264:in `connection'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/abstract/connection_pool.rb:546:in `retrieve_connection'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.2/lib/active_record/connection_handling.rb:79:in `retrieve_connection'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.2/lib/active_record/connection_handling.rb:53:in `connection'
/home/discourse/discourse/lib/site_settings/db_provider.rb:61:in `table_exists?'
/home/discourse/discourse/lib/site_settings/db_provider.rb:10:in `all'
/home/discourse/discourse/lib/site_setting_extension.rb:121:in `block in refresh!'
/home/discourse/discourse/lib/site_setting_extension.rb:117:in `synchronize'
/home/discourse/discourse/lib/site_setting_extension.rb:117:in `refresh!'
/home/discourse/discourse/config/initializers/05-site_settings.rb:3:in `block in <top (required)>'
/home/discourse/discourse/vendor/gems/rails_multisite/lib/rails_multisite/connection_management.rb:45:in `block in each_connection'
/home/discourse/discourse/vendor/gems/rails_multisite/lib/rails_multisite/connection_management.rb:43:in `each'
/home/discourse/discourse/vendor/gems/rails_multisite/lib/rails_multisite/connection_management.rb:43:in `each_connection'
/home/discourse/discourse/config/initializers/05-site_settings.rb:1:in `<top (required)>'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:223:in `load'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:223:in `block in load'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:214:in `load_dependency'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:223:in `load'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/engine.rb:609:in `block (2 levels) in <class:Engine>'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/engine.rb:608:in `each'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/engine.rb:608:in `block in <class:Engine>'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/initializable.rb:30:in `instance_exec'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/initializable.rb:30:in `run'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/initializable.rb:55:in `block in run_initializers'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/initializable.rb:44:in `each'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/initializable.rb:44:in `tsort_each_child'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/initializable.rb:54:in `run_initializers'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/application.rb:215:in `initialize!'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/railtie/configurable.rb:30:in `method_missing'
/home/discourse/discourse/config/environment.rb:5:in `<top (required)>'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `block in require'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:214:in `load_dependency'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/application.rb:189:in `require_environment!'
/home/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/application.rb:250:in `block in run_tasks_blocks'
/home/discourse/.rvm/gems/ruby-2.0.0-p195/bin/ruby_noexec_wrapper:14:in `eval'
/home/discourse/.rvm/gems/ruby-2.0.0-p195/bin/ruby_noexec_wrapper:14:in `<main>'
Tasks: TOP => db:migrate => environment
(See full trace by running task with --trace)

Posts: 11

Participants: 6

Read full topic

Virgo wrote:

Consider a community of "experts" on some topic. Experts would like to post articles or questions on this board, to be discussed only by the other members, who are also experts. For this part, they can use any reasonable traditional message board software (with membership restricted to experts).

Here is the new part.

For each topic opened by an expert for comments by other experts, there should be a "shadow" topic automatically opened for comments by "the public". Say, the expert's topic is visible in the top (or left) half of the screen, and the shadow public's thread is visible in the other half.

The idea is to keep the conversations among experts unencumbered from all the "noise" often generated by non-expert posts, while still allowing visitors to argue with each other about the discussion the experts are having.

A reader should easily be able to choose whether to view ONLY the experts' discussion, or to view both. Searches should also allow this choice.

A related scheme exists at some news sites, where beneath every article there is a comments box (disqus, etc) for readers opinions. However, this is only one layer of comments.

In principle, the idea could be extended to more than 2 layers (imagine professors as the experts, grad students as semi-experts, undergrads below them, and finally the general public at the bottom). However, obvious practical constraints would need to be observed, in going beyond 2 layers.

Posts: 6

Participants: 3

Read full topic

Shiv Kumar wrote:

@zogstrip @sam I noticed that you were involved with creating the emoji plugin, which registers a ton of images. I'm trying to register some images via a plugin, but don't really understand what you had to do in order to get those images to register properly. Can you pass along some tips/best practices for how to register images via plugins?

Posts: 1

Participants: 1

Read full topic

Ashish Saihgal wrote:

Perhaps just a moot point -

Users still have the ability to delete whatever they posted. Does that not change the frozen discussion in a way? One might accidentally delete a vital reply and leave a gap in the discussion.

Should the option to delete replies not be disabled if topic is frozen? I think at the very least it should perhaps be configurable to let forum administrators decide which way they want to go.

Posts: 5

Participants: 3

Read full topic

aeid wrote:

It would be awesome to see Discourse integrated with Wordpress sites as a plugin. Any news or insight on this eventually happening?

Posts: 78

Participants: 32

Read full topic

Kane York wrote:

I think it would be pretty cool if we could get some CSS classes on posts based on what groups a user belongs to.

So, for example:

<article class="boxed group-trust-level-2 group-bb-writers" ......>

With a checkbox for whether or not the group shows up in the styling, in case we want private groups for some reason.

It would already be possible to do crazy CSS stuff with matching on article[data-user-id=6626], but that would be very annoying to do for every user in the group.

Posts: 3

Participants: 2

Read full topic

Sam Saffron wrote:

People are wondering, how it is they can help out with Discourse.

We have seen some chattering both here and on Github.

I wanted to create a topic @eviltrout , @codinghorror and myself can keep up to date with clear ideas of little projects that would immensely help Discourse.

Ruby projects

• Improve performance of the topic list page, or topic page
• Implement more oneboxes (mp3, music from external sources)
• Code climate 4.0, we would like to increase our code climate score cause it strongly indicates to less understandable areas of our code, clearer code is a huge win https://codeclimate.com/github/discourse/discourse
• Help build up the Discourse API gem https://github.com/discourse/discourse_api

JavaScript projects

• Add more unit tests for our JavaScript (especially the admin section)
• Refactor our js so its more readable post CoffeeScript migration
• Add more documentation to our Javascript using YUIDoc
• Improve rendering performance
• Markdown help http://meta.discourse.org/t/add-a-link-to-markdown-syntax-in-posts/8791

Mixed projects

• Work on a Poll plugin, please consult with us first
• Share a link to this post dialog should provide a short link option via goo.gl API
• Editable onebox whitelist (including admin section) currently list of whitelisted urls for oneboxes are hardcoded, some forums may want to amend this.
• Allow logged on users to associate additional login methods (eg: login with google, then add twitter)

CSS projects

• CSS diet, see what can be done to cut down on the css rules we have and make it easier to theme Discourse, add classed where needed, eliminate very deep selectors

General stuff:

Fix your favorite bug listed either here: http://meta.discourse.org/category/bug or on Github

---

If you feel like working on any of the bigger bits, be sure to let us know by replying here. If you want us to add some stuff to the list let us know.

Posts: 24

Participants: 11

Read full topic