Problem/Motivation

I often get this during translation import of custom .po files:

 [notice] Translations imported: 0 added, 404 updated, 0 removed.
 [warning] No configuration objects have been updated.

I get no idea if I did something wrong or if that warning could/should be removed ?

Steps to reproduce

Proposed resolution

Fix typo in locale_config_batch_refresh_name() that was introduced in #1905152: Integrate config schema with locale, so shipped configuration is translated.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Issue fork drupal-2957279

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

pguillard created an issue. See original summary.

pguillard’s picture

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

jeroent’s picture

Status: Active » Needs review
ranjith_kumar_k_u’s picture

StatusFileSize
new592 bytes

Re-rolled for 9.4.

Status: Needs review » Needs work

The last submitted patch, 11: 2957279-11.patch, failed testing. View results

rajab natshah’s picture

Having the same issue on install with other languages. rather than the default English selected language.
Have a custom .po file with the profile and modules too.
Trying to import it on the installation steps.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

kristen pol’s picture

I get this regularly when using demo_umami and installing modules.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

kunalkursija’s picture

I am getting this error when enabling a new custom module on Drupal 9.5.10. The site is an old Drupal 8 site that has been upgraded to Drupal 9 a year back & it's a minimal Drupal profile. The steps that I performed were:

  • Created a new custom module directory & the info yml file.
  • Added custom migration yml in config/install directory. (Note: I don't have any other config files in config/install.)
  • In CLI, I did drush en - y custom_module_name and got the notice & warning saying No configuration objects have been updated..
  • Despite the notice & warning, The module gets enabled.

Even after applying the patches, The issue remains.

bennyjos’s picture

I am getting this message when a module is enabled (Drupal 9.5.10)
> [notice] Checked es translation for admin_toolbar.
> [warning] No configuration objects have been updated.
> [notice] Message: No configuration objects have been updated.

Module enabled successfully, despite these notices/warnings

alexpott made their first commit to this issue’s fork.

alexpott’s picture

Status: Needs work » Needs review

This is caused by a typo in locale_config_batch_refresh_name() ... all the back in #1905152: Integrate config schema with locale, so shipped configuration is translated

Posted MR with fix.

chr.fritsch’s picture

Status: Needs review » Reviewed & tested by the community

Nice finding

wim leers’s picture

Title: [warning] No configuration objects have been updated. » "[warning] No configuration objects have been updated."

Wow, nice find indeed 😊

kristen pol’s picture

Yay! Such a simple fix 👏

kunalkursija’s picture

Wow, Great Find. That was quick 🎉

quietone’s picture

Issue summary: View changes

I'm triaging RTBC issues. I read the IS which should have a proposed resolution so reviewers understand the fix. I considered stopping there but this is a bit older and only 26 comments. After reading the comments I have updated the issue summary.

I ran the test only changes and it does fail on checking the count of error messages, not the error message in the IS. I ran the test only version locally and it does indeed fail with a message of "No configuration objects have been updated."

I reviewed the MR and everything if fine there.

Leaving at RTBC.

quietone’s picture

Title: "[warning] No configuration objects have been updated." » Fix typo in locale_config_batch_refresh_name causing "[warning] No configuration objects have been updated."

A more accurate title.

  • quietone committed e7ab9440 on 11.x
    Issue #2957279 by alexpott, pguillard, chr.fritsch, Wim Leers: Fix typo...

  • quietone committed 820c507c on 10.2.x
    Issue #2957279 by alexpott, pguillard, chr.fritsch, Wim Leers: Fix typo...
quietone’s picture

Version: 11.x-dev » 10.2.x-dev
Status: Reviewed & tested by the community » Fixed

Indeed, this is a nice find.

Pushed to 11.x and 10.2.x Thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

murz’s picture

Seems this patch got reverted for some reason?
Cuz now I see this message again with the "warning" severity in Drupal 11.1.8 (and in 10.2.x too): https://git.drupalcode.org/project/drupal/-/blob/11.1.8/core/modules/loc...

function locale_config_batch_finished($success, array $results) {
  if ($success) {
    $configuration = $results['stats']['config'] ?? 0;
    if ($configuration) {
      \Drupal::messenger()->addStatus(t('The configuration was successfully updated. There are %number configuration objects updated.', ['%number' => $configuration]));
      \Drupal::logger('locale')->notice('The configuration was successfully updated. %number configuration objects updated.', ['%number' => $configuration]);
    }
    else {
      \Drupal::messenger()->addStatus(t('No configuration objects have been updated.'));
      \Drupal::logger('locale')->warning('No configuration objects have been updated.');
    }
  }
}