[wp-docs] codex spam

[Arlen Beiler]

I believe it might be your settings. Stick this at the end of
localsettings.php and post the output (if you want). It will break the wiki
until you change it back.

echo '$wgGroupPermissions = ' . var_export($wgGroupPermissions,true);
break;

On second thought, don't, because it will tell everyone exactly what they
can and can't do, so use it at your own risk. Here is the output from a
private wiki that I have.

$wgGroupPermissions = array (
  '*' =>
  array (
    'createaccount' => true,
    'read' => true,
    'edit' => false,
    'createpage' => true,
    'createtalk' => true,
    'writeapi' => true,
  ),
  'user' =>
  array (
    'move' => true,
    'move-subpages' => true,
    'move-rootuserpages' => true,
    'read' => true,
    'edit' => true,
    'createpage' => true,
    'createtalk' => true,
    'writeapi' => true,
    'upload' => true,
    'reupload' => true,
    'reupload-shared' => true,
    'minoredit' => true,
    'purge' => true,
    'sendemail' => true,
  ),
  'autoconfirmed' =>
  array (
    'autoconfirmed' => true,
  ),
  'bot' =>
  array (
    'bot' => true,
    'autoconfirmed' => true,
    'nominornewtalk' => true,
    'autopatrol' => true,
    'suppressredirect' => true,
    'apihighlimits' => true,
    'writeapi' => true,
  ),
  'sysop' =>
  array (
    'block' => true,
    'createaccount' => true,
    'delete' => true,
    'bigdelete' => true,
    'deletedhistory' => true,
    'deletedtext' => true,
    'undelete' => true,
    'editinterface' => true,
    'editusercss' => true,
    'edituserjs' => true,
    'import' => true,
    'importupload' => true,
    'move' => true,
    'move-subpages' => true,
    'move-rootuserpages' => true,
    'patrol' => true,
    'autopatrol' => true,
    'protect' => true,
    'proxyunbannable' => true,
    'rollback' => true,
    'trackback' => true,
    'upload' => true,
    'reupload' => true,
    'reupload-shared' => true,
    'unwatchedpages' => true,
    'autoconfirmed' => true,
    'upload_by_url' => true,
    'ipblock-exempt' => true,
    'blockemail' => true,
    'markbotedits' => true,
    'apihighlimits' => true,
    'browsearchive' => true,
    'noratelimit' => true,
    'versiondetail' => true,
    'movefile' => true,
  ),
  'bureaucrat' =>
  array (
    'userrights' => true,
    'noratelimit' => true,
    'override-export-depth' => true,
    'deleterevision' => true,
  ),
  'webmaster' =>
  array (
    'userrights' => true,
  ),
);

On Mon, Nov 8, 2010 at 2:26 PM, Arlen Beiler <arlenbee at gmail.com> wrote:

> What is his username. I want to take a look at the logs.
>
>
> On Mon, Nov 8, 2010 at 2:13 PM, mrmist <listswpdocs at mist.org.uk> wrote:
>
>> In message <AANLkTinYkC53sxU8JS-0_2mKzwO_2JYDqG+FBCrnhvHt at mail.gmail.com<AANLkTinYkC53sxU8JS-0_2mKzwO_2JYDqG%2BFBCrnhvHt at mail.gmail.com>>,
>> Lorelle on WordPress <lorelleonwordpress at gmail.com> writes
>>
>>  I've just tried a gentler approach. I've protected and locked the page
>>> so that only admins can edit it. This presents a couple of problems
>>> but I think we can handle them.
>>>
>>>
>> Just to keep you updated (as I'm sure you all want to hear more of this
>> fascinating saga ;) the page was edited today (same sort of spam
>> attributions), so it looks like the "protect" doesn't actually work.
>>
>> I reverted the page to how it was when the protect was set.
>>
>> --
>> mrmist
>> _______________________________________________
>> wp-docs mailing list
>> wp-docs at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-docs
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.automattic.com/pipermail/wp-docs/attachments/20101108/d18c3d92/attachment-0001.htm>