Page MenuHomePhabricator
Feed Advanced Search

Jul 24 2021

Beeswaxcandle added a comment to T257066: Extension:Score / Lilypond is disabled on all wikis.

OK, we're now running lilypond 2.22.0 which should make some more things available in safe mode. Null edits should trigger re-renders.

Jul 24 2021, 3:04 AM · User-notice-archive, Patch-For-Review, MW-1.36-notes (1.36.0-wmf.26; 2021-01-12), Security-Team, Security, WMF-General-or-Unknown, MediaWiki-extensions-Score, SRE

Nov 3 2020

Beeswaxcandle added a comment to T257066: Extension:Score / Lilypond is disabled on all wikis.

Since a couple of days, saving any article that calls the score extension leads to the score becoming invisible (without having the score itself changed). So the workaround of reading pre-rendered files from the cache seems no longer to be working. It is really annoying that the problem is still not solved after such a long time of waiting. There are currently 1,241 pages calling score on en:wikipedia, 748 on de:wikipedia which are endangered of losing the proper display of the contained scores.

Nov 3 2020, 5:36 AM · User-notice-archive, Patch-For-Review, MW-1.36-notes (1.36.0-wmf.26; 2021-01-12), Security-Team, Security, WMF-General-or-Unknown, MediaWiki-extensions-Score, SRE

Aug 16 2019

Beeswaxcandle added a comment to T230499: Musical score on English Wikisource does not render (due to misplaced tilde).

@Peteforsyth, no, the MIDI file was not generated, as it is linked to the same command as the image. The LY syntax is valid, but it seems at first glance to be too complex to be run all at once. Try splitting it?

Aug 16 2019, 6:51 AM · MediaWiki-Shell, MediaWiki-extensions-Score, All-and-every-Wikisource

Mar 20 2019

Beeswaxcandle added a comment to T218535: Score extension now leaving large amounts of space on rendering.

Impossible to have a full list of broken scores, but they can be fixed by adding a comment to the scores, which will force regeneration.

No true. This is possible. Only pages with the "score" property edited in specific time period are affected and number of wikis that use score effectively is limited. Basing on such a query:
https://quarry.wmflabs.org/query/34588
I can likely provide a full list of broken score images.

Will it be helpful?

Mar 20 2019, 7:09 PM · MediaWiki-Configuration, Wikidata-Campsite (Wikidata-Campsite-Iteration-∞ (On Hold)), Wikidata, Patch-For-Review, MediaWiki-extensions-Score, Regression

Mar 19 2019

Beeswaxcandle added a comment to T60688: (Piano)Staff.instrumentName=#"Clarinet" returns only the 4 or 5 last characters.

This is known Lilypond behaviour for "long" instrument names. See Lilypond documentation for solution. An explicitly declared indent is required in a layout block. Doing this is standard Lilypond practice.

Mar 19 2019, 2:14 AM · MediaWiki-extensions-Score

Mar 18 2019

Beeswaxcandle created T218535: Score extension now leaving large amounts of space on rendering.
Mar 18 2019, 5:10 AM · MediaWiki-Configuration, Wikidata-Campsite (Wikidata-Campsite-Iteration-∞ (On Hold)), Wikidata, Patch-For-Review, MediaWiki-extensions-Score, Regression

Jun 13 2017

Beeswaxcandle added a comment to T30856: Remove classic edit toolbar from core.

I think that I had a misconception here. This is indeed about removing it from MediaWiki without providing a replacement.

There may be a replacement; that depends upon whether anyone volunteers to write it. There is no technical impediment to copying this into a local gadget or making a user script that could be run by interested individuals on all the wikis.

In fact, this may already have been done, because we have a lot more people at two wikis saying "I'm using this" than the preferences database knows about. Speaking of which:

@Beeswaxcandle, please look at the Editing tab of Special:Preferences at the English Wikisource. The actual prefs settings matters more than your editing toolbar (because the appearance could have already been replaced by a local gadget or user script). Please tell me what the settings are for the section of prefs that's shown in the first screenshot at T30856#3335615 .

Jun 13 2017, 7:22 AM · User-notice-archive, MW-1.32-notes, MW-1.29-release-notes, Technical-Debt, JavaScript, MediaWiki-Page-editing

Jun 10 2017

Beeswaxcandle added a comment to T30856: Remove classic edit toolbar from core.

I had the sudden thought to check what my toolbar on wikispecies and enwikiversity is. It's the "classic". I haven't edited on either since before the "enhanced" toolbar was made available. This suggests to me that every editor who was editing prior to 2013(?) on a project and who didn't opt in to the enhanced toolbar is still using the "classic"—many of them without realising that there is an alternative.

Jun 10 2017, 1:50 AM · User-notice-archive, MW-1.32-notes, MW-1.29-release-notes, Technical-Debt, JavaScript, MediaWiki-Page-editing

Jun 9 2017

Beeswaxcandle added a comment to T30856: Remove classic edit toolbar from core.

Given that I don't know anyone with Javascript as a second language

https://en.wikisource.org/w/index.php?title=User:Beeswaxcandle/common.js&action=history shows that you've edited that page more than 300 times, and not just to copy and paste someone else's work. Everything on that page is (supposed to be) Javascript. Are you sure you don't know any Javascript?

Regardless of your belief in your proficiency, these lines:

// == SIDEBAR TOOLS ==
/**
 * WikiEditor specific
 *
 * Custom buttons ONLY when Prefs set to - Enable enhanced editing toolbar - is selected,
 * Enable wizards for... - must not be selected. Show [old]edit toolbar - should be off.
 * based upon - https://github.com/he7d3r/mw-gadget-ExtraEditButtons
 */

make me suspect that you are already not using the editor in question.

The editor in question can be seen only when "Show edit toolbar" is enabled but "Enable enhanced editing toolbar" is disabled in Special:Preferences – which is the opposite of what this line requires. Could you go check your preferences (the Editing tab) and tell me which items you have selected/unselected?

Jun 9 2017, 8:19 PM · User-notice-archive, MW-1.32-notes, MW-1.29-release-notes, Technical-Debt, JavaScript, MediaWiki-Page-editing
Beeswaxcandle added a comment to T30856: Remove classic edit toolbar from core.

@Jdforrester-WMF Have you looked at this usage for the Wikisources? I would think that numbers of the Wikisources utilise these toolbars (I know that I do). For the work that we do it is a cleaner and easier toolbar to use, *and* it is far easier to learn to code for the old toolbar than the new.

Sure:

WikiTotalActive last 6moActive last 1mo
enwikisource100
ruwikisource110
frwikisource000
dewikisource000
eswikisource000
ptwikisource000
Jun 9 2017, 7:51 AM · User-notice-archive, MW-1.32-notes, MW-1.29-release-notes, Technical-Debt, JavaScript, MediaWiki-Page-editing

Jun 8 2017

Beeswaxcandle added a comment to T30856: Remove classic edit toolbar from core.

The "new" toolbar is hopeless for me. I use a laptop with a smallish screen for all Wikimedia activity. The vast majority of that activity is on enWS. The narrow height of the "classic" toolbar is ideal in the ProofreadPage Extension. I have tried to use the "new" toolbar and it increased the amount of scrolling I needed to do, which caused a marked decrease in productivity. It simply uses far too much screen real estate for me to function adequately as a normal user.

Jun 8 2017, 7:27 AM · User-notice-archive, MW-1.32-notes, MW-1.29-release-notes, Technical-Debt, JavaScript, MediaWiki-Page-editing