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

Spacing in digest email

0
0

@ndc wrote:

Not sure if this is specific to discourse meta, but check this screenshot:

I find it difficult to tell which title belongs to which block of text.

I think the vertical space marked by the red arrow should be longer than the one marked by the orange arrow.

Posts: 2

Participants: 2

Read full topic


Assign group permission to a category via API

Customize email notification header and footer

0
0

@chenny408 wrote:

Hi, I do not see any option to customize the header, for example adding a logo, or footer, for the new post notification emails.

Posts: 2

Participants: 2

Read full topic

Migrate Vanilla w/ FileUpload to Discourse | Please Quote

0
0

@moens wrote:

Hey, I need the following:

1) Vanilla forum with FileUpload module and attached media migrated to discourse
2) properly mapped 302's in .htaccess file
3) set up, or give me an idea of how to setup a latest posts widget in Magento
...edit to add:
4) Lots of spam registrations in Vanilla need to be cleaned before migration

Vanilla is on Nexcess, Discourse on DigitalOcean, but I can move Vanilla to the same DigitalOcean droplet to ease migration of necessary.

I can pay through oDesk if you want, or PayPal directly.

Posts: 1

Participants: 1

Read full topic

Authorized extensions for admin

0
0

@BerryBlue wrote:

Is there a way to make certain extensions only available for admins? I'd like to allow upload of .zip files but only for admins.

Posts: 1

Participants: 1

Read full topic

Flag option "convert into PM"

0
0

@rubo77 wrote:

Often one big problem is that users feel attacked and answer in a topic whereas a private massage would have been enough.

If there was a flag option to move a message into a private conversation this would preserve that only posts staff public that are of a lot of public interest.

There even could be a heuristic, that tries to detect such posts. And a button for the author at the latest post to convert into pm directly.

Especially for new users such a button would be a big benefit for the forum

Posts: 1

Participants: 1

Read full topic

Add fancier animated buttons to admin pages

How to customize or change the loading spinner icon?


The background on the entire screen as in twitter

Let people know that HTML works in the editor

I have a great idea for discourse (technology Wikipedia)

0
0

@Pirat wrote:

when the user wrote a post, someone may find it a mistake
and to this was no error, the user edits the record and sends the author to test his
author of the post looks record and decides to correct your record or not, technology is taken from Wikipedia
how you like the idea?
P.S. Sorry for the mistakes I through Google translator content

abridged version
1) I have created a post
2) man corrected post
3) sent me his version
4) I corrected their mistakes
5) thanks man

Posts: 4

Participants: 2

Read full topic

Can't connect to MySQL server during migrate

0
0

@renis wrote:

Trying to migrate from vBulletin, having the same problem with MySQL ...

Can't connect to local MySQL server

$ RAILS_ENV=production ruby vbulletin.rb
loading existing groups...
loading existing users...
loading existing categories...
loading existing posts...
loading existing topics...
/home/discourse/.gem/ruby/2.0.0/gems/mysql2-0.3.18/lib/mysql2/client.rb:70:in `connect': Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) (Mysql2::Error)
        from /home/discourse/.gem/ruby/2.0.0/gems/mysql2-0.3.18/lib/mysql2/client.rb:70:in `initialize'
        from vbulletin.rb:21:in `new'
        from vbulletin.rb:21:in `initialize'
        from vbulletin.rb:484:in `new'
        from vbulletin.rb:484:in `<main>'

how do I verify if the requirements for migration are installed...

thank you!

# gem install mysql2
Building native extensions.  This could take a while...
Successfully installed mysql2-0.3.18
1 gem installed

Posts: 1

Participants: 1

Read full topic

Get error when debugging "uninitialized constant SidekiqExceptionHandler"

0
0

@berniegao wrote:

when I debug discourse in rubymine, I got the following error. However discourse run perfectly through the command "rails s" in the terminal. Any idea?

    Fast Debugger (ruby-debug-ide 0.4.28, debase 0.1.3.beta1) listens on 127.0.0.1:32844


