Closed (fixed)
Project:
Drupal core
Version:
10.2.x-dev
Component:
locale.module
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
30 Mar 2018 at 10:13 UTC
Updated:
16 Jun 2025 at 10:00 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
pguillard commentedComment #10
jeroentComment #11
ranjith_kumar_k_u commentedRe-rolled for 9.4.
Comment #13
rajab natshahHaving the same issue on install with other languages. rather than the default English selected language.
Have a custom
.pofile with the profile and modules too.Trying to import it on the installation steps.
Comment #16
kristen polI get this regularly when using
demo_umamiand installing modules.Comment #18
kunalkursija commentedI 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:
No configuration objects have been updated..Even after applying the patches, The issue remains.
Comment #19
bennyjos commentedI 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
Comment #22
alexpottThis 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.
Comment #23
chr.fritschNice finding
Comment #24
wim leersWow, nice find indeed 😊
Comment #25
kristen polYay! Such a simple fix 👏
Comment #26
kunalkursija commentedWow, Great Find. That was quick 🎉
Comment #27
quietone commentedI'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.
Comment #28
quietone commentedA more accurate title.
Comment #31
quietone commentedIndeed, this is a nice find.
Pushed to 11.x and 10.2.x Thanks!
Comment #34
murzSeems 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...