Our members on three different forums are regularly confused by how a new vote in a poll marks a topic unread. And even experiened members like myself find it to be annoying.

Since we're not really seeing the logic in it ourselves, we would like to disable it.

Could we please get such an option or could you think about a different way of presenting this in a better way in the not so distant future?

You can stop a poll from being bumped by a vote in the individual forum settings...

But technically speaking, a vote in a poll means there is something new in there that the user hasn't seen... So it IS unread.

You can stop a poll from being bumped by a vote in the individual forum settings...

Bumping is not the problem. I know of that setting and we do not have it enabled anywhere. ;)

But technically speaking, a vote in a poll means there is something new in there that the user hasn't seen... So it IS unread.

Technically it may be true, but that's not how we and our members expect it to behave ;)

Our experience suggests that most people finds it confusing.

This is something I have had several clients rage on.

I would like to see an option, at minimum a power setting, to avoid this behavior.

I agree.

Agreed, surely there should be an option but I didn't suggest this 2 years ago.

I have often gone into a thread with a poll looking for a new reply for it to only be a new vote.

+1

I personally like it the way it is. If someone new has voted, that means the poll has been updated, so it should be considered as having 'new' content in my eyes.

I personally like it the way it is. If someone new has voted, that means the poll has been updated, so it should be considered as having 'new' content in my eyes.

But how about when a poll is often voted in? There a times when there come new votes like every minute.

The unread link is funny though, it will always take you to the last post in this case, there is no actual unread content, you have to scroll up to see that it was a poll vote often. Showing there have been new votes is one thing, but tied into unread can be downright confusing.

Would a separate way to distinguish that a threads poll has received a new vote be unfeasible?

Have the blip "half-highlighted" or something of the nature, and clicking on it will just take you to the poll itself maybe.

Would a separate way to distinguish that a threads poll has received a new vote be unfeasible?

That's what I'm asking yes, but for us even that wouldn't be really necessary.

Have the blip "half-highlighted" or something of the nature, and clicking on it will just take you to the poll itself maybe.

That would make it inconsistent I think. You would have to think about what you would do if both the poll and the post are in a unread state. Do you link to the poll or post? (The easy answer would of course be to link to the post though)

I think it would've been funny if I had made this a poll :tongue:

But how about when a poll is often voted in? There a times when there come new votes like every minute.

If it's new, it's new, regardless of whether it's a fast poll or a slow one.

This is one of those things where half of the people want it one way, and half want it the other. Even if this were a setting, it probably won't always be 'right' for every poll on every site.

If it's new, it's new, regardless of whether it's a fast poll or a slow one.

This is one of those things where half of the people want it one way, and half want it the other. Even if this were a setting, it probably won't always be 'right' for every poll on every site.

ok, well thanks for very basically saying a power setting by itself would not be enough(you are quite correct)....

So.... new option on polls? :rofl:

No, a new setting on polls wouldn't help either. What if I created a poll that I set this setting to flag new votes as making the topic appear as it's unread, but you don't want to see new votes making the poll appear unread? If this is going to work, it has to be something the end user viewing the poll decides. But I think that is needlessly complicated, considering polls are probably a pretty small percentage of the topics on most sites.

If it's new, it's new, regardless of whether it's a fast poll or a slow one.

Well, when you have polls that are voted in often it's mostly annoying to have it marked unread all the time. Posts and votes are two completely different types of content.

If this is done with votes, why doesn't likes added to posts update the unread-marker then? (NO IPS, do NOT get any ideas here..)

I would be happy with an indication about new poll votes (but I wouldn't really care about it). But it shouldn't share the unread-marker.

The least they could do is to give some sort of indication after members have clicked on it that the unread-thing was about a new vote. (But no, that's not the preferred solution for me, but would atleast be slightly better than it is currently)

No, a new setting on polls wouldn't help either. What if I created a poll that I set this setting to flag new votes as making the topic appear as it's unread, but you don't want to see new votes making the poll appear unread? If this is going to work, it has to be something the end user viewing the poll decides. But I think that is needlessly complicated, considering polls are probably a pretty small percentage of the topics on most sites.

User preference with acp-defined default then(Love your infallible logic by the way :smile: ).

It seems needlessly complicated, but it makes a large difference to the end-user, one of those niceties, one could argue the same of many inbuilt IPB features.

Well, when you have polls that are voted in often it's mostly annoying to have it marked unread all the time. Posts and votes are two completely different types of content.

If this is done with votes, why doesn't likes added to posts update the unread-marker then? (NO IPS, do NOT get any ideas here..)

I would be happy with an indication about new poll votes (but I wouldn't really care about it). But it shouldn't share the unread-marker.

The least they could do is to give some sort of indication after members have clicked on it that the unread-thing was about a new vote. (But no, that's not the preferred solution for me, but would atleast be slightly better than it is currently)

I don't know what to say. I guess I just find this to be a shockingly minor thing to get annoyed about, and not anything that needs to be changed.

I just would like to say that when things don't annoy you it is really easy to dismiss them. But when you are the admin of a community where a lot of members complain about something the story changes.

I just would like to say that when things don't annoy you it is really easy to dismiss them. But when you are the admin of a community where a lot of members complain about something the story changes.

This, and I don't want to give new members an confusing experience either. ;)

I don't know what to say. I guess I just find this to be a shockingly minor thing to get annoyed about, and not anything that needs to be changed.

So you're saying that minor annoyances should never be resolved? Since they are minor we should just learn to live with them... like forever? IPS should never change it just because it's a minor thing? Should I never provide feedback on minor things?

There has taken me some time to actually report this because I've tried to just "accept it" and before that I really thought about it being an "obvious bug" that would be fixed sooner or later myself. But enough is enough and I thought a suggestion about what you define as minor was about time now...

I just would like to say that when things don't annoy you it is really easy to dismiss them. But when you are the admin of a community where a lot of members complain about something the story changes.

Ding.

I, personally, have no issue with this stock behavior honestly, either way would be fine in my usage.

I have 5 different big board admin's, none of which have posted in this topic, all pulling their hair out over thousands of users complaining of this stock behavior.

As it is, rooting around to see if I can find a spot to cleanly hook in to fix, which is doubtful, as this is one query in the middle of a number of them.

Not hooking it means I curse them with manual upgrade maintenance.

I find this extremely annoying also. It is similar how vBulletin also functions and most of our users are pissed because of this.

Wonder why there is indentation in my code blocks? Read my little editor rant

Just want to emphasize that I still want this to be changed.

But since I see no other solution than to change the source code for now: admin/applications/forums/modules_public/extras/vote.php

//-----------------------------------------
// Go bump in the night?
//-----------------------------------------
 
if ($this->topic['allow_pollbump'])
{
# ... *snip* I have no need to change this
}
else
{
$this->topic['last_vote'] = time();
 
$this->DB->update( 'topics', array( 'last_vote' => $this->topic['last_vote'], 'last_post' => $this->topic['last_post'] ), 'tid=' . $this->topic['tid'] );
}

Looks to me like I would just need to change this query a bit, to not update last_post

$this->DB->update( 'topics', array( 'last_vote' => $this->topic['last_vote'] ), 'tid=' . $this->topic['tid'] );
 

This shouldn't cause any problems, right? Would that be all that would be needed to do?

Yuck changing source code :(

I agree its rather confusing, who needs to be updated when their was one frikin vote? Really?

Thats like somone mentioning to me an ant crawled on my lawn.

Yeah... My users are still not happy about this...

New vote != New post