#Outdated translations get stuck as marked outdated after updating/confirming. [Solved]

17 messages · Page 1 of 1 (latest)

polar crag
#

I translate Lethal Company wiki to a different language using translation interface. Recently I started to notice that the pink background used to mark outdated translation blocks stopped disappearing after I update the block and it doesn't contribute to page's translation percentage, however the actual text inside does change to whatever translation I submitted.

If a completely new, not yet outdated block was marked for translation and I submit translation of it then the issue doesn't appear - completely new blocks don't get marked as outdated and contribute to page translation percentage properly.

polar crag
#

Issue still relevant

polar crag
#

Outdated translations get stuck as marked outdated after updating/confirming. [Still relevant]

frank shore
polar crag
#

Outdated translations get stuck as marked outdated after updating/confirming.

polar crag
polar crag
#

Issue got fixed once admin granted unfuzzy to more groups, thank you very much

#

Outdated translations get stuck as marked outdated after updating/confirming. [Solved]

frank shore
#

No problem. I've made a PR to add this to the default permissions, so hopefully this will be fixed by default in the future.

empty kite
#

I would have done that weeks ago if I had known it was a thing

#

My assumption had been that for new wikis ManageWiki inherited the permissions from extension.json, but for existing wikis the content stored in the database overrode the defaults completely

#

I guess that was wrong

frank shore
empty kite
#

Indeed

#

Fun fact - in the code review of the patch that added the unfuzzy permission (to solve a longstanding vandalism problem on MediaWiki.org) exactly this eventuality was predicted.

#

Not specifically on Miraheze, but I was told to grant it to everyone rather than to only logged-in users for that reason.

frank shore