Martin H. Normark wrote:
Do you plan to add keyboard shortcuts to Discource?
Off the top of my head:
Within the list of topics view
j: Move the selection indicator in the table up
k: Move the selection indicator in the table down
enter: Open the topicWithin a topic
j: Scroll to the message above
k: Scroll to the message below
l: Like
s: Share
b: Bookmark
r: Reply
n: Reply as new topicWithin the editor
Esc: Cancel
Posts: 19
Participants: 12
Johan Storm wrote:
Would be good if external urls open in new tab (or an option when creating new hyperlink to either open in same frame or new) as user might "drift away" otherwise? Maybe there is an option for this but have not found it?
Posts: 7
Participants: 6
Michael wrote:
Since we updated to 0.9.8, we have problems creating new accounts.
The error message users are getting is "Something went wrong, perhaps this email is already registered, try the
forgot password link"
production_errors.logshows<backtrace>[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/redis-3.0.6/lib/redis/client.rb:85:in `call' [RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/redis-3.0.6/lib/redis.rb:1205:in `block in sadd' [RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/redis-3.0.6/lib/redis.rb:36:in `block in synchronize' /usr/local/rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize' [RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/redis-3.0.6/lib/redis.rb:36:in `synchronize' [RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/redis-3.0.6/lib/redis.rb:1204:in `sadd' [RAILS_ROOT]/lib/common_passwords/common_passwords.rb:44:in `load_passwords' [RAILS_ROOT]/lib/common_passwords/common_passwords.rb:33:in `block in password_list' [RAILS_ROOT]/lib/common_passwords/common_passwords.rb:32:in `synchronize' .... [RAILS_ROOT]/vendor/bundle/ruby/2.0.0/bin/thin:23:in `<main>'</backtrace> <message>ERR wrong number of arguments for 'sadd' command</message> <url>http://test1101b.discoursehosting.net/users</url> <exception-class>Redis::CommandError</exception-class> </hash>When removing line 44 (redis.sadd) from common_passwords.rb the problem goes away.
def self.load_passwords passwords = File.readlines(PASSWORD_FILE) redis.sadd LIST_KEY, passwords[0,5000].map!(&:chomp) rescue Errno::ENOENT # tolerate this so we don't block signups Rails.logger.error "Common passwords file #{PASSWORD_FILE} is not found! Common password checking is skipped." endThe
10k-common-passwords.txtfile is there, and it's readable.Anyone have any idea what is going on here?
Posts: 10
Participants: 4
Vikhyat Korrapati wrote:
Is there any way to exclude a category from the "top" view? The -categoryname that we're using for the latest section doesn't seem to be working.
Posts: 4
Participants: 3
Hrishikesh Thakre wrote:
For regular users of a forum "New" tab works best and is used widely. They may have bookmarked the best comments and Favorited the topics. The current system works like charm for regulars.
But for new users the current setup seems little lost.
- He is presented with "new" and "categories" tab. But both contains more and less same information. Newest topics / new topics by category.
- "New" tab is about the current discussions which necessarily does not mean the best discussion and it won't reflect the depth or the best of a forum.
- Categories also have topics sorted by age only. So other than knowing the high level setup of forum no more information is provided to user from second tab
- There is no section or tab to represent most liked topics, most discussed topics, editorial /admin marked topics.
We have pinning feature, but it reflects Important note, attention rather than the best quality topics.
We need little more flexibility to showcase site's depth and quality. My suggestions are:
Provide settings where admin can pre-select the sort order for topics shown in categories tab (and topics of single category on selction). That will solve some part of problems. (Admin can decide if it is views, likes, no of comments which he thinks is important for his forum.)
Extra Tab for Editorial /Admin marked Best of Topics. (many forums are still one man army (very few users) )
Tab for Favorited topics by all users
I think first one should be easy, other two can be debated.
Posts: 23
Participants: 7
Jacob wrote:
Continuing the discussion from I deleted "uncategorized". Is this bad?:
Uncategorized is still showing up in the hamburger menu for everyone even though we have it not allowed and admins/mods still see the uncategorized category with no posts, just avatars on the Category page.
Posts: 4
Participants: 3
printec wrote:
I did a clean install on Centos 6.5 64 bit with following shell commands ran as root:
$ ./printec-basic-setup.sh
$ ./discourse-install.shRather than flood this post with bash commands I have uploaded my script contents to media fire (see below).
When I point browser to the webpage I get this error:
It looks like Bundler could not find a gem. This is probably because your application is being run under a different environment than it's supposed to. Please check the following: * Is this app supposed to be run as the `discourse` user? * Is this app being run on the correct Ruby interpreter? Below you will see which Ruby interpreter Phusion Passenger attempted to use. * Are you using RVM? Please check whether the correct gemset is being used. * If all of the above fails, try resetting your RVM gemsets: https://github.com/phusion/passenger/wiki/Resetting-RVM-gemsets -------- The exception is as follows: ------- Could not find rake-10.1.1 in any of the sources (Bundler::GemNotFound) /usr/local/rvm/gems/ruby-2.0.0-p353/gems/bundler-1.5.2/lib/bundler/spec_set.rb:92:in `materialize' /usr/local/rvm/gems/ruby-2.0.0-p353/gems/bundler-1.5.2/lib/bundler/spec_set.rb:85:in `map!' /usr/local/rvm/gems/ruby-2.0.0-p353/gems/bundler-1.5.2/lib/bundler/spec_set.rb:85:in `materialize' /usr/local/rvm/gems/ruby-2.0.0-p353/gems/bundler-1.5.2/lib/bundler/definition.rb:133:in `specs' /usr/local/rvm/gems/ruby-2.0.0-p353/gems/bundler-1.5.2/lib/bundler/definition.rb:178:in `specs_for' /usr/local/rvm/gems/ruby-2.0.0-p353/gems/bundler-1.5.2/lib/bundler/definition.rb:167:in `requested_specs' /usr/local/rvm/gems/ruby-2.0.0-p353/gems/bundler-1.5.2/lib/bundler/environment.rb:18:in `requested_specs' /usr/local/rvm/gems/ruby-2.0.0-p353/gems/bundler-1.5.2/lib/bundler/runtime.rb:13:in `setup' /usr/local/rvm/gems/ruby-2.0.0-p353/gems/bundler-1.5.2/lib/bundler.rb:119:in `setup' /usr/local/rvm/gems/ruby-2.0.0-p353/gems/bundler-1.5.2/lib/bundler/setup.rb:17 /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in `gem_original_require' /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in `require' /opt/passenger/passenger-4.0.29/lib/phusion_passenger/loader_shared_helpers.rb:219:in `run_load_path_setup_code' /opt/passenger/passenger-4.0.29/lib/phusion_passenger/loader_shared_helpers.rb:333:in `running_bundler' /opt/passenger/passenger-4.0.29/lib/phusion_passenger/loader_shared_helpers.rb:217:in `run_load_path_setup_code' /opt/passenger/passenger-4.0.29/helper-scripts/rack-preloader.rb:96:in `preload_app' /opt/passenger/passenger-4.0.29/helper-scripts/rack-preloader.rb:153 Application root /home/discourse/discourse Environment (value of RAILS_ENV, RACK_ENV, WSGI_ENV and PASSENGER_ENV) production Ruby interpreter command /usr/bin/ruby User and groups uid=501(discourse) gid=502(discourse) groups=502(discourse),501(rvm) context=unconfined_u:system_r:httpd_t:s0 Environment variables rvm_bin_path = /usr/local/rvm/bin HOSTNAME = localhost.localdomain GEM_HOME = /home/discourse/discourse/vendor/bundle/ruby/1.8 SHELL = /bin/bash TERM = xterm HISTSIZE = 1000 IRBRC = /usr/local/rvm/rubies/ruby-2.0.0-p353/.irbrc QTDIR = /usr/lib64/qt-3.3 PASSENGER_DEBUG_DIR = /tmp/passenger.spawn-debug.XXXXxDUAYF MY_RUBY_HOME = /usr/local/rvm/rubies/ruby-2.0.0-p353 QTINC = /usr/lib64/qt-3.3/include USER = discourse _system_type = Linux rvm_path = /usr/local/rvm rvm_prefix = /usr/local MAIL = /var/spool/mail/discourse PATH = /usr/local/rvm/gems/ruby-2.0.0-p353/bin:/usr/local/rvm/gems/ruby-2.0.0-p353@global/bin:/usr/local/rvm/rubies/ruby-2.0.0-p353/bin:/usr/lib64/qt-3.3/bin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/sbin:/usr/local/rvm/bin:/home/discourse/bin PWD = /home/discourse/discourse KDE_IS_PRELINKED = 1 LANG = C KDEDIRS = /usr _system_arch = x86_64 _system_version = 6 SSH_ASKPASS = /usr/libexec/openssh/gnome-ssh-askpass HISTCONTROL = ignoredups rvm_version = 1.25.15 (stable) HOME = /home/discourse SHLVL = 2 LOGNAME = discourse QTLIB = /usr/lib64/qt-3.3/lib CVS_RSH = ssh GEM_PATH = LESSOPEN = |/usr/bin/lesspipe.sh %s _system_name = CentOS G_BROKEN_FILENAMES = 1 IN_PASSENGER = 1 PYTHONUNBUFFERED = 1 NODE_PATH = /opt/passenger/passenger-4.0.29/node_lib RAILS_ENV = production RACK_ENV = production WSGI_ENV = production NODE_ENV = production PASSENGER_APP_ENV = production SERVER_PROTOCOL = HTTP/1.1 SERVER_SOFTWARE = Apache/2.2.15 (CentOS) DOCUMENT_ROOT = /home/discourse/discourse/public SERVER_ADMIN = root@localhost QUERY_STRING = SERVER_NAME = 192.168.1.65 REMOTE_PORT = 50724 REMOTE_ADDR = 192.168.1.78 SERVER_PORT = 80 REQUEST_METHOD = GET SERVER_ADDR = 192.168.1.65 REQUEST_URI = / _ORIGINAL_GEM_PATH = /usr/local/rvm/gems/ruby-2.0.0-p353:/usr/local/rvm/gems/ruby-2.0.0-p353@globalI am really close. The problem seems to be a missing GEM_PATH. Does anyone know how to set that from Apache/Phusion?
For those who are interested my install scripts can be downloaded here in zip format.
(Pity I can't attach them to a post here but the forum doesn't allow zip file types.)
Anyone know how to get to the next step?
Thanks in advance
Regards
Glenn @ Printec
www.printec.co.nz
Posts: 1
Participants: 1
Iszi wrote:
The descriptions for the Tracking and Regular levels of topic tracking each have something to say about "replies to your post(s)". For this purpose, what constitutes a reply? There are several ways that someone might directly or indirectly reply to a post.
Topic Starter
- Posts directly referencing the topic's first post would definitely qualify as a reply.
- Any other post added to the topic may be considered a reply to the topic itself.
Topic Participant
- Posts directly referencing the participant's post(s) would definitely qualify as a reply.
- Posts immediately after the participant's post(s), which were started using the Reply button on that participant's post, will not be visibly labeled as replies even though they clearly are intended to be. Do these also qualify?
- Posts immediately after the participant's post(s), which were started using the Reply button at the bottom of the topic page, may be intended to reply to the participant's post but we cannot be sure. Do these qualify?
Posts: 2
Participants: 2
stellarhopper wrote:
So, I have been facing this problem since a while now, and as a workaround, I have had this in my cron:
/usr/bin/env PIDFILE=/var/www/discourse/tmp/pids/sidekiq-worker.pid RAILS_ENV=production bundle exec sidekiq -L /var/www/discourse/log/sidekiq.logNow this fails with:
Could not locate Gemfile
Posts: 7
Participants: 2
stellarhopper wrote:
I checked the default Discourse header logo height which was 66px.
I scaled my logo to the same height, yet it 'overflows' from the header area.Check forum.tinkermill.org to see what I mean.
This was not a problem in 0.9.7.2, but is in 0.9.7.3
Posts: 4
Participants: 2
nXqd wrote:
I think it's a good idea that we can assign a class for a body based on category name or something like that. In that way, we can customize each category to have a difference styling.
I know not everyone needs this, but it'd be nice to have.
Posts: 1
Participants: 1
Jeff Atwood wrote:
Discourse launched at version 0.8.0.0 which was my off the cuff estimate of how “done” we were with our first public release on February 5th, 2013 — about eighty percent done, I thought, once you factor in the ninety-ninety rule: The first 90 percent of the code accounts for the first 90 percent of the…
This topic is for comments on the original blog entry at: http://blog.discourse.org/2014/01/the-road-to-discourse-1-0-2/
Posts: 6
Participants: 4
srid wrote:
Continuing the discussion from The Discourse Servers:
Hi everyone,
I am now successfully running a Discourse site using Docker. All the five processes involved -- redis, postgresql, rails, sidekiq and nginx -- are run as separate containers by docker. Anybody with a Ubuntu 13.04 VM right now can give this a try; should only require a few minutes.
https://github.com/srid/discourse-docker
Please let me know your feedback. In future, we should be able to use an orchestration layer like CoreOS to make the install process even easier.
Posts: 35
Participants: 13
Abhishek Gupta wrote:
So again,
What is the problem?
I need to check user_trust_level , i get the 'username' from a form via ajax, i need to check what level he is on discourse
Also, if possible, i would like to get other details as well, like email address etc.
I took a look at : https://github.com/discourse/discourse_api , but there isn't such method available there.
So any ideas?EDIT: Never Mind, I got the solution, Thanks @eviltrout
For other wandering the same :
The above returns info the user in json format , you can check it by simply typing it in your browser .
But however, i cant see Email in it , if i log in as admin to my forums, i can see admin, but when i do tthe same logged out, it doesnt appears! . How to manage it in ajax call ?
Posts: 1
Participants: 1
Pablo Corral wrote:
Hi everyone,
I'm exploring different paths to integrate discourse with other webapps.
One interesting use case that I'm finding, is to use Discourse and it's excellent identity management capabilities, as a cetral point to id management.
The current features (user creation flow, email validation, email invitacion, oAuth support, etc) makes Discourse as a great core place to hav identity implemented.
In the case that I need to develop a new app, and I want to use discourse's user base as Identity, what's the best approach should I take?
I don't want to directly read the postgres database (or using ActiveRecord). In fact, I don't know how to read passwords or validate facebook logged users.
Do you think that having a feauture that transforms Discourses as e CAS Server it would be a good way?
Tks! appreciate your ideas!
Posts: 1
Participants: 1
Abhishek Gupta wrote:
So, i use this page to gather information and post a new topic in my instance of discourse
Page: http://awake-gaming.com/join-us.htmlForums: http://forums.awake-gaming.com/
It is working fine. But when i took a look at console, i got this :
Although in discourse.conf , under conf.d in nginx directory i have
add_header Access-Control-Allow-Origin "*" ;
But still the error, yes, the post is created in forums, but is this a bug in chrome? or in discorse?
I restarted nginx after adding those lines, is that enough? do i need to compile headers?
@codinghorror ?
Posts: 1
Participants: 1
Peter Jaros wrote:
A few related things here, let me know if they need breaking out:
I can't figure out how to tab to the Category dropdown. I expect it to come after the title, but tabbing from the title goes directly to the post body.
Tabbing from the post body goes…somewhere. I'm not sure where. Wherever it is, it needs a focus style. Tabbing a few more times takes me to more mystery places which I can't locate because they don't have focus styles.
It would also be nice if Cmd-Return / Ctrl-Enter from the post body was "Create Topic"/"Reply". That's become pretty conventional: Gmail and GitHub both use it.
Posts: 4
Participants: 4
Julien Dumétier wrote:
The category url includes the name 'category' which is long to type and only work in english. May it be replaced by /c/ or something custom ?
Posts: 12
Participants: 9
ComputerDruid wrote:
Middle clicking (to open in a new tab) on a topic triggers Firefox's pop-up blocker.
This doesn't make sense to me, given that middle clicking on an ordinary link opens in a new tab without this. Is discourse intercepting middle-clicks somehow?
Right-clicking on the link (if you aim VERY carefully), and selecting "Open in new tab" works as expected, but this is a pain compared to the much-easier-to-execute middle click.
Edit: You don't actually have to aim carefully to right-click on the link, you have to right-click twice. The first right-click acts as if you'd right-clicked on the page, and the second one as if you'd right-clicked a link. Right-clicking before middle-clicking also works. This is really weird.
Posts: 24
Participants: 11
Stuart Langridge wrote:
I'd like to be able to, via the API, create a Discourse topic but not have it show up until a defined time in the future. This is really handy for things like announcement posts, so I can create a new topic to announce a thing at some point before the release of the thing, and have the forum discussion become available automatically at release time without me having to do anything. Has this sort of feature been discussed? (I did take a glance at the code, but I'm not really a Ruby guy, and I fear walking through the code and changing every single request for a topic to include "
and publish_time <= now"...)
Posts: 2
Participants: 2
