Jun 15 2019
Potentially tasks: (both paths)
Jun 14 2019
Closing, as technically the asked question was answered.
Jun 13 2019
(as far as I know) WikiApiary has never had a particularly thriving community
Jun 12 2019
many wikis disable automatic generation and instead periodically run maintenance scripts to regenerate them
Well yeah. However setting up cronjobs to work on the miser mode pages is not complicated.
Seems like a good middle ground solution to me. Having those pages at least update every N weeks/months seems more preferable than not updating them at all.
Jun 11 2019
Aug 13 2018
Update: Seems the "populateRevisionSha1" maintenance script needed to be run with some "--force" option.
Aug 3 2018
Update: The maintenance script "populateRevisionSha1.php" was run. But ... it did not resulted in the empty sha1 fields being filled.
Aug 1 2018
Just for the record. Page moving can also trip on this.
(Page with single revision with empty sha1 field in this case)
(MergeHistory seems not effected)
Jul 30 2018
As general wiki-Admin(Administrator level) I can't, but I will definitely pass is along to the wiki owner/sysop.
But I also like to wait a bit before I do, to see if some other options might pop-up.
(Probably contact the wiki-sysop on Friday, hoping he has some free time in the weekend to run that fix.)
The sha1 field was added in MediaWiki 1.19. If a page was deleted before MediaWiki 1.19, it may have this field empty.
In this case its not limited to pages that where already deleted before the last MW 1.31.0 update. Its also effecting currently active revisions (after deleting them) created during the MW 1.21.1 installation. (because those revisions have empty sha1 data/fields to begin with. which can (not) be seen (any more) with this API query (as the problem was fixed).)