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

Should views column be removed?

$
0
0

Konrad Borowski wrote:

Continuing the discussion from What should selecting each topic list field do?:

First of all, this is a thread about views column, not view count in thread itself.

Does this column provide useful information? Or could it be simply removed? First of all, there is no doubt that views column shows threads that become popular, like discussion of JavaScript vs CoffeeScript. But, is that information useful to the user?

Views column is part of forum tradition. It's practically default on many forum systems, with few exceptions where admin manually removed view column from the layout (like Pixelmator Support or CSS Tricks).

But let's take a look at it. What does view count say? To be honest, I don't know. It's just an arbitrary number for me that I always ignored. On any forum system, including Discourse. Perhaps it means something else to you (tell me if it does). Why you would care how many people viewed this particular topic before viewing it yourself? There is no doubt that lurkers are important part of Internet culture, but information about their activity isn't useful for a forum user.

There is only one advantage of view column I can think of - it can be used by thread owner to determine how much activity the topic brings. However, Discourse offers a perfectly fine solution - view counter inside the thread itself.

And if we push it, there is another advantage. It could be used by staff members to determine popular threads, for analytics purposes (like the most common referrers). On Stack Exchange, there is Tools page which shows various statistics, one of them shows most active questions (yes, I know the "questions" on this image aren't question-like, but this is https://codegolf.stackexchange.com/). This could be added to admin dashboard page, if it could be useful.

However, the view column has its disadvantages. It's yet another column in the view, confusing the users with the numbers. Without it, the main page would become cleaner. Wouldn't it be great to make thread list less confusing? In fact, I believe this is the goal, with the removal of way more useful likes column (view counter is just a rather arbitrary counter, when likes actually show if users like this thread).

One less column, and there is just one column with just numbers (the activity column doesn't quite count, as it has units) - the post count itself.Continuing the discussion from What should selecting each topic list field do?:

Posts: 7

Participants: 7

Read full topic


Failed to bootstrap

$
0
0

wrote:

Just ran the upgrade via /admin/upgrade only it stopped half way through and said it had failed. so i did a refresh and the site was not working.

went into ssh and ran ./launcher rebuild app only for it to fail to bootstrap. not sure where what to do from here.

2014-08-19 01:43:50 UTC LOG:  received smart shutdown request
2014-08-19 01:43:50 UTC LOG:  autovacuum launcher shutting down
[179 | signal handler] (1408412630) 2014-08-19 01:43:50 UTC LOG:  shutting down
Received SIGTERM, scheduling shutdown...
2014-08-19 01:43:51 UTC LOG:  database system is shut down
[179] 19 Aug 01:43:51.051 # User requested shutdown...
[179] 19 Aug 01:43:51.051 * Saving the final RDB snapshot before exiting.
[179] 19 Aug 01:43:51.210 * DB saved on disk
[179] 19 Aug 01:43:51.211 # Redis is now ready to exit, bye bye...
/pups/lib/pups/exec_command.rb:85:in `spawn': cd /var/www/discourse && sudo -E -u discourse bundle exec rake db:migrate failed with return #<Process::Status: pid 405 exit 1> (RuntimeError)
	from /pups/lib/pups/exec_command.rb:55:in `block in run'
	from /pups/lib/pups/exec_command.rb:53:in `each'
	from /pups/lib/pups/exec_command.rb:53:in `run'
	from /pups/lib/pups/command.rb:6:in `run'
	from /pups/lib/pups/config.rb:85:in `block (2 levels) in run_commands'
	from /pups/lib/pups/config.rb:76:in `each'
	from /pups/lib/pups/config.rb:76:in `block in run_commands'
	from /pups/lib/pups/config.rb:75:in `each'
	from /pups/lib/pups/config.rb:75:in `run_commands'
	from /pups/lib/pups/config.rb:71:in `run'
	from /pups/lib/pups/cli.rb:31:in `run'
	from /pups/bin/pups:8:in `<main>'
9bd602a52aa3d827d619d0d7dd949d7a4b26d406abdf1853c8150ee3a1ac7e9a
FAILED TO BOOTSTRAP

Posts: 8

Participants: 4

Read full topic

Polls do not work in zh_CN locale

$
0
0

Ordinary wrote:

If you turn the basic site setting of language into Chinese(zh_CN) ,polls will no longer working.

I used aws ec2(hvm ubuntu).Everything was allright when I tried this on Digital Ocean last month.

BTW I used it with docker

Posts: 5

Participants: 2

Read full topic

Add sso_overrides_avatar option for SSO Plugin

So, you want to help out with Discourse

$
0
0

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

JavaScript projects

Mixed projects

  • Improve general polish.
  • 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: 22

Participants: 12

Read full topic

"You have no unread topics" is a lie

$
0
0

Michael Downey wrote:

Personally, the whole "Unread" concept has always confused me, even as a power user/admin of a Discourse site. I just clicked over to the "Unread" tab a moment ago, and saw the following:

Now, I haven't read all the topics on Meta -- not by far. But I'm being told I have no unread topics? Lies!

Surely there's a better way to explain this to confused users like me?

Posts: 14

Participants: 10

Read full topic

Double Likes... as a feature!

$
0
0

Matches wrote:

Posts: 5

Participants: 4

Read full topic

Further simplifying the columns: quality score > view count

$
0
0

Adam Capriola wrote:

Continuing the discussion from Suggestion: # of likes in a topic in the tool tip:


I'm digging the removal of the Likes column (the glyph being gone in particular make the display less noisy), however I do think @boomzilla makes a good point that views aren't all that well quantified. (What is a view? Are there different types of views? What does each individual view mean?)

I think the goal of showing stats, like the number of views and likes, is to convey some information about the quality of a topic. If it's a particularly engaging discussion, it should stand out from the rest.

Any notion I have of what a view count implies is the result of years of frequenting forums and coming up with some arbitrary notions in my head that certain disparities between posts and views are good or bad. (The same can be said for posts vs. likes.) I have no idea how accurate my assumptions are and this unknowingness is part of the reason @codinghorror wanted to use a ratio to give likes more meaning.

But the heatmap on the posts column so far isn't indicating to me at all a ratio of posts versus likes. It does stand out to me though and seems to be calling to me that a topic is, well, hot. Hot in the sense that it's a topic to be looked at; a quality topic.

I know there are discussions on fixing the heatmap to be more telling, but why not instead remove the views column too and come up with some kind of "quality score" that incorporates likes and views. Use that quality score to assign the heatmap to the posts column. Keep the coldmap for now simplified activity column and I think it will be easy to glean info at a glance. (Hot and cold together means the topic has had staying power. Etc.)

Views and likes without context are somewhat crummy indicators. Even with context (a post count), how reasonable is it to expect users to come up with the same conclusion about what they mean? I think creating a universal metric is worth consideration. The individual stats can still be displayed within the topic and I'm assuming at some point there will be advanced searching with sorting by views and likes and whatnot, for those who want to do so.

Posts: 13

Participants: 10

Read full topic


What should make the notification bubble go away?

$
0
0

Adam Capriola wrote:

Continuing the discussion from You may miss a notification if you are actively on a topic


This is somewhat related and I want to confirm whether this functionality is intended. I'm calling notifications.json through the API so that I can display if a user has any unread notifications on the non-Discourse portion of my website. I've noticed that when I get a new notification and click over to Discourse, the blue notification bubble doesn't appear (which is not ideal). The notifications are unread though when I do click to view them (they are highlighted blue).

I'm guessing that because notifications.json was accessed with an API call, that's why the bubble was cleared (it's as if I clicked to view the list of notifications).

Should the bubble clear just by clicking to view the list of notifications or should it remain until each notification is clicked on (acknowledged)? I'm uncertain how the major social networks are handling this functionality these days. I could see if a user had a lot of notifications that it would be annoying to have to click on all of them to make the bubble indicator go away, but on the other hand having to actually view all them would possibly keep users more engaged in discussions.

Posts: 7

Participants: 4

Read full topic

Allow option to switch display order

$
0
0

Stuart Alexander wrote:

Depending on the type and length of a topic, often I want to see the last post, not the first one. I know there's a "go to bottom" feature, but I don't find this is particularly obvious or user friendly.
I would like a button near the top of a post to change the sort order from first-first to last-first.

Posts: 4

Participants: 3

Read full topic

Allow switching of categories in a topic

$
0
0

Stuart Alexander wrote:

Currently when I am in a topic, I am limited with what I can do. I can't create a new topic and I can't switch to a different category.
This forces me to press back or click on the category / header to return to root menu and then switch to a new category.

Posts: 5

Participants: 3

Read full topic

Duplicate notifications

Plugin not correctly loaded

$
0
0

Matti Nelimarkka wrote:

Hi,

I'm developing my own plugin and check to check how it's done copied the discourse-alert code to examine and explore it a bit. I installed the code using rake, cleaned my assets and restarted the server.

However, it seems that the plugin is not correctly loaded, is there some sort of configuration I need to make these plugins to work?

Posts: 4

Participants: 2

Read full topic

Attachment icon

Notifications not clearing properly unless visited from menu

$
0
0

TechnoBear wrote:

New notifications in the notification menu show blue until visited, but the behaviour is erratic and sometimes they will only clear if the menu link itself is followed, not if the topic has been visited by another rouite. This occurs both here and on our own site, but the behaviour is inconsistent/intermittent and I can't find a reliable way to reproduce it.

This is an issue because the notification menu is not easy to use by keyboard. The shortcut which opens it does not give focus, so links can only be accessed by tabbing through from the top each time. I generally use j/k navigation to move through new/updated topics and just check the dropdown periodically to ensure I haven't missed anything. The fact that sometimes the blue highlighting clears and sometimes it doesn't just makes this confusing and unreliable.

Posts: 1

Participants: 1

Read full topic


Import users and post from other forums

$
0
0

Eliseo Soto wrote:

Are there any plans to add a feature to migrate an existing forum to Discourse?

I'm currently using myBB and I migrated from phpBB and it wasn't too bad.

Posts: 48

Participants: 29

Read full topic

Problem Embedding Comments

$
0
0

Thomas Wilson wrote:

I'd like to use discourse comments in my ghost blog (using @eviltrout's instructions here) -- until recently, this has been working smoothly as expected. After re-importing my blog content with slightly different slugs, it started complaining that the X-Frame-Options header on discourse was set to 'SAMEORIGIN', preventing any x-site communication.

I followed the instructions here and the error has since disappeared, only to be replaced by another.

In my developer console, I now see a 403 Forbidden error:

GET http://discourse.muselive.com/embed/comments?embed_url=http%3A%2F%2Fghost.muselive.com%2Falbum-number-7-on-its-way-1393155960%2F 403 (Forbidden)

followed by:

Uncaught TypeError: Cannot read property 'forEach' of undefined
Uncaught TypeError: Cannot read property 'create' of undefined    discourse.muselive.com/assets/vendor-3c0b29078a0c6673dd5ae1991a1fc9a6.js:12

Could this be a problem with my ghost install or with discourse? Has anyone else come across this issue? Example page which doesn't work here.

Any help would be appreciated - thanks.

Posts: 7

Participants: 3

Read full topic

New (2) does not update when "Dismiss New" is used in another tab

$
0
0

wrote:

Steps to reproduce:

  • Open two browser tabs, when there are new topics. One shows Latest, the other shows New (2).
  • Press Dismiss New on the second tab.

Expected behavior: On both tabs "New (2)" should become "New" as it happens when I visit both new topics.

Actual behavior: Only on the second tab (where I pressed Dismiss New) the label changes to "New". On the first tab it stays unchanged "New (2)". Of course, when I visit it, there are no new topics.

This may be related to ‘New (3)’ shows no topics.
The same problem also occurs on the Unread tab with the Dismiss buttons.

Posts: 1

Participants: 1

Read full topic

Strange behaviour of emoticons in character count

Set Title dialog shows multiple instances of the same badge

Viewing all 60721 articles
Browse latest View live




Latest Images