A temporary hack would be to add .* to the titleblacklist and then nobody but users with tboverride will be able to create anything. The other way around is to add it to the closeddb.list. If the second solution is preferred, I can submit a patch.

I think you'd need to create a closed-labs.dblist and add eswiki as the contents.

Can't someone in the developer group lock the db through the special page? http://es.wikipedia.beta.wmflabs.org/wiki/Especial:Usuarios_globales/developer

Yep, locked. Looks like it's stored the lock at /data/project/upload7/wikipedia/es/lock_yBgMBwiR

First time I see Special:LockDB working :D I'll see if I can work the closed-labs.dbilist, if it's still needed. It's just creating the file and adding the project, right?

Change 234594 had a related patch set uploaded (by MarcoAurelio):
Creating closed-labs.dblist and closing eswikibeta

https://gerrit.wikimedia.org/r/234594

In T109157#1584925, @MarcoAurelio wrote:

First time I see Special:LockDB working :D

Yeah, I was kind of surprised it worked in our setup, interesting.

In T109157#1584925, @MarcoAurelio wrote:

I'll see if I can work the closed-labs.dbilist, if it's still needed. It's just creating the file and adding the project, right?

That's certainly the preferred way to do this on an indefinite basis (Special:Lockdb is supposed to be for temporary maintenance), yup.

Actually I have no idea why that works in our setup. We set $wgReadOnlyFile = false;.

Change 234594 merged by jenkins-bot:
Creating closed-labs.dblist and closing es.wikipedia.beta.wmflabs.org

https://gerrit.wikimedia.org/r/234594

Doesn't seem to have taken effect. The closed tag is applied, but it doesn't get the right settings for closed wikis in groupOverrides:

krenair@deployment-bastion:/srv/mediawiki-staging$ git diff
diff --git a/wmf-config/CommonSettings.php b/wmf-config/CommonSettings.php
index 9874348..d15d624 100755
--- a/wmf-config/CommonSettings.php
+++ b/wmf-config/CommonSettings.php
@@ -140,7 +140,7 @@ if ( @filemtime( $filename ) >= filemtime( "$wmfConfigDir/InitialiseSettings.php
 if ( !$globals ) {
        # Get configuration from SiteConfiguration object
        require( "$wmfConfigDir/InitialiseSettings.php" );
-
+}//
        $wikiTags = array();
        foreach ( array( 'private', 'fishbowl', 'special', 'closed', 'flaggedrevs', 'small', 'medium',
                        'large', 'wikimania', 'wikidata', 'wikidataclient', 'visualeditor-default',
@@ -152,7 +152,7 @@ if ( !$globals ) {
                        $wikiTags[] = $tag;
                }
        }
-
+if ( !$globals ) { //
        $dbSuffix = ( $site === 'wikipedia' ) ? 'wiki' : $site;
        $globals = $wgConf->getAll( $wgDBname, $dbSuffix,
                array(

krenair@deployment-bastion:/srv/mediawiki-staging$ mwscript eval.php eswiki
> var_dump( $wikiTags );
array(6) {
  [0]=>
  string(6) "closed"
  [1]=>
  string(5) "large"
  [2]=>
  string(14) "wikidataclient"
  [3]=>
  string(9) "wikipedia"
  [4]=>
  string(15) "arbitraryaccess"
  [5]=>
  string(13) "usagetracking"
}

> var_dump( $groupOverrides );
array(5) {
  ["rollbacker"]=>
  array(2) {
    ["rollback"]=>
    bool(true)
    ["abusefilter-log-detail"]=>
    bool(true)
  }
  ["*"]=>
  array(1) {
    ["patrolmarks"]=>
    bool(true)
  }
  ["autopatrolled"]=>
  array(1) {
    ["autopatrol"]=>
    bool(true)
  }
  ["patroller"]=>
  array(3) {
    ["patrol"]=>
    bool(true)
    ["autopatrol"]=>
    bool(true)
    ["abusefilter-log-detail"]=>
    bool(true)
  }
  ["flood"]=>
  array(1) {
    ["bot"]=>
    bool(true)
  }
}

I figured out the issue. eswiki's own explicit entry in groupOverrides will override the 'closed' tag. Needs the '+' added.

Change 235666 had a related patch set uploaded (by Alex Monk):
Make eswiki groupOverrides inherit overrides from relevant tags

https://gerrit.wikimedia.org/r/235666

Change 235666 merged by jenkins-bot:
Make eswiki groupOverrides inherit overrides from relevant tags

https://gerrit.wikimedia.org/r/235666

Thanks

There are account creations too

(I restored the titleblacklist, which contains ".*", till the problem is fixed, so no one can create new pages)

In T109157#1734261, @hashar wrote:

Please reopen the eswiki on beta cluster. It is used for content translation testing.

From the opening description of the task:

Hello, beta eswiki was used for the ContentTranslation Project, but there was no activity by mebers of this project for over three (or six?) months.

Is there somewhere more active in labs that could be used?

Please note:
It is possible to write at eswiki at the moment, till T115584 is fixed, but I would revert the change as soon as possible (not possible at the moment, I would set up a patch in a few hours)

@Peachey88: simplewiki, enwiki (these are the most actives). But there are others too: http://deployment.wikimedia.beta.wmflabs.org/wiki/Special:SiteMatrix

Can we unlock this wiki for registered users? I need to create some pages for testing the recommendation API: T211397: Recommendation API in beta labs doesn't work.

Hi,

I also want to test the ContentTranslation tool, specially due the bug affecting blocked users from translating.

Change 608249 had a related patch set uploaded (by Krinkle; owner: Krinkle):
[operations/mediawiki-config@master] multiversion: Fix 'closed-labs' reading as 'closed' for static config

https://gerrit.wikimedia.org/r/c/operations/mediawiki-config/ /608249

Change 608249 merged by jenkins-bot:
[operations/mediawiki-config@master] multiversion: Fix 'closed-labs' reading as 'closed' for static config

https://gerrit.wikimedia.org/r/c/operations/mediawiki-config/ /608249

I'm planning to undo this per T306833: Reopen beta eswiki. If the spam becomes a problem, we can figure something out (e.g. limit write access to known IP ranges), although I'm not sure if there's reason to care about spam pages on a beta wiki.