**Uncaught exception: uninitialized constant Discourse::SidekiqExceptionHandler::Sidekiq**

        	/home/bernie/Workstation/discourse/lib/discourse.rb:9:in `<class:SidekiqExceptionHandler>'
        	/home/bernie/Workstation/discourse/lib/discourse.rb:8:in `<module:Discourse>'
        	/home/bernie/Workstation/discourse/lib/discourse.rb:5:in `<top (required)>'
        	/home/bernie/Workstation/discourse/config/application.rb:31:in `<class:Application>'
        	/home/bernie/Workstation/discourse/config/application.rb:19:in `<module:Discourse>'
        	/home/bernie/Workstation/discourse/config/application.rb:18:in `<top (required)>'

Posts: 1

Participants: 1

Read full topic

Unread post bubbles in topic list are not updated

0
0

@elberet wrote:

Screenshot:

The topic list shows several topics with unread posts, but all except the top two are wrong. I took that screenshot right after having read these topics, navigting back and forth a few times.

To reproduce:

  1. Be inactive for a day or two, but at least long enough so that there are a few tracked topics with unread posts. Several of these must be sufficiently far down the list of latest topics so that they're loaded only when you scroll down through the list.

  2. Scroll down until more topics are loaded, then click a topic with unread posts and read everything.

  3. Navigate back to the topic list. At this point, the topic list will not have changed at all. The topic still has the same amount of unread posts (blue marker) as before.

  4. Read another topic with unread posts and navigate back.

  5. Now the topic you've read previously will have updated but will show a gray marker with the same number of unread posts.

  6. Repeat until everything has been read. All topics that had unread posts will now show gray bubbles, with the exception of the last read topic which will still show a blue bubble.

Note: only the front-end topic list is affected, replies are correctly marked as read in the backend. Also, new topics behave correctly, the blue "new" marker is removed immediately when navigating back from the topic view to the list.

Posts: 4

Participants: 2

Read full topic

Bootstrapping Discourse hangs on Redis "ready to accept connections" on Amazon EC2

0
0

@dgs wrote:

Hello,

First timer here, have been following the instructions here: https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md but I'm doing it on an Amazon EC2 instance instead of a Digital Ocean droplet. I'm not very good at server admin stuff so I tend to follow the instructions and get a bit lost when things don't go right, but I've managed to get to the bit about bootstrapping Discourse mostly successfully!

However, when I run the command ./launcher bootstrap app (Actually, I do sudo ./launcher bootstrap app) it begins the process but always 'hangs' for lack of a better word, at the following line:

The server is now ready to accept connections on port 6379

It becomes unresponsive, I then get 'connection reset by peer' and I cannot SSH back in... Also, stuff I have on the instance times out when you try to visit it online, trying to FTP into the instance times out too and the only way I've found to regain control is to reboot the instance from the Amazon EC2 Dashboard.

Here's my Docker Info

Containers: 4
Images: 6
Storage Driver: devicemapper
 Pool Name: docker-202:1-25685-pool
 Pool Blocksize: 65.54 kB
 Backing Filesystem: extfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 222.2 MB
 Data Space Total: 107.4 GB
 Data Space Available: 4.962 GB
 Metadata Space Used: 1.745 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.146 GB
 Udev Sync Supported: false
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.82-git (2013-10-04)
Execution Driver: native-0.2
Kernel Version: 3.5.0-51-generic
Operating System: Ubuntu quantal (12.10)
CPUs: 1
Total Memory: 589.9 MiB

Any guidance would be much appreciated!

Posts: 1

Participants: 1

Read full topic


Docker boostrap fails due to single quotes escaping in SQL INSERT commands

0
0

@willgarcia wrote:

When bootstrapping a Discourse environment with Docker (samsaffron/discourse image, version 1.0.11), Rails db migration fails because of unescaped single quotes in translations' files.

Steps to reproduce:

$ git clone https://github.com/discourse/discourse_docker.git /var/discourse
```

Set the default lang to French in `/var/discourse/containers/app.yml`
,

```
...
env:
  LANG: fr_FR.UTF-8
  DISCOURSE_DEFAULT_LOCALE: fr
...
```

DB migration error:
```
$ cd /var/discourse && ./launcher boostrap app
...
I, [2015-04-25T07:53:17.634912 #39]  INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate'
2015-04-25 07:53:34 UTC [315-1] discourse@discourse ERROR:  syntax error at or near "équipe" at character 284
2015-04-25 07:53:34 UTC [315-2] discourse@discourse STATEMENT:  INSERT INTO categories
	                          (name, color, text_color, created_at, updated_at, user_id, slug, description, read_restricted, position)
	                   VALUES ('Staff', '283890', 'FFFFFF', now(), now(), -1, 'staff', 'Catégorie privée pour les discussions de l'équipe du forum. Les sujets ne sont visibles que pour les admins et les modérateurs.', true, 2)
	                   RETURNING id
rake aborted!
StandardError: An error has occurred, this and all later migrations canceled:

PG::SyntaxError: ERROR:  syntax error at or near "équipe"
LINE 3: ...f', 'Catégorie privée pour les discussions de l'équipe du fo...
                                                             ^
: INSERT INTO categories
                          (name, color, text_color, created_at, updated_at, user_id, slug, description, read_restricted, position)
                   VALUES ('Staff', '283890', 'FFFFFF', now(), now(), -1, 'staff', 'Catégorie privée pour les discussions de l'équipe du forum. Les sujets ne sont visibles que pour les admins et les modérateurs.', true, 2)
                   RETURNING id/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.3/lib/patches/db/pg.rb:90:in `exec'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.3/lib/patches/db/pg.rb:90:in `async_exec'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/postgresql/database_statements.rb:128:in `block in execute'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract_adapter.rb:373:in `block in log'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract_adapter.rb:367:in `log'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/postgresql/database_statements.rb:127:in `execute'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/migration.rb:656:in `block in method_missing'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/migration.rb:628:in `block in say_with_time'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/migration.rb:628:in `say_with_time'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/migration.rb:648:in `method_missing'
/var/www/discourse/db/migrate/20140227201005_add_staff_category.rb:9:in `up'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/migration.rb:605:in `exec_migration'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/migration.rb:586:in `block (2 levels) in migrate'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/migration.rb:585:in `block in migrate'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/connection_pool.rb:294:in `with_connection'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/migration.rb:584:in `migrate'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/migration.rb:759:in `migrate'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/migration.rb:998:in `block in execute_migration_in_transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/migration.rb:1044:in `block in ddl_transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/database_statements.rb:201:in `block in transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/database_statements.rb:209:in `within_new_transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/database_statements.rb:201:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/transactions.rb:208:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/migration.rb:1044:in `ddl_transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/migration.rb:997:in `execute_migration_in_transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/migration.rb:959:in `block in migrate'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/migration.rb:955:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/migration.rb:955:in `migrate'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/migration.rb:814:in `up'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/migration.rb:792:in `migrate'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/railties/databases.rake:34:in `block (2 levels) in <top (required)>'
Tasks: TOP => db:migrate
(See full trace by running task with --trace)
I, [2015-04-25T07:53:35.556523 #39]  INFO -- : == 20140227201005 AddStaffCategory: migrating =================================
-- execute("INSERT INTO categories\n                          (name, color, text_color, created_at, updated_at, user_id, slug, description, read_restricted, position)\n                   VALUES ('Staff', '283890', 'FFFFFF', now(), now(), -1, 'staff', 'Catégorie privée pour les discussions de l'équipe du forum. Les sujets ne sont visibles que pour les admins et les modérateurs.', true, 2)\n                   RETURNING id")

I, [2015-04-25T07:53:35.557179 #39]  INFO -- : Terminating async processes
I, [2015-04-25T07:53:35.557276 #39]  INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/9.3/bin/postmaster -D /etc/postgresql/9.3/main pid: 68
2015-04-25 07:53:35 UTC [68-2] LOG:  received fast shutdown request
2015-04-25 07:53:35 UTC [68-3] LOG:  aborting any active transactions
2015-04-25 07:53:35 UTC [75-2] LOG:  autovacuum launcher shutting down
2015-04-25 07:53:35 UTC [72-1] LOG:  shutting down
I, [2015-04-25T07:53:35.557509 #39]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 191
191:signal-handler (1429948415) Received SIGTERM scheduling shutdown...
191:M 25 Apr 07:53:35.607 # User requested shutdown...
191:M 25 Apr 07:53:35.607 * Saving the final RDB snapshot before exiting.
191:M 25 Apr 07:53:40.060 * DB saved on disk
191:M 25 Apr 07:53:40.060 # Redis is now ready to exit, bye bye...
I, [2015-04-25T07:53:45.593683 #39]  INFO -- : HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/9.3/bin/postmaster -D /etc/postgresql/9.3/main pid:68 did not terminate cleanly, forcing termination!


FAILED
--------------------
RuntimeError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 303 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:105:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle install --deployment --verbose --without test --without development'", "su discourse -c 'bundle exec rake db:migrate'", "su discourse -c 'bundle exec rake assets:precompile'"]}
fd361942a3688d08c9d47a84305aabb47cc52d1216b3812c0474cc50388c9835
FAILED TO BOOTSTRAP

I guess this is not acceptable to introduce single quotes escaping in the translation files because official translators do not have to be aware of database migrations.

Posts: 1

Participants: 1

Read full topic

Port already in use, what to do?

0
0

@Exuraz wrote:

Hi, just tried to setup Discourse and all went good except for launching it.
It gives the following error:

starting up existing container
+ /usr/bin/docker start app
Error response from daemon: Cannot start container app: Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use
FATA[0000] Error: failed to start one or more containers

Which suggests the port is already in use. On the system we run a web (apache, teamspeak and minecraft server.
I am not the best with Linux and Apache, so I was wondering if anyone could help.

Thanks in advance, if you need any more information, let me know.

Regards,
Exuraz

Posts: 13

Participants: 3

Read full topic

General system administration on Digital Ocean droplet?

0
0

@Benno wrote:

Outside of managing Discourse (updates, plug-ins, backups), how much system administration is require when using a Digital Ocean droplet to host Discourse?
Do you need to do your own OS and other security and maintenance patches and updates?

Posts: 4

Participants: 2

Read full topic

Custom emoji set(s)

0
0

@Benno wrote:

We currently have several emoji sets to choose from and can add custom emoji to those.
I would like to propose either or both:

  1. disable/enable individual emoji from the default sets
  2. 'empty' emoji set(s) where the admin adds only custom emoji (or copies them from the existing emoji sets)

On my existing (non-Discourse) forum I have a rather limited set of emoji. I personally feel that having only a few basic emoji to convey basic emotion benefits the discussion.

Posts: 2

Participants: 2

Read full topic

Topics appear empty (user undefined) until refresh

0
0

@kazad wrote:

Loving Discourse, ran into this issue:

Environment: v1.3.0.beta6 +42 with the MathJax plugin

Repro steps:

<div id="ember1597" class="ember-view names trigger-user-card"><span class="username"><a href="undefined" data-auto-route="true" data-user-card="undefined">undefined</a></span></div>

Fix: Performing a hard refresh on the page loads the content correctly (and the issue does not repro further).

I suspected something was cached incorrectly; I've tried rebuilding the app (./launcher rebuild app), backing up & re-importing, flushing the avatars, rebaking the posts, and viewing the site as both admin/anonymous user, but no luck.

Any help or things to investigate would be greatly appreciated!

Posts: 3

Participants: 2

Read full topic

Viewing all 60279 articles
Browse latest View live




Latest Images