Last modified: 2010-04-09 09:07:43 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 T25088, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 23088 - Need for a gadgets-preference versus skin-preference compatibility table
Need for a gadgets-preference versus skin-preference compatibility table
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
User preferences (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-04-08 04:56 UTC by folengo
Modified: 2010-04-09 09:07 UTC (History)
3 users (show)

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


Attachments

Description folengo 2010-04-08 04:56:28 UTC
Hello,

Right now I am testing the "Classic" skin on Wikimedia Commons, which has some interesting features like the display of categories at the top of the page rather than at the bottom, which is good for picture categorizing jobs.

However, I discovered that some of the gadgets I previously used (like the "tineye" tab, the "catscan" tab) are no longer available, although they are kept selected in my user preferences.

I perfectly understand that it is not possible (at least for the time being) to have all gadgets available for all skins. But the availability of gadgets for a given skin (or the other way round: the availability of a skin while keeping the possibility of using a given gadget) should be predictable when the user selects his preferences.

For that purpose, a compatibility table showing skins in rows and gadgets in columns (or the other way round) should be provided so that the user knows what to expect before changing his preference settings.

The status for the compatibility between a skin and a gadget could have three values :

* perfectly compatible (the gadget developer said he tested that compatibility)
* not compatible (the gadget developer said he tested and found out it is not compatible)
* you may try at your own risk (we don't have information on that compatibility issue)

Another possibility would be to have a popup warning saying "you can't change that skin unless you remove that gadget preference" or "you can't add that gadget unless you switch to another skin", or "we are not sure if your skin change will keep your gadgets alive", or "we are not sure if that gadget your are choosing now is compatible with the skin you are using".
Comment 1 Bawolff (Brian Wolff) 2010-04-08 21:48:25 UTC
>However, I discovered that some of the gadgets I previously used (like the
>"tineye" tab, the "catscan" tab) are no longer available, although they are
>kept selected in my user preferences.

I'd imagine a significant portion of incompatible gadgets would work if addPortletLink was modified to be compatible with the older skins. (have no idea if thats worth the effort)

As for a compatibility chart, as it stands there is no way for the software to know which gadget is compatible with what, so such a chart would probably have to be made at your local wiki, as every wiki has different gadgets.
Comment 2 Platonides 2010-04-08 22:11:07 UTC
It's global_append_tab what is not working. See http://commons.wikimedia.org/wiki/MediaWiki:Extra-tabs.js

I have improved it to work with quickbar, so it now works for all skins but  nostalgia (and I'm not sure where should they be added there or even if they should).

Closing as FIXED.
Comment 3 folengo 2010-04-09 09:07:43 UTC
Thanks Platonides for the fix (it works fine now).

To Bawolff : I was wondering if the layout of the preference page was not hard coded within mediawiki, and if something like an empty table had not be coded in Mediawiki, before asking every local gadget developer to fill it. If everything can be changed on the local wiki, I will try to make my suggestions there, then.

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


Navigation
Links