The alias was apparently removed from tt-cyrl in TranslateWiki, probably because it's a Latin alias, so I guess they thought it belonged in tt-latn instead.

1.16:

'redirect'              => array( '0', '#yünältü', '#перенаправление', '#перенапр', '#REDIRECT' ),

1.17:

'redirect'              => array( '0', '#ЮНӘЛТҮ', '#перенаправление', '#перенапр', '#REDIRECT' ),

I've live-hacked the code to put #yünältü back in.

timming wrote:

Thank you.

What about the article count? Why did it decrease?

(In reply to comment #3)

What about the article count? Why did it decrease?

The pages with '#yünältü' are not detect as redirects by MediaWiki (due the software update). That is why there were broken and the edits from the bot are detect as a change from article ('#yünältü') to a redirect ('#REDIRECT') and MediaWiki decrease the article counter by 1 for each edit.

The wiki needs a refresh of the article counter. I do not know, if that is possible.

timming wrote:

(In reply to comment #4)
Oh, thank you for explanation.

What should we do to restore previous article count? It is very important for our community, because we lost ~13% of articles, participants are a little unhappy with that fact, we have a goal to complete 10 000 this year.

Is there a way to count the articles (it wouldn't take much time, they are ~8000) in Tatar Wiki and update the counter?

Thank you for your help

The article count issue is now tracked in bug 27705

Article count refreshed with bug 27705, it now show 9,396 articles. Thanks duplicatebug :)

If the redirect issue is fixed we can probably find this bug report OR we might want to keep it to fix the live-hack added by Roan.

rashat_Kazan wrote:

(In reply to comment #7)

Article count refreshed with bug 27705, it now show 9,396 articles. Thanks
duplicatebug :)

If the redirect issue is fixed we can probably find this bug report OR we might
want to keep it to fix the live-hack added by Roan.

Thank you very much!

Are we keeping this open so we don't lose track of Roan's livehack? Or is there another reason?

timming wrote:

The problem is solved. I think the bug can be closed. Great thanks to all participants.

no longer blocks, then.

jeluf wrote:

Closing the ticket.