I'd like to also request such a feature. An interface on a wiki page similar to Google Spreadsheets would be convenient for large datasets. There are some open source javascript spreadsheet libraries like SlickGrid that might be able to be adapted to Mediawiki.

This is solved for me. I'm not sure if there's actually any bug to fix, so if not it can be closed.

In T326046#8495181, @Xqt wrote:

I've tested the generate-family-file script and indeed it added that method to the Family file. I think it is a better approach not to copy a family file example from mediawikiorg but either to use this script or use AutoFamily.

If I use the above code in the family file, then response.request.body equals:

So Void over at Miraheze's Phabricator figured out that I needed to add this code to the family file, and now it logs in fine:

Is there a way to output and see the exact request sent to the server when it serves up HTML instead of JSON? This is what I spent a couple hours digging through the code for, to see if maybe the format=json was missing or something else was wrong, but I didn't have the skills to pinpoint where the request is made.

@Xqt Ok, thanks, I'll create a bug report on Miraheze's phabricator then.

In T326046#8493149, @Xqt wrote:

@Dimpizzy: With the patch given above I've adjusted the error warning a bit. This is all I can do in this case if the server is temporary down. The request will be retried several times.

In T326046#8493049, @Xqt wrote:

I played a bit with this issue; this bug occurres randomly. It looks like the server is temporarily not available. This also means that Pywikibot 8 does not solve it.

In T326046#8493007, @Xqt wrote:

In T326046#8493004, @Dimpizzy wrote:

Just to satisfy my curiosity since I spent a while trying to find it, could you say what the issue was, if it's not super complex?

I have no idea at the moment but the LoginManager was rewritten and support of older wikis was given up.

Sure, Pywikibot 8 (master) is ready to use but it has "under development" state which means it could fail if new features are implemented whereas "stable" means it is ready for production systems. Anyway using master could help to find and fix those bugs which aren't detected yet during CI tests.

Just to satisfy my curiosity since I spent a while trying to find it, could you say what the issue was, if it's not super complex?

In T326046#8492986, @Xqt wrote:

I was able to reproduce it. This issue is already solved with Pywikibot 8 which is the current master branch but still unser development. I could backport a relatedchange to stable version 7.7.4 or we can just wait for finishing Pywikibot 8 development (which will be in few weeks). You have to update your bot anyway. What would you prefer?

1. use the current master branch
2. wait for a stable release which solves this bug

@Xqt: I just copied the example from the manual and changed it to suit my wiki.

My wiki experienced this bug yesterday on a Miraheze site. https://phabricator.miraheze.org/T10143