Do you still have backups of the old databases and can check if those indices existed at all in the old MediaWiki versions?

A quick fix for this is to extend the update hook to install different SQL files for MySQL and PostgreSQL.

Would a complete database import be an option?

After fighting this for some time now today I figure out that pywikibot.userinterfaces are indeed the root cause of T281643: Pywikibot: avoid double logging of output.

September 2024 report from pl.wikipedia - need to confirm about:config settings of the reporter

In T358020#9565952, @Legoktm wrote:

queue runner seems to have crashed

502 error with Gerrit is probably better to be filed on Phabricator, not on the talk page...

Ah, forget my babble. you are right, this is the "End call" button, although the browser calls it the "BACK" button (it says "Press BACK again to quit browser.")
The bad part about it that there seems to be not timeout between the presses, i.e. pressing End Call once, waiting 10 seconds and pressing it twice shuts it anyway.

Do we really need this?...

Thank you @Anomie for having this one un-stuck! Much appreciated.

Is this still a problem?

Is this *strictly* necessary to make https://packagist.org/packages/davidbarratt/mediawiki work? (I mean it currently requires this patch):

What about replacing the "Settings" key with a language switch?

Can you put it on https://etherpad.wikimedia.org for others to see?

"Hi, What would you learn today?" seems to unnecessary take the screen space and - again - needs to be translated. "W" letter takes enough space already.

Would that be possible to have a build-time option to disable this and other forms of tracking? For example in webpack.config.js

It works now, but the problematic code is still there in

Maybe KaiOS app could simply be also hosted on .wikipedia.org and just presented there in a similar way the mobile interface is?

Personally I don't like this idea. I have a very small screen and having a clean, fast, readable search screen is enough. Please do not clutter those tiny displays....

Yes, that's what my patch is about.

In T237752#5866848, @Milimetric wrote:

Does dev guide say something which devices will use 56px and 84px icons?

So, I have just spent an HOUR trying to troubleshoot this with a very nice and patient new user. It was not obvious at all what is the problem (I was suspecting some wrong license settings first but we double checked).

Just got this reported by a new user on IRC... very annoying!

My deployment procedure

@Aklapper I found the code at https://github.com/wikimedia/wikipedia-kaios - I even managed to build it and deploy on my Nokia 8110. I just ran

Thanks. I just realized there is a something I don't like with those links, just filed T244618: Canonical wikistats v2 URLs should be permalinks to the period the graph is referring to for this... possibly a duplicate though

What is the canonical URL for the new stats after go live? For example, will this be

Wow, thanks @ashley ! 💌

I think I have found something related to this:

1. Switched to Polish language globally
2. On the search screen started searching for "Tupo"
3. then selected entry called "Tupolew Tu-154"
4. and pushed the center button "WYBIERZ" (select)
5. Tu-154 article loads (I am redirected correctly)
6. Pressed left button ("Menu")
7. Picked "Language" from the "Article Menu"
8. A message appears "Loading..."
9. The app is stuck and needs to be killed

Thank you. I think that getting rid of "/v2" is not a very worthy goal in itself. It could be also changed to something else. Unfortunately, I don't have a team to consult :)

Do we need to log every peep of the user?

Also you might want to add some cache control parameters to js and css assets if you like, all that inside of /srv/src/wikistats-v2/dist directory block.

What about something like this:

Great, we should just test it with MySQL and here we go...

Can you check if https://gerrit.wikimedia.org/r/c/mediawiki/extensions/CheckUser/+/561848 brings us further? (I haven't tested this at all yet)

@Lahwaacz Do you have environment where this could be easily tested?

@saper - keeping a project that is no longer updated as the root and leaving the maintained version in a subfolder means nobody will find it.

Hi, I don't understand this example from https://wikitech.wikimedia.org/w/index.php?title=Analytics/Wikistats/Deprecation_of_Wikistats_1&oldid=1844348:

@kostajh I have changed the status to "Declined" (it could have also possibly be "Stalled" but that implies being open). I got lured in here hoping that something has been positively done in this respect - but it wasn't; therefore I suggest to leave it as "Declined" until it is re-opened again.

Yay, thanks @matmarex !

I don't think we should be changing core schema to fix this little thing :( but I'll think about the JSON abstraction in core that can be used by other parts of the code.

After trying this for a first time (due to reports on plwiki) I second what @CKoerner_WMF and @Alsee are saying. Edit->preview->edit->preview->edit->preview->submit flow should be natural and not interrupted with modals, animations and hidden buttons. In this regard I am pretty happy with a current "live preview" feature of the 199x/2010 wiki editors. Can we get rid of modals altogether?

@mwjames It is a pretty old request - I wonder how did you get there in the first place.

Isn't that a duplicate of T17823 ?

What does $wgDBserver = '' mean? "localhost"? "use socket"?

A tiny example of what I mean is https://phabricator.wikimedia.org/T203850 - had we had an abstraction to handle JSON values in IDatabase, we wouldn't need fixes like https://gerrit.wikimedia.org/r/c/mediawiki/extensions/TemplateData/+/521193 - JSON could end up as JSONB in Postgres and a BLOB in MySQL. Sometimes the abstractions would need to go much higher than this, providing a DB-specific implementation of it.

Excerpt from an announcement from June 2019 about Gitlab dropping MySQL support:

Recently I got into https://github.com/djrobstep/migra which does an amazing job for PostgreSQL to create what some people call "migrations" between the database versions. This makes Proposal 1 quite attractive - it could be used to create a target empty schema (from JSON) and then just use such a tool (or similar ones) to migrate. There are limitations (migra itself is PostgreSQL-only, version 10+, other tools must have been used for other DBs), but I wouldn't give up on Proposal 1.

Regarding the first question I'd think we could do it in a step-by-step approach: take something ready to use (Mastodon/Pleroma/whatever) and see how that could fit and work from there. Then we'd have at least a something to extend OR a pilot experience with requirements for a good custom system if needed.

Yes, but the search can be made better. Discourse is almost good, but it has a habit of limiting brand new user options, which is a big limitation of a Q&A system. But it can be configured not to do this (giving more options at the level 0).

Maybe a solution could be solved with federated networks like T198363: Consider ways to integrate with federated social networks ? One might define additional activity to "mark answer as correct", or for upvote/downvote if such features are desired.

Just ran into this issue when troubleshooting something on 1.31.0, pretty confusing!

Are we really so nicely abstract on the DML level? My impression was this is a MySQL app and other databases apply workarounds to get rid of MySQL-specific things sprinkled around the code.

Okay, but why? Do we need to read a whole SVG as XML to figure it out? In this case this option is useless. On the other hand, I cannot reproduce this with a unit test.

@Paladox no, only some oldish Gentoo for now.

@Paladox can you try to apply https://gerrit.wikimedia.org/r/449915 and run phpunit on your MW instance:

Just need to report that a fresh install of 1.29.1 still has this problem :(

Thanks @Reedy!

SQL injection? We do not quote $default at all?

Do all those tasks really need to be restricted? it is difficult to follow what is going on...

Apart from moving to 9.2 - which is a no brainer, seems like a tough choice. I've had impression the authors of the original PostgreSQL port tried to fix the deficiencies of the MySQL schema to some extent, resulting in well-known incompatibilities.

The Extension is currently unmaintained

Same as T161864 reported earlier by @Amire80