Skin talk:Chameleon

Jump to navigation Jump to search

About this board

DDSnowl (talkcontribs)

Hi F.trott,

I'm using FIrefox 68.0.1, Mediawiki 1.31 and chameleon installed by composer. When I want to print content, only the first page is shown (printed). It doesn't make a difference, which driver I use, problems exists with normal printers, pdf Architect, Fax, aso. What is to be done? --~~~~

F.trott (talkcontribs)

Is this only on Firefox or also on other browsers?

Emwiemaikel (talkcontribs)

Stephan, I also face this problem. with MW1.13, Firefox and Chameleon 2.1. In Chameleon 1.7 it did work. And your suspicion is correct. It only fails in FF and works well in Chrome. I created a Github issue for this:

Reply to "Only first page is printed"

Editing with a form does not work for previews and diffs

Kghbln (talkcontribs)

This is an Chameleon 1.7 and Page Forms 4.5 issue. I am not sure if it was there before with earlier versions of Page Forms.

When you edit a page with a form and click "Show preview" or "Show changes" then a preview or a diff of the page is indeed shown. However the buttons "Save changes" "Show preview" etc. including the summary line are no longer shown which is preventing you from saving the page. Basically everything added with the "standard input" tags provided by the Page Forms extension is not showing.

I am not sure if this is a Chameleon or Page Forms issue. I suspect the latter but want to make sure.

This can be recreated on smw.o.

F.trott (talkcontribs)

I did a quick check on a local wiki and it seems to work on Chameleon 1.7.1 and PF 4.3.

For me, when I click Show Preview e.g. on the complete form is gone. Curious.

There is two things I could think of that might cause this.

  1. Chameleon is built to enforce valid HTML. This includes changing HTML element IDs, if necessary. For the preview this means that for example the content of the preview gets the ID bodyContent-g2wfpz001g instead of just bodyContent. I would not be surprised if that throws PageForms off.
  2. It could be that PageForms now uses a hook that Vector calls and Chameleon does not.

In any case it would probably make sense to involve Yaron.

Kghbln (talkcontribs)

> For me, when I click Show Preview the complete form is gone. Curious.

Apparently this is what happens on smw.o too. Thus we are talking about the same issue I believe. Yeah, probably @Yaron Koren: can be of help here.

Yaron Koren (talkcontribs)

I don't think Page Forms has any Vector-specific code... beyond that, I have no idea; sorry.

Kghbln (talkcontribs)

Thanks a lot for looking at it, even without conclusion. What I had hoped for was that the "Some parts of the edit form did not reach the server; double-check that your edits are intact and try again." error note, which is actually also shown for Vector, could provide a decisive hint.

Pastakhov (talkcontribs)
Stefahn (talkcontribs)

I had the same problem: Preview was not shown when clicking on "Preview" in a form (MW 1.31.3, PF 4.6 (dae51e2)).

I applied the patch manually and the preview now works again (Thanks Pastakhov!).

Can someone please merge the patch into master?

Yaron Koren (talkcontribs)

@Stefahn - thanks for letting me know about this; I'm not sure if I saw the patch before. I merged it in yesterday.

Reply to "Editing with a form does not work for previews and diffs"

