Licensing update/Bugs
 | This page is kept for historical interest. Any policies mentioned may be obsolete. If you want to revive the topic, you can use the talk page or start a discussion on the community forum. |
Licensing update
Known Bugs
[edit]- "Internal Error": A small number of accounts are encountering a persistent "internal error" when they attempt to vote. This is being investigated.
- Multiple votes can be cast by the same user from different projects if the user has satisfied the voting requirement in each project. Please do NOT test this bug out. Such duplicate votes are being removed by hand.
- The site notice links accessed from secure.wikimedia.org are broken. One can access the vote page directly by visiting Special:SecurePoll/vote/1 from within any wiki in the secure.wikimedia system (provided you are qualified to vote there), but to get to this page you will need to type its url directly.
- Edits made before February 2002 are not counted by the software when determining if an account has the 25 edits needed for voting. These edits should be included towards eligiblity. If the software tells you that you are ineligible as a result of its not counting these old edits, please inform us at this section.
- In some projects, jump-text page sometimes show English instead of user's language settings.
Fixed Bugs
[edit]- CentralNotice sometimes contain empty rotation (meaning it does not display Wikimania nor licensing update announcement)
- Vote page has unnecessary "login" button at upper right.
- Login subpage fails to properly create a session and set a cookie. It does create a session from the error page though.
- Vote wiki currently has incomplete page orientation support for right-to-left languages (e.g. Hebrew and Arabic)
- Adding &rtl=1 to the url will reorient the page, but the orientation is not applied by default.
- Hiding the previous CentralNotice announcements (scholarship for Wikimania) will cause the browser to not display the licensing update announcement until 7 days after the previous announcement was hidden.
- This wasn't "fixed" at a technical level but the move to showing only one unified notice at a time removed the potential for further conflict.