User Notes on Profile Page

February 11, 2014, 3:29 pm

≪ Previous: Download Archive of My Posts Implementation

Continuing the discussion from Profile Comments:

cpradio said:

This may be a slightly different idea, but in vBulletin there is a feature known as "User Notes" that can only be seen/entered by members with certain privileges (think moderators/admins). We use these notes to indicate whether a person is worth watching, requires an infraction on the next violation of the rules, etc.

It would be nice to have something similar in Discourse.

Is this on a road map? Because if it isn't, I'm fairly certain the devs at SP are likely going to build it. I'm just curious if there are any plans for this (since @codinghorror and @sam liked it).

Posts: 2

Participants: 2

Read full topic

↧

LDAP login into Discourse

July 26, 2013, 4:30 am

≫ Next: Discourse Spoiler Alert

≪ Previous: User Notes on Profile Page

Roni Baby wrote:

Can you possible to integrate LDAP login into Discourse? If possible let me know the steps
We are using Discourse in Ubuntu 12.04LTS server

Thanks
Roni

Posts: 12

Participants: 7

Read full topic

↧

Discourse Spoiler Alert

February 11, 2014, 7:47 pm

≫ Next: Discourse Emoji

≪ Previous: LDAP login into Discourse

Sam Saffron wrote:

Location: https://github.com/discourse/discourse-spoiler-alert
Created by: @zogstrip

Live Demo

This is a spoiler

Also works for images.

Posts: 1

Participants: 1

Read full topic

↧

Discourse Emoji

February 11, 2014, 7:49 pm

≫ Next: Discourse Docker Manager Plugin

≪ Previous: Discourse Spoiler Alert

Sam Saffron wrote:

Location: Main repo https://github.com/discourse/discourse/tree/master/plugins/emoji
Author: Discourse team

Demo:

Posts: 1

Participants: 1

Read full topic

↧

Discourse Docker Manager Plugin

February 11, 2014, 8:58 pm

≫ Next: Sam's Blog Plugin

≪ Previous: Discourse Emoji

Sam Saffron wrote:

Location: https://github.com/discourse/docker_manager

Author: @sam

Provides basic monitoring and upgrade facilities to Discourse instances hosted using our Docker template: https://github.com/discourse/discourse_docker

Screen Shot:

Pasted image1120x838 104 KB

Posts: 1

Participants: 1

Read full topic

↧

Sam's Blog Plugin

February 11, 2014, 9:01 pm

≫ Next: Programmatically inviting users

≪ Previous: Discourse Docker Manager Plugin

Sam Saffron wrote:

Location: https://github.com/samsaffron/blog

Author: @sam

A Rails engine implemented as a Discourse plugin, provides a completely different front end to Discourse.

Pasted image1069x1090 152 KB

See also: http://samsaffron.com

Posts: 1

Participants: 1

Read full topic

↧

Programmatically inviting users

February 11, 2014, 6:34 pm

≫ Next: Suggestion: Short description on main page and category pages

≪ Previous: Sam's Blog Plugin

Phil Nelson wrote:

We have a need to invite about 100 users (and eventually about 3000 more) to our discourse install, and my ruby/rails is super rough. I searched around on the forums and couldn't find a good example. How might someone invite users to the forums in an automated way, from a list or even just on the command line? I'm not even really worried about sending an invite email, but creating the user and assigning an invite code.

Posts: 2

Participants: 2

Read full topic

↧

Suggestion: Short description on main page and category pages

March 31, 2013, 5:32 pm

≫ Next: Posting API Returns Invalid Access

≪ Previous: Programmatically inviting users

David McClure wrote:

I poked around at a few of the other forums out there running discourse and something struck me - it wasn't clear what the forums were about. This 'meta' forum solves the problem with the pinned Welcome topic.

While looking around at other forums, its clear that this isn't universally done, though.

It feels like having some short about section that states what the forum is about would make sense.

Other forums help solve this by including excerpts of the posts or descriptions of the categories on the main page. But I have seen in other posts that this was experimented with here on Discourse before being deemed to be too much clutter (which I agree with).

