Last modified: 2013-04-22 16:14:10 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 T39303, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 37303 - Additional configurable campaign field
Additional configurable campaign field
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
UploadWizard (Other open bugs)
unspecified
All All
: Unprioritized enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: 37144
  Show dependency treegraph
 
Reported: 2012-06-02 14:34 UTC by elya
Modified: 2013-04-22 16:14 UTC (History)
4 users (show)

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


Attachments

Description elya 2012-06-02 14:34:35 UTC
Another one for Wiki Loves Monuments! 

In addition to the existing field "idField0" which - mainly - allows entering a unique monuments ID, several countries would need a second configurable field to add additional data, e.g. a geographic sublevel (district, state, municipality) because the respective countries do not have national unique identifiers. 

A perfect solution would be a dropdown/select that could be filled from a page in MW namespace, and had 2 $1 $2 values (option value, option text). 

Example:

Mediawiki:CampaignOptions 
1234|Limburg
4321|Brussels
87687|Moscow

This could be handled in the campaign configuration via {{foo|$1|$2}} or sth. similar. 

If a dropdown like described above is too complicated, a simple text field as we have with idField0 would be already a help.

Thx for considering this request. 

Elke
Comment 1 elya 2012-06-04 18:43:16 UTC
Addendum: the drop down request should work with the pre-filling by parameters (see https://bugzilla.wikimedia.org/show_bug.cgi?id=33341).
Comment 2 Mark Holmquist 2012-06-04 18:47:47 UTC
Hi, Elke! This is on my list of things to do, but my database is currently not set up for campaigns for some reason, and I can't find any guidance in the normal places. Jeroen is my next best hope for help, but there appears to be no response as yet. I'll let you know when I make progress.
Comment 3 elya 2012-06-04 18:59:13 UTC
Hi Mark, I talked with Jeroen this weekend about this bug, so I'm optimistic you'll find a solution :-)
Comment 4 Mark Holmquist 2012-06-04 23:37:15 UTC
Right, here you go: https://gerrit.wikimedia.org/r/10201

This is _a_ solution, it should be noted, but certainly not the best one. I'll be looking for a better way to do this in the very near future, but in case this is a pressing issue, this is your fix.
Comment 5 Mark Holmquist 2012-08-14 16:58:36 UTC
So, clearly I never came back to this, but again, it's at least one solution. I'd prefer to have some JavaScript that creates and deletes fieldsets for these fields, but for now, this will work.

Future: Make it less nasty and repetitive.
Comment 6 Erik Moeller 2012-08-24 02:27:20 UTC
This is now deployed, marking as fixed. The field should only be shown in the wizard when it's configured for a campaign.

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


Navigation
Links