Last modified: 2009-07-23 07:10:54 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T20976, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 18976 - Method to distribute the "jump text" from SPI to the various wikis
Method to distribute the "jump text" from SPI to the various wikis
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
SecurePoll (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Tim Starling
:
Depends on:
Blocks: 18991
  Show dependency treegraph
 
Reported: 2009-05-28 02:52 UTC by Robert Rohde
Modified: 2009-07-23 07:10 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Robert Rohde 2009-05-28 02:52:17 UTC
Currently one starts a SecurePoll session by visiting it at your local wiki.  This includes a message that we referred to as the "jump text" informing users that they would be going to an off-WMF site to vote.

Currently only developers can update the jump text at all the local wikis.  Vote admins can update the copy on the SPI wiki, but because the jump text appears locally on the user's original wiki this has no effect.  This had the result that translations made to the jump text after the start of the vote were mostly never seen by users.  We actually offended several translators who thought their work was being deliberately ignored.

There needs to be some practical process or mechanism by which changes made at SPI to the jump text can be propagated to all the other wikis.  Perhaps the wikis could query SPI for this text and cache it for 24 hours or something?
Comment 1 Tim Starling 2009-07-23 07:10:54 UTC
This is done as of r53668, as far as the method goes. It just needs a few lines of wrapper scripts and cron configuration to make it work for the coming Board election.

A cron job at SPI can generate a periodic dump of all messages (in XML format) and expose it on the web. Then a cron job at Wikimedia can download the dump and load it into all wikis. There isn't much that can go wrong, so it can be fully automated.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links