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.

@MacFan4000 any objections?

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

If there was a consistent issue where there was abuse being stopped by the abuse filters that needed CU information to look into, I'd do it, but there just hasn't been precedent.

I would like to suggest reconsideration of the abusefilter-private right. Abusefilter now logs private data access. This must be enabled with the $wgAbuseFilterPrivateLog setting and the abusefilter-private-log right is required to view it. I suggest this config option be enabled and both rights be added to the checkuser group.

I support a change of default skin to "Vector", I believe that "Refreshed" is difficult to use due to the absence of some sidebar links such as "Special pages".

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.

Done

I made a mistake in my last PR. Please merge this one quick: https://github.com/Test-Wiki/mediawiki/pull/6

So, I was able to recive MediaWiki email just fine (although it went to my spam). Configuring phab mail is rather annoying

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.