Sign Up Sign In

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Voting while not signed in


(Persistent irrelevant comment: I jumped down to the title field and entered that first and then went back up here to enter the actual question.)

I tried to vote on an answer and nothing happened. No change to the count, no visible error message.

After several clicks, I realized that I might not be logged in. I clicked "Sign in" and logged in as normal and then voting worked as expected.

Unlike some other action buttons (e.g., Delete if you don't have Delete privileges), I think the voting buttons should always be visible - they are a key feature of the system and no special privileges are (and none should be) required to vote. However, if you are not signed in then one of the following should happen if you click a voting button:

  • On-screen notification that you must register/sign in to vote.
  • A dialog box giving the option to either Sign In or Sign Up.

@ArtOfCode No errors from the actual vote-clicks. But on each page load, in addition to 404 on meta.css and meta.js (which I get whether signed in or not), I see:

Uncaught TypeError: Cannot read property 'split' of undefined
    at HTMLDocument.<anonymous> (application-b9346985…56530b11235aa8.js:7)
    at i (jquery-2.2.2.min.js:2)
    at Object.fireWith [as resolveWith] (jquery-2.2.2.min.js:2)
    at Function.ready (jquery-2.2.2.min.js:2)
    at HTMLDocument.J (jquery-2.2.2.min.js:2)
(anonymous)	@	application-b9346985…56530b11235aa8.js:7
i	@	jquery-2.2.2.min.js:2
fireWith	@	jquery-2.2.2.min.js:2
ready	@	jquery-2.2.2.min.js:2
J	@	jquery-2.2.2.min.js:2````
Why should this post be closed?


It should also be noted that if I visit a page while not signed in, then sign in in another tab, then return to the previous tab; I cannot upvote there until I refresh the page. Not sure if that's correct or not. ‭mbomb007‭ about 2 months ago

Actually, that behavior is generally correct. The first page doesn't have the token (terms may vary - session variable, etc.) needed. When you refresh the page, it gets that and then voting, etc. work. It is a side-effect of making things work via AJAX rather than full page reloads for every click. ‭manassehkatz‭ about 2 months ago

Weird; there should already be a warning message for this case. Not sure why it's not firing. Any errors in your browser console? ‭‮edoCfOtrA‭ about 2 months ago

Our use cases/wireframes call for a pop-up that invites you to sign in; I guess we haven't gotten there yet with the code. (This should apply to any control that's visible but requires that you be signed in.) ‭Monica Cellio‭ about 2 months ago

This seems to be working now (403 error popup) in both Chrome & Firefox. Did somebody fix something and not note it here? Or is the system acting inconsistently? ‭manassehkatz‭ about 2 months ago

Show 2 more comments

0 answers

Sign up to answer this question »