On the Categories page, something similar may be appropriate. Currently, the description is shown when the mouse hover's over the label, but I know there is a desire to make everything work without hovers since tablets are a first class citizen.

So I think a simple 'what is this forum about' line above the list of topics could be a good way to address this in all cases. I've attached a mockup of what the meta.discourse.org FAQ category page may look like after doing this.

325388027663b6ae.png1270x514

Or perhaps the description line belongs above the row of Filter tabs and Create button...

f655bd54fb7ebca6.png1270x514

Posts: 22

Participants: 6

Read full topic

↧

Posting API Returns Invalid Access

February 11, 2014, 9:10 pm

≫ Next: Ubuntu Single Sign On

≪ Previous: Suggestion: Short description on main page and category pages

whatasunnyday wrote:

Hello!

I've been messing around with the discourse api and I'm running into issues using it. I managed to setup discourse on my machine with the specs running correctly. When I try to to an invite a user to a topic using the api, it returns invalid access. Can someone take a look at my cURL and see if they can see what's wrong?

curl --data "email=admin@mailinator.com&topic_id=1&api_key=f8a279f3febc97c20e423e44aa0c7ae57797ee3f13f97e051735443fc2dbd633&api_username=eviltrout" http://localhost:3000/t/1/invite.json

It returns [error: 'invalid access']%.

The server log looks like this:

Started POST "/t/1/invite.json" for 127.0.0.1 at 2014-02-11 21:04:34 -0800
Processing by TopicsController#invite as JSON
  Parameters: {"email"=>"admin@mailinator.com", "topic_id"=>"1", "api_key"=>"f8a279f3febc97c20e423e44aa0c7ae57797ee3f13f97e051735443fc2dbd633", "api_username"=>"eviltrout"}
Can't verify CSRF token authenticity
  ApiKey Load (1.4ms)  SELECT "api_keys".* FROM "api_keys" WHERE "api_keys"."key" = 'f8a279f3febc97c20e423e44aa0c7ae57797ee3f13f97e051735443fc2dbd633' ORDER BY "api_keys"."id" ASC LIMIT 1
  User Load (1.4ms)  SELECT "users".* FROM "users" WHERE "users"."id" IN (24)
   (1.3ms)  SELECT "groups"."name" FROM "groups"
   (1.7ms)  SELECT categories.id FROM "categories" WHERE "categories"."read_restricted" = 't'
  Category Load (1.6ms)  SELECT "categories".* FROM "categories" WHERE (NOT categories.read_restricted or categories.id in (13)) ORDER BY "categories"."position" ASC
  Topic Load (1.6ms)  SELECT id, title, slug FROM "topics" WHERE ("topics"."deleted_at" IS NULL) AND "topics"."id" IN (10, 11, 12, 13, 41, 42, 43, 44, 45, 46, 47, 56, 55)
   (1.4ms)  SELECT "categories"."id" FROM "categories"
  PostActionType Load (1.3ms)  SELECT "post_action_types".* FROM "post_action_types" ORDER BY position asc
  SiteContent Load (1.5ms)  SELECT content FROM "site_contents" WHERE "site_contents"."content_type" = 'top' ORDER BY "site_contents"."content_type" ASC LIMIT 1
  SiteContent Load (1.4ms)  SELECT content FROM "site_contents" WHERE "site_contents"."content_type" = 'bottom' ORDER BY "site_contents"."content_type" ASC LIMIT 1
   (1.2ms)  SELECT COUNT(*) AS count_all, notification_type AS notification_type FROM "notifications" WHERE "notifications"."user_id" = $1 AND (id > 0 and read = false) GROUP BY notification_type  [["user_id", 24]]
   (1.1ms)  SELECT COUNT(*) FROM "notifications" WHERE "notifications"."user_id" = $1 AND (read = false AND notification_type = 6)  [["user_id", 24]]
  UserStat Load (1.2ms)  SELECT "user_stats".* FROM "user_stats" WHERE "user_stats"."user_id" = $1 ORDER BY "user_stats"."user_id" ASC LIMIT 1  [["user_id", 24]]
   (1.1ms)  SELECT COUNT(*) FROM "topics" WHERE ("topics"."deleted_at" IS NULL) AND "topics"."user_id" = $1  [["user_id", 24]]
   (4.1ms)   SELECT u.id AS user_id, topics.id AS topic_id, topics.created_at, highest_post_number, last_read_post_number, c.name AS category_name
 FROM users u
 FULL OUTER JOIN topics ON 1=1
 LEFT JOIN topic_users tu ON tu.topic_id = topics.id AND tu.user_id = u.id
 LEFT JOIN categories c ON c.id = topics.category_id
 WHERE u.id IN (24) AND
 topics.archetype <> 'private_message' AND
 ((tu.last_read_post_number < topics.highest_post_number AND COALESCE(tu.notification_level, 1) >= 2) OR (topics.created_at >= CASE
 WHEN COALESCE(u.new_topic_duration_minutes, 2880) = -1 THEN u.created_at
 WHEN COALESCE(u.new_topic_duration_minutes, 2880) = -2 THEN COALESCE(u.previous_visit_at,u.created_at)
 ELSE ('2014-02-12 05:04:34.520719'::timestamp - INTERVAL '1 MINUTE' * COALESCE(u.new_topic_duration_minutes, 2880))
 END AND tu.last_read_post_number IS NULL AND COALESCE(tu.notification_level, 2) >= 2)) AND
 (topics.visible OR u.admin OR u.moderator) AND
 topics.deleted_at IS NULL AND
 ( category_id IS NULL OR NOT c.read_restricted OR category_id IN (
 SELECT c2.id FROM categories c2
 JOIN category_groups cg ON cg.category_id = c2.id
 JOIN group_users gu ON gu.user_id = u.id AND cg.group_id = gu.group_id
 WHERE c2.read_restricted )
 )


  ApiKey Exists (1.7ms)  SELECT 1 AS one FROM "api_keys" WHERE "api_keys"."key" = 'f8a279f3febc97c20e423e44aa0c7ae57797ee3f13f97e051735443fc2dbd633' LIMIT 1
  Topic Load (1.9ms)  SELECT "topics".* FROM "topics" WHERE ("topics"."deleted_at" IS NULL) AND "topics"."id" = 1 ORDER BY "topics"."id" ASC LIMIT 1
  Rendered text template (0.0ms)
Completed 403 Forbidden in 52ms (Views: 0.5ms | ActiveRecord: 26.8ms)

Posts: 1

Participants: 1

Read full topic

↧

Ubuntu Single Sign On

February 11, 2014, 9:13 pm

≫ Next: Category definition for Plugin

≪ Previous: Posting API Returns Invalid Access

Sam Saffron wrote:

Location: https://github.com/marcoceppi/discourse-ubuntu-sso

Author: @marcoceppi / @sam

Ubuntu one login support for your forum.

Posts: 1

Participants: 1

Read full topic

↧

Category definition for Plugin

February 11, 2014, 7:35 pm

≫ Next: Expanding to drive mailing lists

≪ Previous: Ubuntu Single Sign On

Sam Saffron wrote:

One post per plugin! Only plugin owners should post here.

If you have a plugin that should move here please flag your post.

Note

Plugin authors should all have the permission to post topics here, if you are a plugin author please contact @sam via a PM so I can add you to the plugin_author group.

Posts: 1

Participants: 1

Read full topic

↧

Expanding to drive mailing lists

February 5, 2013, 5:47 pm

≫ Next: Rake Aborted Issue After Setup - Using Discourse Docker

≪ Previous: Category definition for Plugin

Bob Watson wrote:

If this is the evolution of the discussion forum - is it possible that a later plugin API (or even core feature) would be able to expand to driving discussion email lists to replace our crusty old listservs?

Posts: 36

Participants: 15

Read full topic

↧

Rake Aborted Issue After Setup - Using Discourse Docker

January 20, 2014, 2:20 pm

≫ Next: Pre-loading any link on the onmousedown event

≪ Previous: Expanding to drive mailing lists

DAB Lucide wrote:

I'm running the Discourse Docker setup and it will not let me use the rake command. I first found this out when I tried to install the Adsense Plugin I ran the rake command with and without the bundle exec and it always aborts the task.

