[#271] Mediawiki User theme preferences breakage



Detailed description

If user change the theme in mediawiki, then user loses the fusionforge header (tabs and so on)... Only custom fusionforge theme which is the default works.... partially as it breaks the funky theme.

General Information
Submitted by:
Franck Villaume
Date Submitted: 2011-01-27 14:00
Last Modified by:
Franck Villaume
Last Modified: 2018-01-24 19:29
Date Closed: 2018-01-24 19:29
Permalink: https://fusionforge.org/tracker/a_follow.php/271
Votes: 0/1 (0%)
Internal Fields
Data Type: Bugs
Assigned to: Franck Villaume (nerville)
State: Closed
Priority: 3
Extra Fields
Target Release:
Found in Version:
Follow-up tabs
Message  ↓
Date: 2018-01-24 19:29
Sender: Franck Villaume

Option 1 is implemented: user cannot change the mw skin. Only one skin is supported, the other are skipped by configuration.

fix in commit: 29c7812d37c7eed86a43611d251b8f529be18f6b

Date: 2011-01-28 09:45
Sender: Franck Villaume

2 options : 1) disabling changing mediawiki theme. Then you need a very lightweight non intrusive mediawiki theme. Currently, default custom fusionforge mediawiki theme breaks the funky theme.... 2) disabling changing mediawiki theme from the mediawiki user preferences page and use the mediawiki API to sync changing theme from fusionforge user preferences page. We need to add a specific funky theme for mediawiki. And if the choosed theme is missing on mediawiki part, we need to fall back to a lightweight non intrusive mediawiki theme.

Plan could be : implement option 1 and if we have time, implement option 2.

Date: 2011-01-28 08:41
Sender: Thorsten Glaser

That much was obvious. What do you suggest?

In Evolvis, we say we don’t support changing theme (and our cow-orkers want Monobook anyway, on which it’s based).

So, what about we disallow changing the MediaWiki theme? I think I coudld hack that.

Contra: if we ever have more than one “forge theme” we’d need to think about it again. But that’s not now.

Other solution is to “just” (hah!) tell users to not do it………

No attached documents

No related commits.

Field Old Value Date By
status_idOpen2018-01-24 19:29
Franck Villaume
close_dateNone2018-01-24 19:29
Franck Villaume
assigned_tonone2018-01-24 19:29
Franck Villaume
Target ReleaseNone2018-01-24 19:29
Franck Villaume
Found in Version5.3.12018-01-24 19:29
Franck Villaume
ResolutionAccepted As Bug2018-01-24 19:29
Franck Villaume
Found in Version5.12014-06-06 14:08
Sylvain Beucler
Target Release5.1.x2013-04-27 13:17
Franck Villaume
SeverityNone2011-03-18 14:18
Franck Villaume
ResolutionNone2011-03-18 14:18
Franck Villaume
Target ReleaseNone2011-03-18 14:04
Franck Villaume

No relations found.