function ConfigImportUITest::prepareSiteNameUpdate
4 calls to ConfigImportUITest::prepareSiteNameUpdate()
- ConfigImportUITest::testBatchErrors in core/
modules/ config/ tests/ src/ Functional/ ConfigImportUITest.php  - Tests that errors set in the batch and on the ConfigImporter are merged.
 - ConfigImportUITest::testImport in core/
modules/ config/ tests/ src/ Functional/ ConfigImportUITest.php  - Tests importing configuration.
 - ConfigImportUITest::testImportLock in core/
modules/ config/ tests/ src/ Functional/ ConfigImportUITest.php  - Tests concurrent importing of configuration.
 - ConfigImportUITest::testImportValidation in core/
modules/ config/ tests/ src/ Functional/ ConfigImportUITest.php  - Tests that multiple validation errors are listed on the page.
 
File
- 
              core/
modules/ config/ tests/ src/ Functional/ ConfigImportUITest.php, line 398  
Class
- ConfigImportUITest
 - Tests the user interface for importing configuration.
 
Namespace
Drupal\Tests\config\FunctionalCode
public function prepareSiteNameUpdate($new_site_name) {
  $sync = $this->container
    ->get('config.storage.sync');
  // Create updated configuration object.
  $config_data = $this->config('system.site')
    ->get();
  $config_data['name'] = $new_site_name;
  $sync->write('system.site', $config_data);
}
Buggy or inaccurate documentation? Please file an issue. Need support? Need help programming? Connect with the Drupal community.