Apr 10 2022
can you please explain what my task has to do with task T305803?
Oct 28 2021
German Wiktionary has now Version 1.38.0-wmf.6 again and the bug seems to be fixed
Yes, see the comment from the stashbot at 4:04 pm in T293947
Hi @Vlad.shapik and @Majavah,
Feb 2 2021
Sep 16 2020
In de.wikt, it has only occurred to one user so far and I've already taken care of that.
Sep 15 2020
Sep 14 2020
@matmarex. Ok, now I see it. The user "Wilkibur" in dewikipedia did many edits before July 2019, the time when "autopromote" no longer worked.
In dewiktionary we have the user "Beitrag50330" with over 360 contributions in NS 0, see here.
Jun 24 2020
Hi @Urbanecm , thank you very much for the quick implementation.
Mar 5 2020
Hi @Ladsgroup, undeleting of entries now works again without problems. Thank you very much for fixing the bug.
Feb 21 2020
Sep 19 2019
Hi @Urbanecm, no, these are old log entries.
Aug 6 2019
Jul 30 2019
Jun 25 2019
Ok, thank you for the info. I will watch the "user rights log" in de.wiktionary.
I don't know why. But it works fine all the years.
Hi @Reedy, yes, i'm very sure.
Jun 24 2019
About 2 hours ago, another user automatically became "editor" (Sichter), see https://de.wiktionary.org/wiki/Spezial:Logbuch?type=rights&user=Hans-Friedrich+Tamke
@Reedy: Many thanks for the quick help. Now it works again.
Hi @Reedy. can you possibly still set up the config so that the admins can grant (or revoke) "autoreview" and "editor" again?
I am not sure. We became aware of it today because the user Peter Berbe automatically became an editor. Udo T.
The same behavior as in T225115 a few weeks ago.
Hi @Reedy, but we can't remove the group from the account, because no admin is able, to grant (or remove) the right for "autoreview" (passiver Sichter) or "editor" (Sichter). (Part 1 of the task).
Jun 5 2019
Hi @Reedy, now it looks the same as before. That's what we wanted.
Ok, I take the picture in English from the other task: we formerliy didn't had the line with Accuracy, Depth and Readability.
I think $wgFlaggedRevsTags['accuracy']['levels'] = 1; is the correct config for us
Hi @Reedy, in the above picture we formerly didn't have the line with "Status gesichtet (patrouilliert) Tiefe: einfach Lesbarkeit: akzeptabel"
Hello @Reedy , thank you very much, this problem is now fixed.
seems also like a deployment blocker, therefore I rise the priority to "High". Please adjust if I'm wrong.
It's quite possible that this will be in de.wikipedia (and other wikis?) tomorrow as well.
I changed the priority to "High" because I think its very possible that this will be happen in de.wikipedia (and other wikis?) tomorrow as well.
In de.wikipedia these two rights are assigned to admins only. I think, because every bureaucrat is also an admin.
Jun 4 2019
Hi @Urbanecm, many thanks. I have already tested it and everything works great as desired.
May 19 2019
Hi @Urbanecm, I would like to ask you, what's the reason for the long duration? Until when can we expect an implementation of the change?
Apr 25 2019
As I understand it, the change only needs one or two more code reviews.
Mar 3 2019
When can we expect the implementation of the protection levels? Do you need additional information from us?
Feb 16 2017
Aug 7 2016
@MarcoAurelio : Thanks a lot for the previous hint and the info now. I have just restartded my bot with OAuth and it works fine now in all languages. Best regards Udo T.