@Aklapper hello, if I may you're wrong about the "no community discussion about this idea" concerning the French Wikibooks because two of the four active admins came here to support the discussion I had initiated and mentioned above.

Hello, about the fragmentation of discussions you've mentioned several times, I do not have any better solution than the one I had proposed above: document the Phabricator relation system into the wiki and participate to it.

Hello, sorry but today I still don't know how many French or English Wikibooks tickets we have, so I can't close the deprecated ones or treat the others with my PHP and JavaScript skills.

DavidL has taken the time to split several books, but on https://en.wikibooks.org/wiki/Category:Pages_with_too_many_expensive_parser_function_calls we can see that 14 are still broken for more than seven months.
And some readers are complaining: https://en.wikibooks.org/wiki/Talk:F_Sharp_Programming/Print_version

Hello, I've created a PR on https://github.com/x-tools/xtools/pull/441

Hello, actually I had posted this idea on:

The typical use case would be a ticket created by the Wikibooks community, only about Wikibooks (not other families), and tagged by it.

As an administrator of two Wikibooks, I'm unable to tell you now how many tickets about Wikibooks have been opened, if there are some doubles, or if some of them need a community input to be treated (like https://phabricator.wikimedia.org/T280019).

Since the 8th June 2022, all the Snottywong tools have been shutdown, because of a total incompatibility between the old code and the new infra: https://en.wikipedia.org/wiki/User_talk:JackPotte#RFA_counter_downloading_a_cgi

All my jsub crons have been moved to toolforge-jobs run --schedule

In conclusion, https://www.mediawiki.org/wiki/Manual:Pywikibot/BotPasswords/fr worked (Pywikibot could re-login) if my user-config.py only contains the same account for all wikis.

Adding site.login() in the code does the same.

Now my bot works with toolforge-jobs run, but crashed when login is required.

With Pywikibot 7.7.0, I've removed the crashing useless pip dependencies, and it crashed on dbus-python.

After solving my pip conflicts, everything works on my PC, but my toolforge-jobs run on the server crashes on pycairo 1.16.2.

After refreezing requirements.txt it's another story:

Following https://wikitech.wikimedia.org/wiki/Help:Toolforge/Python, I've got:

Thank you for this message.
Actually I had already tried to migrate, the second March 2022 by testing:

toolforge-jobs run wt2 --command ./WT.sh --image tf-bullseye-std

instead of my current:

jsub -mem 1G -once -quiet -N WT "$HOME/WT.sh"

But it didn't do anything and toolforge-jobs list is empty after, still today.

Sorry to ask but if the problem won't be solved here in a few days, I need to know in order to replace all smallest <syntaxhighlight> by <pre> tags by bot.
Because print versions are worth a little less readability.

Actually by experience the hard-coded page solution in the print version has the exact withdraw of the redundancy code anti-design pattern: it's never up-to-date.

Still working on it...

Perfect, thanks a lot

Actually an EDP is de facto in place since 2006: https://fr.wikibooks.org/wiki/Cat%C3%A9gorie:Images_en_fair_use

OK I've figured it out, it was my Firefox module "ModHeader" which used to send the HTTP header key "Authorization" with a token.

In private navigation, the bug does not occur.

This bug also occurs if I click with Vector on the star icon, to add a page to my watchlist or try to log off.
If I empty my cookies (and local storage), I'm unlogged but if I click on "log in" the site logs me in without any password and the bug persists.

I use Firefox, by just clicking on "mark as patrolled" as I thought it was clear.
As far as I know, the bug does not occur on Chrome or Edge.
I could bypass the bug by adding &debug=true into the Firefox URL bar.

Thank you matmarex, you've solved it for good.

The error 500 is due to the absence of Python package on the new Toolforge server:
"ImportError: No module named MySQLdb"

I've just found another similar file: https://commons.wikimedia.org/wiki/File:LL-Q56499_(arq)-Reda_Kerbouche-%D9%83%D9%8A_%D9%87%D9%88_%D9%83%D9%8A_%D8%A8%D8%A7%D8%A8%D8%A7%D9%87.wav.

Sorry but I had posted this bug in a hurry while going to work. I confirm your analysis that the bug is about the player disappearance on every wiki which calls this file.

I'm not sure that it has begun today, but as I edit one of these wikis every day, I should have noticed any change the same day, and I'm convinced that this bug is systematic and has appeared this week.

Nice try, but does anyone have metrics about this experiment?
https://stats.wikimedia.org/wiktionary/FR/TablesWikipediaFR.htm doesn't show the figures of how many IPs and accounts have modified the French Wiktionary before and after the Visual Editor tab, in April 2016.
However it could have been interesting to compare them to the before and after French Wikipedia double tabs installation.

As far as I can see, the only problem is just to be able to find who ever is trusted enough to have the right to modify the French. Wiktionary LocalSettings.php.

This tool has been improved one year ago: https://phabricator.wikimedia.org/T114559
And today, the URL above has worked (after five minutes, but still): https://tools.wmflabs.org/jackbot/snottywong/cgi-bin/rfastats.cgi?name=JustBerry&max=200&startdate=20180101

There's nothing complex about this request: the community just wants to provide the two tabs to the editors: the wikicode and Visual Editor.

Yes, the bug concerns the raw HTML and wikicode.

Sorry, I was not angry at you particularly.
If it can help, you can just come to our village pump and ask if I had translated the vote correctly here and if it still needs to be applied.

For god sake, the community of the greatest French dictionary in the world had already precisely discussed about all these options, and voted two times for them for several years (I had already posted the links in this ticket and I'm tired to repeat it, with all due respect).

No please apply the consensus which just consists in two links, like on the French Wikipedia.

Nope, nowhere. I've tried:

• https://fr.wiktionary.org/wiki/MediaWiki:Edittools which uses specialcharsets
• https://fr.wikibooks.org/wiki/MediaWiki:Edittools which uses specialchars

Herewith my second diagnosis:

• On Chrome, there isn't any bug.
• On Firefox, the bug occurs systematically (but never with debug=true), logged or not, and there isn't any JS error in the console (debug or not). Given the fact that the IDs specialchars & specialcharsets are native and not erased in the site CSS and JS pages, I can't figure out how to resolve this quickly and properly.

OK, as this is working with &debug=true but still not without it, I'm going to follow this process...

Problem solved.

Well seen, https://fr.wikiversity.org/wiki/Mod%C3%A8le_MOOC_administration has just been created two days ago after the return of Xtuc-Sven, and its GitHub link is supposed to help any French speaker to repair with the non-minified code.

Hi, the actual community desire would have been to offer two tabs to the IPs, that's why we're respectfully asking to add "edit the code":
https://fr.wiktionary.org/w/index.php?title=page&action=edit
near:
https://fr.wiktionary.org/w/index.php?title=page&veaction=edit

I don't know if a maintenance period was planned, but currently the "previous" and "next" links in the categories are not working properly anymore.

I can see one: the link behind "Printable version" is the printable page (https://...&printable=yes) but with Firefox we can never reach it.

Sorry to insist but I couldn't figure out how several Wikis of the foundation including a few Wiktionaries could get this extension before, but the greatest French dictionary of the world wouldn't be worth the effort?

We have chosen "uca-default" before "uca-fr" because it includes it, among several other languages collations we publish.

Yes if I delete all my cookies I've got the pop-up, but that's not the problem.

Sorry but I never get any pop-up during my tests: so I'm totally forced.