MW1.31 > 1.34 Upgrade: Chameleon Skin Broken :(

3 (talkcontribs)

Everything went smoothly with my upgrade, except for Chameleon skin. I followed some advice from this forum and upgraded Composer and Chameleon-skin, but I still get the error below at the top of every wiki page. Content loads below the error, without the customised Chameleon skin.

"Deprecated: Use of ExtensionRegistry::load was deprecated in MediaWiki 1.34. [Called from ExtensionRegistryHelper\ExtensionRegistryHelper::loadModuleRecursive in /var/www/html/w/vendor/mediawiki/mw-extension-registry-helper/src/ExtensionRegistryHelper.php at line 79] in/var/www/html/w/includes/debug/MWDebug.phpon line333"

F.trott (talkcontribs)

Thanks for the report. For the moment it should be enough to turn off PHP error reporting in LocalSettings.php (which is a good idea on production systems anyway):

error_reporting( 0 ); ini_set( 'display_errors', 'Off' );

F.trott (talkcontribs)

This should be fixed. This was actually an issue in a dependency, so please update with composer update "mediawiki/chameleon-skin" --with-dependencies

Reply to "MW1.31 > 1.34 Upgrade: Chameleon Skin Broken :("

Initial SCSS compiling time very slow

SbstnS (talkcontribs)


I'm currently working with Chameleon 2.1.0 and MW 1.31.2 on an Ubuntu 18.04 box. I noticed that compiling the SCSS files takes up to 1.3 minutes after touching the LocalSettings.php and cleaning the browser cache. After the first time compiling, the page load time is normal (1-4 seconds).

I did not get any errors in web server log,php or JS.

Is a compile-time > 1 minute normal?

F.trott (talkcontribs)

>1min is a lot, but still within expectations on a slow machine. The SCSS compiler is a pure PHP implementation and not too fast. After the first compilation the resulting styles are cached and are available faster.

Reply to "Initial SCSS compiling time very slow"
LCavalini (talkcontribs)


I've installed Chameleon skin on an Apache server and it works fine, but I'm facing problems with this skin on a Nginx server. When I try to access any page, the browser can't load CSS and says zzz.ext.bootstrap "was blocked due to mime type ( text/html ) mismatch ( x-content-type-options nosniff )". I had no problem with other skins and extensions. Everything works perfectly, except for Chameleon skin.

F.trott (talkcontribs)

I don't have any experience with nginx at all. What you could try to do is to disable x-content-type-options nosniff in nginx.conf and see, what the server is actually sending. It could be that it does not send CSS, but some HTML formatted error message,

LCavalini (talkcontribs)

Thank you for your reply! I've tried to disable "x-content-type-options nosniff" and tested many settings, but it didn't work. If I find a solution, I'll post here.

Reply to "Nginx zzz.ext.bootstrap"

Broken with MW 1.33.0 upgrade

Summary by F.trott

After upgrading MW with Softaculous, Composer and maintenance/update.php have to be run.

Grlucas (talkcontribs)

Hello, all. After upgrading to MediaWiki 1.33.0, I get the following error trying to load my site.

Fatal error: Uncaught UnexpectedValueException: callback 'Skins\Chameleon\Chameleon::init' is not callable in /home/grlumjcd/public_html/includes/registration/ExtensionRegistry.php:405 Stack trace: #0 /home/grlumjcd/public_html/includes/registration/ExtensionRegistry.php(173): ExtensionRegistry->exportExtractedData(Array) #1 /home/grlumjcd/public_html/includes/Setup.php(127): ExtensionRegistry->loadFromQueue() #2 /home/grlumjcd/public_html/includes/WebStart.php(77): require_once('/home/grlumjcd/...') #3 /home/grlumjcd/public_html/index.php(39): require('/home/grlumjcd/...') #4 {main} thrown in /home/grlumjcd/public_html/includes/registration/ExtensionRegistry.php on line 405

I tried to upgrade the skin (composer update "mediawiki/chameleon-skin") but I get a series of errors there, too:

> ComposerHookHandler::onPreUpdate

Loading composer repositories with package information

Updating dependencies (including require-dev)

Your requirements could not be resolved to an installable set of packages.

  Problem 1

   - The requested package oojs/oojs-ui (locked at v0.29.2, required as 0.31.3) is satisfiable by oojs/oojs-ui[v0.29.2] but these conflict with your requirements or minimum-stability.

  Problem 2

   - The requested package pear/net_smtp (locked at 1.8.0, required as 1.8.1) is satisfiable by pear/net_smtp[1.8.0] but these conflict with your requirements or minimum-stability.

  Problem 3

   - The requested package wikimedia/ip-set (locked at 1.3.0, required as 2.0.1) is satisfiable by wikimedia/ip-set[1.3.0] but these conflict with your requirements or minimum-stability.

  Problem 4

   - The requested package wikimedia/php-session-serializer (locked at v1.0.6, required as 1.0.7) is satisfiable by wikimedia/php-session-serializer[v1.0.6] but these conflict with your requirements or minimum-stability.

  Problem 5

   - The requested package wikimedia/scoped-callback (locked at v2.0.0, required as 3.0.0) is satisfiable by wikimedia/scoped-callback[v2.0.0] but these conflict with your requirements or minimum-stability.

  Problem 6

   - The requested package wikimedia/xmp-reader (locked at 0.6.0, required as 0.6.2) is satisfiable by wikimedia/xmp-reader[0.6.0] but these conflict with your requirements or minimum-stability.

  Problem 7

   - The requested package mediawiki/mediawiki-codesniffer (locked at v22.0.0, required as 25.0.0) is satisfiable by mediawiki/mediawiki-codesniffer[v22.0.0] but these conflict with your requirements or minimum-stability.

  Problem 8

   - The requested package nikic/php-parser (locked at v3.1.3, required as 3.1.5) is satisfiable by nikic/php-parser[v3.1.3] but these conflict with your requirements or minimum-stability.

  Problem 9

   - The requested package psy/psysh (locked at v0.9.6, required as 0.9.9) is satisfiable by psy/psysh[v0.9.6] but these conflict with your requirements or minimum-stability.

  Problem 10

   - The requested package jetbrains/phpstorm-stubs (locked at dev-master) is satisfiable by jetbrains/phpstorm-stubs[dev-master] but these conflict with your requirements or minimum-stability.

  Problem 11

   - don't install symfony/polyfill-mbstring v1.11.0|remove mediawiki/core No version set (parsed as 1.0.0)

   - don't install symfony/polyfill-mbstring v1.11.0|remove mediawiki/core No version set (parsed as 1.0.0)

   - Installation request for mediawiki/core No version set (parsed as 1.0.0) -> satisfiable by mediawiki/core[No version set (parsed as 1.0.0)].

   - Installation request for symfony/polyfill-mbstring (locked at v1.11.0) -> satisfiable by symfony/polyfill-mbstring[v1.11.0].

Any help would be appreciated.

F.trott (talkcontribs)

How did you upgrade MW?

Grlucas (talkcontribs)

I used Softaculous through my web host, and it hasn't been a problem so far.

F.trott (talkcontribs)

I don't know how that works, but it seems that it has left your composer files (or your whole MW installation) in an inconsistent state. From the error messages you can see that MW 1.33 requires higher versions than are installed, e.g. oojs/oojs-ui (installed: v0.29.2, required: 0.31.3). It could just be a bookkeeping issue. It could also be that Softaculous just downloads the new MW version, but does not update the packages it depends on.

My advice would be to

  • make a backup
  • run composer update from the MW install directory (this should update all packages MW depends on, incl. Chameleon)
  • run php maintenance/update.php from the MW install directory (this should update the database to make sure it is compatible with your new MW version)
Grlucas (talkcontribs)

Thanks for the suggestions. I've not had the opportunity to try this yet, but I will report back.

Grlucas (talkcontribs)

@F.trott: OK, I followed your steps, then updated. Still the same errors. Then I tried to update composer, then Chameleon, and it worked. I'm thinking it would have worked the last time, too. I'll have to remember to include composer in any of my upgrades from now on. Thanks!

Trying to add larger breakpoint but to no avail

2601:646:100:43B3:B8D0:6D74:83CB:36D3 (talkcontribs)

I have appended the scss, the grid-breakpoint variable, and the container max-width variables. Still not seeing any changes though. I am not caching anything and I have tested in multiple browsers. What am I missing?

F.trott (talkcontribs)

Changing Variables Led to No Change

Finncrux (talkcontribs)


I'm using MediaWiki1.32,and installed the Chameleon skin with composer successfully. The skin looks awsome, but when I tried to add

$egChameleonExternalStyleVariables= [

'cmln-navbar-toggler-color' => 'dark',


to my LocalSettings.php, no change was applied to my page. I tried clearing the cache, restarting the serve and adding some other variables I found form the var lists on github, and non of them seem to work.

Could you please tell me what I should do to change the color of the navi bar? thank you! (talkcontribs)


2601:646:100:43B3:B8D0:6D74:83CB:36D3 (talkcontribs)

@Finncrux what solved it for you if you don't mind me asking?

Finncrux (talkcontribs)

if you want to change the color of navi bar, just add

$egChameleonExternalStyleVariables= [

'cmln-navbar-bg-color' => 'dark',


or change 'dark' to whatever color that's already defined. If you want to use custom color, or change the navibar icon and text color, you will need to make a lot of change with the style file.

Changing Personal-tool icon color

2 (talkcontribs)

Hi: How can I change the color of personal-tool and page-tool icons in the Navbar section? I have tried to add

'cmln-personal-tools-link' => '#1b599b none #10345a underline', to the egChameleonExternalStyleVariables array, but nothing happened.

Thank You!

Finncrux (talkcontribs)


Not compatible with MediaWiki 1.33.0?

4 (talkcontribs)

With MediaWiki 1.33.0, wfLoadSkin('chameleon') causes the following error:

... mediawiki-1.33.0/includes/resourceloader/ResourceLoader.php: ResourceLoader module info type error for module '0.mediawiki.skinning.content': expected ResourceLoaderModule or array ...

It traces back to Chameleon trying to load resources. It doesn't seem normal. Anything I can do?

F.trott (talkcontribs)
2607:F470:14:A:C94A:FD64:F06D:CA34 (talkcontribs)

I had the same issue. A fix was just pushed to the master branch. You'll need to change your version in your composer.json to "dev-master" instead of "~2.0" or whatever version you're using. Then run composer update

F.trott (talkcontribs)

A new version is now available, so a simple composer update should be enough.