I got the answer from the HTTPSEverywhere developer:
HTTPSEverywhereUserRules/ is not supported with WebExtensions and won’t be supported. My understanding is that security restrictions for WebExtensions block it from reading from the filesystem in the way that the HTTPSEverywhereUserRules/ approach needed.
Do you have a list of some examples of broken pages?
The good news is nothing is lost. For once, we have mysql backups (but then we’d loose the work after the translation unmark, so we’d need to back that up first before we roll back). Also not sure forum and wiki can be separately restored, fortasse would know. Secondly, if we can identify the broken pages, the rollback can be rolled back.
<translate>, </translate> and such I can later remove with mass search and replace. For now, I just try to identify rolled back pages and roll them back. Hard, since the translation removal is not part of the log.
I think we should cut the tiny section existing in it’s own page (VFAQ) into the FAQ itself and delete that VFAQ page. And also shift up FAQ to the Download section on main TOC page.
Yes. Feel free to move that page. Let the new FAQ be a FAQ and the VFAQ
can be moved elsewhere and/or moved to where appreciate.
Also some stuff like OpenBSD was a FAQ in past, but nowadays it’s not
being asked anymore. So FAQs naturally need cleanup. (So that
information could be moved elsewhere.) But perhaps no one asks about it
since the reply of this is easily found on google and the answer
prevents any further debate?
I think when you ran that auto-run on removing certain pages from translation in the last few days, it returned the page edits to their very old (rough) versions.
The “tvar” variable has broken almost every link on the main Documentation page, so I’ve removed them, plus the “[languages/]” insert which was appearing in plain text, instead of doing anything useful.