Thanks Amir and Andre!

intitle:/dari/i intitle:spanyol would not work, as the second intitle would be ignored and it would search "spanyol" on the text body. But intitle:/dari spanyol/i works like my original intention. Thanks.

Thanks Trey. I'm interested in the last option, but I'd like to hear others chimed in first.

it's back to what it should be as of today

In T117580#1783718, @Umherirrender wrote:

Same as with the sitenotice: T22870

The sidebar is cached and not reparsed for each page so you cannot use page variable or time variable

After the old eAccelerator was replaced by XCache, the error was resolved.

I was pointed out to the fork managed by people at NEC at https://github.com/NewEraCracker/eaccelerator. Is there anybody who used the original eAccelerator previously and got the error and moved to this branch? Did it solve the problem or not? The person who I could ask to update the eAccelerator was mostly not available to reach due to his busyness, so I can't test it for myself.

What about at least giving better error than "There were no results matching the query."?

btw, imo admin and editor user groups should inherit autoconfirmed too. some of the users with editor status who lost their autoconfirmed lamented that they couldn't move, upload, and have to fill captcha. Or is that for another task?

Thanks for the confirmation and T101983, I'll wait for it to be resolved instead.

@Krenair: the stewards bit is not true, though. I'm a steward, and that option was still greyed out for me (on id.wp), but I have that option on meta, though (where I'm not an admin, so it's must be my steward flag)

So this is only true for en.wp then? https://en.wikipedia.org/wiki/Wikipedia:User_access_levels#User_access_level_changes

I could see _why_ it is currently as it is now, so I'm just wondering if it is possible to add a lightweight version of the bundle.

Usually, the reset link would be sent to the (original) email address, thus it's hard to exploit the password, if you don't control the email also. But since email is optional in WMF projects, then this obviously would not work for someone that didn't provide emails.

Thanks jay, for the ping. My reading of the original post seems to me more about the Jawi script (a.k.a. Malay Arabic), rather than Jawa (or Javanese) script, which is derived from Sanskrit. As far as I know, Malay projects (-pedia, -tionary) tries to incorporate Jawi script, and I heard that min.wiki (Minangkabau) also been thinking about it. Javanese script, on the other hand, is incorporated in Javanese (jv) projects, and it is our plan to someday have a converter like that of Kyrgyz or Uyghur wikipedias. Help on that aspect would really be appreciated.

Autocomplete is not intuitive, and potentially wrong. A dropdown would be better in the "Projects" field. Thanks for associating the task.

Awesome. Thanks Runa, Santhosh and everyone else.

Upon reseraching more towards the subject of long vowels, I found out that the sign that looked like a colon was not actually a colon (:) but another unicode symbol (ː), and replacing colon by that symbol would solve the problem that we're having. So I'll close this task.

In Mohawk language, for example, if we were to link the words in the example below:

It would be a good case study, since Minangkabau Wikipedia is our newest Wikipedia, and already relied a lot on translation from Indonesian Wikipedia articles. Minang speakers are almost all diglot too.

On top of my head: