Xenharmonic Wiki talk:Bugs

This page is to report Wiki bugs. It is also for "To Do" items that are not about the content of the Wiki, but rather its administration. Please add to this page as you see bugs.

This page is only for discussion of bugs related to MediaWiki or the migration from Wikispaces. For more general discussion of how to improve the wiki, please go to Wikifuture instead.

NEEDS CHANGING

Below this section are all the bugs that currently require us to do something. When bugs are finished, they will be removed from here and added to Talk:FinishedBugs.

Scala file pages

Pages that are scala files need to be wrapped in code blocks and have extra line breaks removed. (EDIT: yes, I will be doing this automatically -- stay "tuned" :) )Mike Battaglia (talk) 17:27, 18 September 2018 (UTC)

There are a whole lot of these pages! Is there a way to do this (semi-)automatically? Or at least to generate a list of, say, all pages that contain ".scl"? To complicate matters further, some pages contain multiple .scl files (and no other content). Another option (not sure if better or worse) would be to transfer these .scl-only pages to actual files. Thoughts? I'm happy to help, just not sure of the best way to proceed... Spt3125 (talk) 03:19, 19 September 2018 (UTC)

Yes, I'll be doing this automatically, it's on my list -- no way we're doing this by hand and this is a simple regex job. Edited above to make clearer... -- Mike Battaglia (talk)

These pages have use in people clicking Random page and seeing random interesting tunings. PiotrGrochowski (talk) 04:22, 19 September 2018 (UTC)

It may be worth looking into excluding the Scala files from Random page results, maybe using something like Extension:ExcludeRandom. --Tyler (talk) 13:03, 19 September 2018 (UTC)

But whyyyy? The fanmade tunings only make Special:Random even better, inspiring people to use the tunings! PiotrGrochowski (talk) 13:05, 19 September 2018 (UTC)

Heh, if you like having the Scala files in random pages, might as well keep them. But, just thinking, maybe we could create a "Random tuning" link right below it... :) Mike Battaglia (talk) 13:48, 19 September 2018 (UTC)

How could we have split random page generators in MediaWiki? PiotrGrochowski (talk) 16:27, 19 September 2018 (UTC)

We could put them in a category like "Scala files", as User:Spt3125 suggests, and then there are MediaWiki extensions like this that let you get a random page from a category. Mike Battaglia (talk) 06:23, 20 September 2018 (UTC)

Sorry, I misread your comment and thought it was a complaint. Ignore me. Tyler (talk) 13:51, 19 September 2018 (UTC)

Excellent, thanks Mike! If that regex job can include adding a category such as "Scala files" or "scl" to those pages, that would be very useful i think. Some pages already have these ("tags" from Wikispaces), but many do not. Spt3125 (talk) 00:44, 20 September 2018 (UTC)

Random thought: what about moving them to, say, scl.xen.wiki? Not sure if this would be good or bad...? Spt3125 (talk) 00:44, 20 September 2018 (UTC)

Making a whole new wiki would be a lot of infrastructure work - would be much easier to just make a category for them, as you mention. Shouldn't be too difficult with regex, just a lot of other stuff to get finished first... Mike Battaglia (talk) 06:23, 20 September 2018 (UTC)

If we want to go this route, maybe it makes more sense to remove them as pages, and upload them as files? Essentially these .scl things are config files for Scala, not wiki pages. There could be a wiki page which contains a directory of uploaded .scl files including descriptions, related pages, etc. Someone can always make a wiki page about a scale which links to an .scl file, if they want to. Tyler (talk) 12:51, 20 September 2018 (UTC)

Whatever we do, I think the main use case should be on making it easy for people to create and add new Scala files the "right way" (whatever we decide that is), in the future. Mike Battaglia (talk) 16:17, 20 September 2018 (UTC)

Organized thought: how about handling of .scl in a way similar to .svg, and have a way of rendering it in-browser as a text list (and maybe even eventually audio clips)? This is also a vote against having .scl-only pages, and instead converting those to files. Xenjacob (talk) 21:06, 21 September 2018 (UTC)

We could do both of those. Automating audio will be more difficult, but possible -- I wrote a JavaScript MIDI library once upon a time I could dust off for this. We could also use the "subpage" feature and put them all at pages like scala/something.scl. Then we could create templates for the rest: so at the top of the page we put something like {{scala-start}} and at the end we put {{scala-end}}, and then create those templates to have whatever markup we like. Mike Battaglia (talk) 22:17, 21 September 2018 (UTC)

---

Move Spanish pages to es.xen.wiki