Without bundle exec

root@cid:/var/www/discourse# rake plugin:install repo=http://github.com/discoursehosting/discourse-adsense --trace
rake aborted!
You have already activated rake 0.9.6, but your Gemfile requires rake 10.1.1. Using bundle exec may solve this.
/usr/local/lib/ruby/gems/2.0.0/gems/bundler-1.3.5/lib/bundler/runtime.rb:33:in `block in setup'
/usr/local/lib/ruby/gems/2.0.0/gems/bundler-1.3.5/lib/bundler/runtime.rb:19:in `setup'
/usr/local/lib/ruby/gems/2.0.0/gems/bundler-1.3.5/lib/bundler.rb:120:in `setup'
/usr/local/lib/ruby/gems/2.0.0/gems/bundler-1.3.5/lib/bundler/setup.rb:7:in `<top (required)>'
/usr/local/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:135:in `require'
/usr/local/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:135:in `rescue in require'
/usr/local/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:144:in `require'
/var/www/discourse/config/boot.rb:6:in `<top (required)>'
/usr/local/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/local/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/var/www/discourse/config/application.rb:1:in `<top (required)>'
/usr/local/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/local/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/var/www/discourse/Rakefile:5:in `<top (required)>'
/usr/local/lib/ruby/2.0.0/rake/rake_module.rb:25:in `load'
/usr/local/lib/ruby/2.0.0/rake/rake_module.rb:25:in `load_rakefile'
/usr/local/lib/ruby/2.0.0/rake/application.rb:604:in `raw_load_rakefile'
/usr/local/lib/ruby/2.0.0/rake/application.rb:89:in `block in load_rakefile'
/usr/local/lib/ruby/2.0.0/rake/application.rb:160:in `standard_exception_handling'
/usr/local/lib/ruby/2.0.0/rake/application.rb:88:in `load_rakefile'
/usr/local/lib/ruby/2.0.0/rake/application.rb:72:in `block in run'
/usr/local/lib/ruby/2.0.0/rake/application.rb:160:in `standard_exception_handling'
/usr/local/lib/ruby/2.0.0/rake/application.rb:70:in `run'
/usr/local/bin/rake:37:in `<main>'

With bundle exec

root@cid:/var/www/discourse# bundle exec rake plugin:install repo=http://github.com/discoursehosting/discourse-adsense --trace
rake aborted!
uninitialized constant Annotate
/var/www/discourse/lib/tasks/auto_annotate_models.rake:33:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/engine.rb:641:in `block in run_tasks_blocks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/engine.rb:641:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/engine.rb:641:in `run_tasks_blocks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/application.rb:244:in `run_tasks_blocks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.2/lib/rails/engine.rb:446:in `load_tasks'
/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/Rakefile:7:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/rake_module.rb:25:in `load'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/rake_module.rb:25:in `load_rakefile'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:637:in `raw_load_rakefile'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:94:in `block in load_rakefile'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:165:in `standard_exception_handling'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:93:in `load_rakefile'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:77:in `block in run'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:165:in `standard_exception_handling'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/lib/rake/application.rb:75:in `run'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.1.1/bin/rake:33:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/rake:23:in `load'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/rake:23:in `<main>'

I decided to check to see if I had bundler installed, which it appears I do.

root@cid:/var/www/discourse# gem list

*** LOCAL GEMS ***

bigdecimal (1.2.0)
bundler (1.3.5)
io-console (0.4.2)
json (1.7.7)
minitest (4.3.2)
psych (2.0.0)
rake (0.9.6)
rdoc (4.0.0)
rubygems-update (2.1.11)
test-unit (2.0.0.0)

Any ideas on why this is happening and how to resolve it? Thanks.

Posts: 14

Participants: 5

Read full topic

↧

Pre-loading any link on the onmousedown event

February 12, 2014, 4:03 am

≫ Next: Discourse Meetup in Madrid

≪ Previous: Rake Aborted Issue After Setup - Using Discourse Docker

5an1ty wrote:

For more information http://instantclick.io/

