At first I thought I was going crazy. Recently I have seen a SPORADIC pattern, where when voting on the original node and replies, only the reply votes get tallied on the first click of the vote button, returning a page with the original node still checked ( with a positive vote), but with the Reply votes properly showing their tally.

This requires me to hit the Vote button twice.

Just reporting this. Do you think it is caused by javascript, my browser, or is there a small bug in nodelet voting?

I'm not really a human, but I play one on earth.
Old Perl Programmer Haiku ................... flash japh

Replies are listed 'Best First'.
Re: node voting oddity
by Perlbotics (Archbishop) on Sep 23, 2010 at 21:22 UTC

    I observed something similar a few days ago - and unfortunately, just a few minutes ago. When voting on multiple nodes (root- and replies), the votes get tallied but all nodes that were not voted have their up-vote button checked after the updated page is presented. So hitting the submit button twice results in all nodes being up-voted ;-)

    It seems to be a server problem as the following code snippets try to illustrate:

    Before voting / freshly loaded page: 
    <div class="vote"><center>
<label><label><input type="radio" name="vote__86xxxx" value="1" />++</
+label></label> &nbsp; &nbsp; <label><label><input type="radio" name="
+vote__86xxxx" value="-1" />--</label></label>
</center></div>

    [download]
    After voting / reloaded page: 
    <div class="vote"><center>
<label><label><input type="radio" name="vote__86xxxx" value="1" checke
+d="checked" />++</label></label> &nbsp; &nbsp; 
<label><label><input type="radio" name="vote__86xxxx" value="-1" />--<
+/label></label>
</center></div>

    [download]
    Note the checked tag (I masked the real vote id xxxx, BTW). Expected behavior: no checked tag for nodes not voted and no input tags but a reputation header for those nodes voted.
    Yesterday and (I think) the day before, it seemed to be fixed. Using: Opera 10.62 / Linux

[reply]
[d/l]
[select]

      Enable "null vote" in User Settings.

      A group of radio buttons with none selected is a violation of some standard but it is still allowed by modern browsers. CGI.pm got updated and decided to enforce this standard on its own. I thought I had patched CGI.pm back to be backward compatible on this point but I guess I missed one of the web servers. I'll fix it shortly and then the problem will eventually go away as Apache children get recycled (I've lost the ability to restart Apache).

      - tye        

[reply]
        I'll fix it shortly and then the problem will eventually go away...

        I'm still observing the issue (i.e. all '++' buttons preselected after having voted (when having "null vote" disabled)).  So, as nearly 3 months have passed by now, I wonder if it has reverted again?

        P.S.: if it's that CGI.pm is enforcing some (silly, IMHO) standard, how come the inital renderering of the buttons before having voted is not affected by the problem. Isn't CGI.pm being used in this case as well?

[reply]

Back to Perl Monks Discussion