Reopen if still wanted.

Sorry for the late response is this still wanted?

In T59#1059, @MacFan4000 wrote:

If it doesn't seem like it's installed then it's probably down to caching.

If it doesn't seem like it's installed then it's probably down to caching.

Installed

Yes we don't have transwiki importing configured, but you can still get an xml file through Special:Export on wikipedia, and then import it on testwiki through Special:Import/

Extension is unmaintained

@BlackWidowMovie0 please stop modifying closed tasks

Hi, what is the purpose for this task?

Twinkle is a gadget, not an extension. Therefore any user can add it.

Found the GitHub project: Twinkle

Already installed

this has been open for a while, apologies, didn't see this before. User that requested has gone inactive

@MacFan4000 comments? I'm not sure I want to install a brand new extension for testing, however, the only real blocker is doing it (or the task going stale).

I’d rather not have flagged Rex’s on the entire site, just in protection mode is what I prefer.

This is a non-default option that makes flagged revs work only as a protection system. It is not a common setup and disables a lot of functionality. Would it not be best to allow testing with the most common/default configuration. We already have a protection system that works just fine, with this enabled I think that there is almost no point to having Flagged Revs installed at all. Please disable this so we can test the full/default functionality of the extension.

TBH, I'm not sure we really want/need to change it. Unless there is some sort of need for testing that particular toolset.

After unsetting that config you can remove the editor and reviewer rights grants from the config as they are the same as the extension's defaults.

Accualy , it seems to be becuese $wgFlaggedRevsProtection is considered some sort of "simple mode" or "simple config" of the extension.
I suggest setting it false to enable full functionality of the Flagged Revs extension.

I figured it out. it is because of this code in the extension.

Lol, Mybe I try to fix

I don't know that this is really needed. I don't think many users would be confused.

I've already pull into the server using SFTP also in git before. So I pull 2 version, via git and sftp(to the server).

Two reasons why its not working

1. you may not have pulled the latest changes to the server
2. The submodules are not correctly added to the repositorys

Mkay, I reopen because have issue, can someone go to server and check the wfLoadExtension at localsettings.php, I put some extensions but not load anytime, should me to push via git.

That is include 'root' group not sysadmin group

sometime, I want to edit LS, but I can't save the edit, nah, maybe have a wrong chmod or something else.

LoL, I think this is just for admin, I usually push to the server, :) and I always be there.

Two questions: Why is this task protected? And why not do it through github?

CentralAuth is meant for wiki farms to create a shared account database so that you have a single account across wikis. We are not a wiki farm. We are a single wiki. so it wouldn't really work.

Hey this isn't urgent.

I'd personally be willing to help out with locking in the future. Also I believe that checkusers can masslock spam accounts (good for sleeper hunting/mass stopping spambots/sleepers).

Done

Done

Thanks for quick response

It’s unmaintained currently which means that it likely won’t work with newer versions of MediaWiki.