But @codinghorror is right: Mods especially will probably need a way to act on groups of topics, and the concept of hover tools only scales to one. There's always the good old check-box. Even Google uses them in Gmail, right there next to the star. Perhaps, after checking some topics, a new toolbar rolls down from underneath the masthead (<header/>)dock with appropriate actions: favorite and flag for regular users, delete and unflag for mods.
I just updated discourse to 0.9.7.9 and am now seeing performance times on each page (see image below). It looks like this is only on for admins because I don't see the times on a coworkers computer. That said, I would still be interested in turning this display off. There are several people in our company that are going to be admins for our localized sites and I don't want to field the question of why this is showing up over and over. Is there a setting to toggle the times off?
I'm using webfaction postgresql specific private instance to run discourse (custom port already configured for discourse 0.9.7.6).
This is not my first update, but this time i have an error. Impossible to upgrade from 0.9.7.6 i have this error (after gem update) when i try to launch :
[reyman64@xxxx discourse]$ RUBY_GC_MALLOC_LIMIT=90000000 RAILS_ENV=production bundle exec rake db:migrate
rake aborted!
FATAL: no pg_hba.conf entry for host "127.0.0.1", user "discourse", database "discourse", SSL on
FATAL: no pg_hba.conf entry for host "127.0.0.1", user "discourse", database "discourse", SSL off
/home/reyman64/webapps/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/reyman64/webapps/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/reyman64/webapps/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/reyman64/webapps/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/reyman64/webapps/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/reyman64/webapps/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/reyman64/webapps/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/reyman64/webapps/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/reyman64/webapps/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/reyman64/webapps/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/reyman64/webapps/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/reyman64/webapps/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/reyman64/webapps/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/reyman64/webapps/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/reyman64/webapps/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.2/lib/active_record/connection_handling.rb:79:in `retrieve_connection'
/home/reyman64/webapps/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.2/lib/active_record/connection_handling.rb:53:in `connection'
/home/reyman64/webapps/discourse/discourse/lib/site_settings/db_provider.rb:61:in `table_exists?'
/home/reyman64/webapps/discourse/discourse/lib/site_settings/db_provider.rb:10:in `all'
/home/reyman64/webapps/discourse/discourse/lib/site_setting_extension.rb:121:in `block in refresh!'
/home/reyman64/webapps/discourse/discourse/lib/site_setting_extension.rb:117:in `synchronize'
/home/reyman64/webapps/discourse/discourse/lib/site_setting_extension.rb:117:in `refresh!'
/home/reyman64/webapps/discourse/discourse/config/initializers/05-site_settings.rb:3:in `block in <top (required)>'
/home/reyman64/webapps/discourse/discourse/vendor/gems/rails_multisite/lib/rails_multisite/connection_management.rb:45:in `block in each_connection'
/home/reyman64/webapps/discourse/discourse/vendor/gems/rails_multisite/lib/rails_multisite/connection_management.rb:43:in `each'
/home/reyman64/webapps/discourse/discourse/vendor/gems/rails_multisite/lib/rails_multisite/connection_management.rb:43:in `each_connection'
/home/reyman64/webapps/discourse/discourse/config/initializers/05-site_settings.rb:1:in `<top (required)>'
/home/reyman64/webapps/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:223:in `load'
/home/reyman64/webapps/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:223:in `block in load'
/home/reyman64/webapps/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:214:in `load_dependency'
/home/reyman64/webapps/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:223:in `load'
/home/reyman64/webapps/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/reyman64/webapps/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/engine.rb:608:in `each'
/home/reyman64/webapps/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/engine.rb:608:in `block in <class:Engine>'
/home/reyman64/webapps/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/initializable.rb:30:in `instance_exec'
/home/reyman64/webapps/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/initializable.rb:30:in `run'
/home/reyman64/webapps/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/initializable.rb:55:in `block in run_initializers'
/home/reyman64/webapps/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/initializable.rb:44:in `each'
/home/reyman64/webapps/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/initializable.rb:44:in `tsort_each_child'
/home/reyman64/webapps/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/initializable.rb:54:in `run_initializers'
/home/reyman64/webapps/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/application.rb:215:in `initialize!'
/home/reyman64/webapps/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/railtie/configurable.rb:30:in `method_missing'
/home/reyman64/webapps/discourse/discourse/config/environment.rb:5:in `<top (required)>'
/home/reyman64/webapps/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
/home/reyman64/webapps/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `block in require'
/home/reyman64/webapps/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:214:in `load_dependency'
/home/reyman64/webapps/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require'
/home/reyman64/webapps/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/application.rb:189:in `require_environment!'
/home/reyman64/webapps/discourse/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/application.rb:250:in `block in run_tasks_blocks'
Tasks: TOP => db:migrate => environment
There is a new config file to modify in this version ? Thanks, SR
I've configured a bridged interface in Vagrant, and my port forwards works as expected, but the VM for some reason doesn't see any traffic that didn't originate on that internal network. Ideas?
Categories drop down for smaller forum like mine is nice to have but use of "Latest" is prominent. So I was little uncomfortable with categories drop-down as first clickable element. I customized the categories drop-down to the right side and end result seems less cluttered to me.
So this is just a suggestions for anyone interested and likes it. Customization: ol.category-breadcrumb { float: right; margin: 0 0px 0 0; } ( Not 100% sure if this is the best way to achieve the same but works well)
I am attempting to write a Ruby script to disable email_digests for all users. So far, I have got a script along the following lines:
me = User.find_by_username_or_email('me@email.com')
me.email_digests = false
me.save
which will select and disable digests for a specific user. However, I am unsure how to get the script to loop over every user in the database. Any help appreciated!
We recently upgraded our discourse installation's postgres database and in doing so, it looks like the precision was lost on all timestamps. I investigated and ensured the precision is persisting via psql and it is. It appears the JSON serialization is no longer returning the decimals for times that we're seeing on other installations (as indicated in example: http://discuss.launchacademy.com/t/programming-interview-questions/86.json)
The result (I think) is an odd display of time related information:
Can anyone point me in the right direction of what might be happening here?
One feature which I miss in Discourse is the ability to mention user groups inline in posts, or when sending a private message to insert the group name rather than typing them in individually.
This feature would be greatly enhanced if groups were more than just their id field, and had a field just like users do for Full Name.
On iPad 4 (iOS 7.0.4, Safari or Chrome), when I click into the search box and the keyboard appears on screen, the whole header moves down. Here is a screenshot: http://imgur.com/0l3k1tm
PS: to trigger the bug, scroll the page up a bit before clicking the search icon.
@sam, @zogstrip, @codinghorror and the rest of the discourse team. I have already seen posts related to support for advertising and it looks minimal except for adding HTML at the top and bottom of a page. I think Discourse is a great software and I am working on launching at least two discussion forums based on this but wanted to know what kind improvements are being planned (if any) for better advertising support over the next 2-3 months. Thanks, -Dev
I noticed that the topics table has a meta_data hstore field that can be used by plugins to store data (at least, the blog plugin seems to be using it that way).
Any chance of adding something like that to the users table as well? Our use case is that we need additional data for our customized user pages (example), which I'm currently fetching by making an extra AJAX request to our Rails application, but I would prefer to remove the need for that extra request so that user pages can load faster.
But on the posts I moved there's no link-back... making it look like (to the untrained user) posts are out of order due to the post times. A link back would clarify that these posts were moved in.
Please let me know if you notice anything broken that is related to this upgrade.
The biggest change is the $.browser has been junked, which makes sense, it was hacky. But broke some of the older bootstrap.js stuff we were using. I upgraded the spots that needed fixes.
We are looking to hire someone for a series of customizations for our Discourse installation.
Initially we have a short list of simple needs for our forum's MVP (adding a couple fields to the user model, some UI tweaks, etc). If we choose to continue using Discourse, this can translate into more involved custom features.
We're building a website around a community that has no proper virtual place to gather, and we believe Discourse can be a great fit for the many discussions that will arise around all the collaboration waiting to happen.
Our ideal contractor is be very comfortable with Discourse itself, and has professional experience with the technologies involved.