User talk:Thorncrag/LQT Archive 1

Leave a message!

parenthetical statements in help:links
Hi! I updated an example on Help:Links a few days ago. After my first edit, I realized that having parentheses around the note included with the example was not consistent with the other examples on the page. None of the other examples' notes are parenthetical. So I removed the parentheses. Later, you added them back with the edit summary of "(Undo revision 362520 by Lsloan (talk) - not consistent)".

I disagree with your analysis, and I could just remove the parentheses again, but I wanted to learn from you why you thought it was not consistent to remove them. Can you please explain? Thank you! --Lance E Sloan 17:31, 12 November 2010 (UTC)
 * I'm not precisely sure how this happened, but it has to do with the pending changes system. When I first intended to remove the parenthesis it seems I instead undid the one removing them, and at that time, I did not know that there were subsequent pending revisions.  Then, when I then tried to approve my revision instead of approving just it it seems to have approved all pending revisions instead hence restoring the parenthesis.... Wow, that's confusing.  I'll fix it :)     Thorncrag    21:13, 12 November 2010 (UTC)


 * Oh, I see... So I was just wondering, how does the pending changes system work?  I've seen links that say a change is pending, but I didn't see any documentation about who can approve changes or how it's done.  I've set up a MW instance at work for my colleagues and I think this ability to let some people make changes while others' need to be approved would be helpful.  If you could point me to some documentation to get me started, I'd appreciate it!  --Lance E Sloan 14:10, 15 November 2010 (UTC)
 * If I fully understood how it worked on MediaWiki.org this wouldn't have happened... hehe. Nevertheless, the only documentation as far as configuring can be found at Extension:FlaggedRevisions.  I setup FlaggedRevisions at my org basing it on Wikipedia's configuration to do precisely what I want, have all changes be pending until reviewed by bureaucrat.  Here's what I used for my config in LocalSettings.php, with some notes that I added as I understand the config options, perhaps it will help you:

include_once('extensions/FlaggedRevs/FlaggedRevs.php');
 * 1) Flagged revisions - used to hide edits until approved by specified user(s)
 * 1) Flagged revisions - used to hide edits until approved by specified user(s)

# This should stay disabled $wgFlaggedRevsAutopromote = false; ### This group is shown pending changes by default ### I'm disabling this - I don't think we want this to happen even for managers $wgFlaggedRevsExceptions = array( '' ); # Specify namespaces where it will apply ### customize later as needed $wgFlaggedRevsNamespaces = array( NS_MAIN, NS_PROJECT ); # Is a "stable version" used as the default display # version for all pages in reviewable namespaces? $wgFlaggedRevsOverride = true; ### This doesn't seem to be a valid setting - not in FlaggedRevs.php $wgFlaggedRevsReviewForDefault = false; # We have only one tag with one level ### This removes the quality tags, despite seeming to define them below $wgFlaggedRevTags = array(       'status' => array( 'levels' => 1, 'quality' => 2, 'pristine' => 3 ),    ); # Restrict autoconfirmed to flagging semi-protected ### We don't use quality flags (at this time) ### I have no idea what this var does, but don't think it's necessary ###$wgFlagRestrictions = array(   ###    'status' => array( 'review' => 1, 'autoreview' => 1 ),    ###); # Restriction levels for auto-review/review rights ### Specify user group whose edits need not be reviewed which can be applied to a page protection (?) $wgFlaggedRevsRestrictionLevels = array( 'bureaucrat' ); # Use flag "protection" levels ### We want this to stay false so it applies to all pages by default ### Set to true sets the extension to be applied like a page-protection mechanism, which we don't want $wgFlaggedRevsProtection = false; # Use current templates/files ### No idea... $wgFlaggedRevsHandleIncludes = FR_INCLUDES_CURRENT; # Group permissions for autoconfirmed ### We don't use autoconfirmed group so it is changed to bure $wgGroupPermissions['bureaucrat']['autoreview'] = true; $wgGroupPermissions['sysop']['autoreview'] = false; # WP:FPPR trial quota ###$wgFlaggedRevsProtectQuota = 2000; # Group permissions for bureaucrat's   $wgGroupPermissions['bureaucrat']['review']         = true; $wgGroupPermissions['bureaucrat']['stablesettings'] = true; $wgGroupPermissions['autoconfirmed']['stablesettings'] = false; $wgGroupPermissions['autoconfirmed']['review'] = false; # Use 'reviewer' group ### We don't want this, we just want this to be assigned to bureaucrats (?) ###$wgAddGroups['sysop'][] = 'reviewer'; ###$wgRemoveGroups['sysop'][] = 'reviewer'; # Remove 'editor' group ### This is required because the extension creates "editor" group, which we don't want unset( $wgGroupPermissions['editor'] ); $wgAddGroups['bureaucrat'] = array_diff( $wgAddGroups['bureaucrat'], array( 'editor' ) ); $wgRemoveGroups['bureaucrat'] = array_diff( $wgRemoveGroups['bureaucrat'], array( 'editor' ) );