On Thu, 07 Aug 2014 18:02:58 +0200, James HK jamesin.hongkong.1@gmail.com wrote:
Hi,
I just went on to `git pull --rebase origin master` on getting MW 1.24 master and suddenly I see a "Whoops! The default skin for your wiki ($wgDefaultSkin), vector, is not available."
I have to say that I'm not really interested in modifying the LocalSettings.php just to get a MW working as it used to be.
I do expect when downloading MW it is at least functional and not comes with a message of "Whoops!" your missing something.
On Thu, 07 Aug 2014 21:12:13 +0200, James HK jamesin.hongkong.1@gmail.com wrote:
Honestly, I don't care about skins, when I download MW I'd expect it to work and not to figure out that I need another two, three or four steps just to have decent user experience.
I want my LocalSettings from MW 1.23 to work with MW 1.24 (we are not talking about an ancient release such as 1.16) without having to study an extra page on mw.org about skins.
If you want a stable experience, it is unwise to use the git master to run your wiki. I recommend using the tarballs or checking out release branches.
Straight git master checkout *is* functional; it includes the minimal skin that you're seeing that also displays a (hopefully useful) information screen. If you have concrete suggestions on how to improve that message, I'd love to hear them.
I am sad to have introduced a breaking change, but these are sometimes necessary. I tried to make the transition as painless as possible. Again, I'd love to hear concrete improvement suggestions.
The other funny thing, is the message which says: "You can paste the following lines into LocalSettings.php to enable all currently installed skins:" ( empty )
So I should paste an empty message to `LocalSettings.php`, what the hell!!
That's interesting. Can you share any details about your personal setup, so that I can try to debug this? I have tested this and my MediaWiki installation correctly produces a message that you have no skins installed.