Páginas_en_español - i rounded up all the es pages i could find (not many) and linked them all here. Perhaps these could be moved to es.xen.wiki? Spt3125 (talk) 01:30, 20 September 2018 (UTC)

Also: 日本語のページ_(pages_in_Japanese) Spt3125 (talk) 01:59, 20 September 2018 (UTC)

Yes, we mentioned this on the Facebook forums here. Basically, the Spanish pages should be spun off and merged into es.xen.wiki. It would also be good to move the "Purdal" pages from purdal.xen.wiki into es.xen.wiki. The Japanese pages should also be spun off into jp.xen.wiki. But we will need someone who speaks these languages to lead the process; I know no Japanese at all and only know basic Spanish. If you would like to help with this, we would be very grateful! Mike Battaglia (talk) 06:30, 20 September 2018 (UTC)

I'm happy to help, but would need some guidance on the best way to proceed (not sure how to move a page, etc.) I can read Japanese just enough to do something basic like this; Spanish a bit better, but i'm far from fluent in either... Spt3125 (talk) 02:12, 21 September 2018 (UTC)

I will be happy to help here, Japanese as well as Spanish. (Don't know so much of both, but sure enough to create/edit/move pages, already done that in the old xenwiki.) (hstraub)(talk)

User:hstraub, User:Spt3125 -- can you compile a list of pages that need to be moved to es? Then I can mass export them all at once and re-import them there. Also, should we talk about this here, or on FB? Mike Battaglia (talk) 16:23, 23 September 2018 (UTC)

Mike, the page Páginas_en_español is that list (unless i've missed any pages, which is certainly possible). Happy to discuss on FB if you prefer. Spt3125 (talk) 21:40, 23 September 2018 (UTC)

Link system for other languages

On mobile devices, there is a "Language" icon on each page - apparently like in Wikipedia. Clicking it currently results only in a message that this page isn't available in other languages - even if content would exist, in German, Spanish or Japanese. It would sure make sense to bring this button to work! And also the analogous functionality on a desktop PC where wikipedia shows for each page the available other-language versions of it in the the side bar. (hstraub) (talk)

Agreed - this is only like this because some of the other languages are actually in this wiki (Japanese and half of Spanish), so they're going to have to be split off first. But if you change the links from, for example, [[:de:Wilkommen]] to [[de:Wilkommen]], they will become language links and appear in the sidebar. (And also disappear as normal links) Mike Battaglia (talk) 11:18, 22 September 2018 (UTC)

That works indeed, thanks! I can start editing at once with German, then. And for Spanish as soon as the Spanish pages are moved to the Xenharmonico wiki. And then it will make much sense to create a separate Japanese xenwiki and move all the Japanese pages there, so this link system will work there, too. The Japanese pages, BTW, are all (or at least mostly) tagged with „jp“ so a list can be compiled easily. hstraub

You are not supposed to craft the signature yourself. ~~~~ automatically gives the name, talk and time. ~~~ gives the name and talk only, while ~~~~~ only gives the time. PiotrGrochowski (talk) 18:33, 24 September 2018 (UTC)

Re-add organizers

Organizers need to be put back from the old Wiki. We're working on this now as people sign up, but wanted to make a note of it. Mike Battaglia (talk) 06:51, 20 September 2018 (UTC)

"IMPORTDEBUG" category - changing external images

MediaWiki doesn't quite support external images in the same way that Wikispaces did. There are a few pages with external image links that need to be changed. More on the situation here: Category:IMPORTDEBUG - Change External Images - 07:23, 20 September 2018 (UTC)

Calculators/JavaScript is broken

Pages like Just Intonation -- EDO calculator render catastrophically incorrectly. PiotrGrochowski (talk) 15:56, 17 September 2018 (UTC)

Hi PetrPiotr - yes, unfortunately MediaWiki doesn't support JavaScript. There are three or four "calculator" pages that have broken as a result. We may be able to add some of this back in using Templates, but for now, this is unfortunately one of the (few) things that Wikispaces was able to do that MediaWiki doesn't support. Mike Battaglia (talk) 16:31, 17 September 2018 (UTC)

Why did you misspell my name, ... MiekMike? PiotrGrochowski (talk)

Oops - was talking to someone named "Petr" on Facebook at the same time, and I got my Petr's and my Piotr's mixed up... :) Mike Battaglia (talk) 16:51, 17 September 2018 (UTC)

The talk page has a link for a webpage that almost works, but fails when numbers are entered. PiotrGrochowski (talk) 18:41, 18 September 2018 (UTC)

If someone wants to create a version of this that works as a standalone page, maybe we can host it and then link to it from the wiki. Tyler (talk) 13:34, 20 September 2018 (UTC)

@Piotr - Yeah, this is because there's no JavaScript, since MediaWiki is HTML only. I think this "Widgets" plugin is what we will need. I'm not sure if Templates will also work, but maybe. Mike Battaglia (talk) 16:00, 20 September 2018 (UTC)

Did you see that webpage in Talk:Just Intonation -- EDO calculator with the "almost working" behavior? That's a copy of the HTML code given. PiotrGrochowski (talk) 16:06, 20 September 2018 (UTC)

Page backups are done, https://web.archive.org/web/20180920184047/http://xenharmonic.wikispaces.com/Interval%20calculator?responseToken=05777b0c767eb7f0d7338c241de5ac1ff , https://web.archive.org/web/20180920184435/http://xenharmonic.wikispaces.com/Just%20Intonation%20->%20EDO%20calculator?responseToken=09b43236460272dc924467493160c31d5

any more?

Yes, these: https://en.xen.wiki/w/Wolfram_Alpha_Regular_Temperament_Widgets Mike Battaglia (talk) 16:07, 23 September 2018 (UTC)

Wolfram Alpha Regular Temperament Widgets now has a link to another page backup. PiotrGrochowski (talk) 16:10, 23 September 2018 (UTC)

Imagine what would happen if FREEZE rendered the Acid3 test. Have you tested this? How about the Acid1 test or the Acid2 test? PiotrGrochowski (talk) 06:42, 21 September 2018 (UTC)

The thing you are calling "FREEZE" was just from before we imported - now it's only the MediaWiki engine. We may be able to do some JavaScript things -- on the list of things to do Mike Battaglia (talk) 16:08, 23 September 2018 (UTC)

Complete the translation of purdal:

The translation of purdal: to Spanish looks very incomplete. PiotrGrochowski (talk) 08:07, 23 September 2018 (UTC)

MinervaNeue Mobile Skin Sidebar

Minerva Neue is the Mobile Skin, but it has a few bugs - no recent changes in the sidebar, no way to change a Page's protected status (I think?), etc. Changing MobileSettings.php to add a per-user mobile skin setting (I think this is possible?) would let a user change their mobile skin to Timeless, which is one workaround Mike Battaglia (talk) 14:41, 23 September 2018 (UTC)

One simple change I made is to enable the "Responsive" mode of the Vector skin, which is the default enabled MediaWiki skin on desktop. This leaves desktop the same, and also leaves mobile the same, but if you ever go to "Desktop mode" on mobile, it looks nicer. This makes it easier to do stuff on mobile that MinervaNeue can't do -- see below for more details - Mike Battaglia (talk) 18:42, 23 September 2018 (UTC)

nicer is subjective... PiotrGrochowski (talk) 18:44, 23 September 2018 (UTC)

Added special "Responsive" mode to default Vector skin

To make the default "Vector" skin more responsive, I enabled a special setting. This leaves everything the same on Desktop, but makes "Desktop mode" on mobile look somewhat nicer. I couldn't find any issues with it, but if it does, post here and I'll revert. I'll leave this for a while and then move to finished if nobody notices anything wrong with i. Mike Battaglia (talk) 18:08, 23 September 2018 (UTC)

Some people might prefer non–responsive skins so that the pages appear like in desktop. You should make it an optional setting, like you did with Selected just intervals by error. PiotrGrochowski (talk) 18:22, 23 September 2018 (UTC)

Right now the mobile skin is left alone - it's still MinervaNeue. Vector currently has responsive mode on. You may be misunderstanding "responsive" - the desktop mode should look exactly the same. But if you go on a mobile phone, but choose "Desktop mode" on the mobile phone (at the bottom of the page), you will get the nicely scaled responsive version of Vector. Basically, everything should be left exactly alone, except for "Desktop mode" on mobile. Have you seen any other differences that break things? If so, please let me know and I'll revert it. Mike Battaglia (talk) 18:33, 23 September 2018 (UTC)

"differences that break things" is subjective. There may as well be someone who hates anything that differs in mobile. In my opinion it's confusing design if the user chose every "desktop mode" it can and it still differs. PiotrGrochowski (talk) 18:38, 23 September 2018 (UTC)

Desktop mode was almost completely broken for me on mobile before, and with this setting, it works. I need some working desktop mode because MinervaNeue doesn't let me do everything. Do you have any concrete examples of something that is broken now? 18:45, 23 September 2018 (UTC)

You're making my brain crash with all these subjective brokens and nicers. PiotrGrochowski (talk) 19:03, 23 September 2018 (UTC)