Does discourse do this already? Seems to me like a guaranteed increase in perceived performance!

If you preload on mouse down, there is no risk of pre-loading pages you don't need.

Edit: never-mind this probably wouldn't work with all the dynamic content discourse has.

Posts: 1

Participants: 1

Read full topic

↧

Discourse Meetup in Madrid

July 30, 2013, 1:16 pm

≫ Next: Is "Extensibility" meant for discussing prospective plugins?

≪ Previous: Pre-loading any link on the onmousedown event

Pablo Corral wrote:

Hi all,

I would like to meet people using/working/exploring Discourse in Madrid.

I'am happy to organize a meeting between September and October, in the most convenient moment when we have at least 10 participants.

Please, shout if you are interested in participate on it.

Regards,
Pablo

Posts: 23

Participants: 12

Read full topic

↧

Is "Extensibility" meant for discussing prospective plugins?

February 12, 2014, 6:08 am

≫ Next: Landing page for 'not logged in' users of private categories

≪ Previous: Discourse Meetup in Madrid

Erlend Sogge Heggen wrote:

Description of Feature category:

Discussion about features or potential features of Discourse: how they work, why they work, etc.

Description of Extensibility category:

Topics about extending the functionality of Discourse with plugins, themes, add-ons, or other mechanisms for extensibility.

Scenario 1

I have this great new feature idea for Discourse, but I'm proposing it as something that should be made as a plugin because I have no desire to see it added to core, ever.

Where should I post?

Scenario 2

I have posted to the Feature category about a suggested new core feature for Discourse but the general consensus of the thread is that this feature should exist as a plugin.

Should the thread be moved?

Posts: 1

Participants: 1

Read full topic

↧

Landing page for 'not logged in' users of private categories

February 11, 2014, 1:37 am

≫ Next: Viewing open / archived or closed topics

≪ Previous: Is "Extensibility" meant for discussing prospective plugins?

Michael Jonker wrote:

At present, if a user follows a link from an email notification to a topic in a private group, they get to the landing page saying that the content does not exist.

If the content does exist, but is private, it would be good to display a message saying 'log in to view' and present a login box.

Posts: 3

Participants: 3

Read full topic

↧

Viewing open / archived or closed topics

January 12, 2014, 10:16 pm

≫ Next: User Avatar should have a dropdown menu

≪ Previous: Landing page for 'not logged in' users of private categories

Sam Saffron wrote:

FYI I added a "hidden" query string so you can filter down topic lists to open / closed or archived topics.

For example, the following will display all the open bugs in meta.

https://meta.discourse.org/category/bug/l/latest/more?status=open

Posts: 5

Participants: 3

Read full topic

↧

User Avatar should have a dropdown menu

August 6, 2013, 3:01 pm

≫ Next: Clicking logo doesn't always take you to top of home page

≪ Previous: Viewing open / archived or closed topics

Luke S wrote:

Just what the title says. In the user-bar (upper right, in english) the avatar icon, which currently links to [username]/activity, should have a dropdown menu, similar to all the other items in the user-bar.

Some targets available from the menu should be:

Activity

Preferences

Messages

Logout

As (if) it becomes available, I would add:

Drafts
Such a menu is a fairly standard feature of websites today, and would be consistent with the styling of the user-bar. Also, it is weird to make me go to another page to logout.

Posts: 3

Participants: 3

Read full topic

↧

Clicking logo doesn't always take you to top of home page

February 12, 2014, 2:27 am

≫ Next: Icon in category label: how can I add them?

≪ Previous: User Avatar should have a dropdown menu

probus wrote:

Continuing the discussion from Scroll position is no longer being maintained when navigating to a topic:

eviltrout said:

Fixed!

github.com

FIX: Was not resuming scroll position on back button

by eviltrout on 08:17PM - 11 Feb 14

changed 1 files with 10 additions and 1 deletions.

I believe this fix caused that when clicking the logo the user is taken back to the same scroll position. Clicking the logo should take the user to top of the home page (latest by default), not replicate back button behaviour.

Posts: 7

Participants: 5

Read full topic

↧

Scenario 1

Scenario 2

Latest Images