User warning: The configuration name "backup_migrate.backup_migrate_schedule.daily" does not match the ID "daily_schedule" in Drupal\Core\Config\ConfigInstaller->createConfiguration() (line 345 of core\lib\Drupal\Core\Config\ConfigInstaller.php). 

I see the above warning after enabling the module under Drupal 8.6

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Pasqualle created an issue. See original summary.

couturier’s picture

Did you set up a schedule already, or did you see the warning after simply enabling the module? If you have a schedule configured, try clearing it out or uninstalling the module and re-installing to see if the error goes away.

couturier’s picture

Status: Active » Closed (cannot reproduce)

I'm closing this issue due to non-response from the original poster.

Pasqualle’s picture

Status: Closed (cannot reproduce) » Active

backup_migrate.backup_migrate_schedule.daily.yml
id: daily_schedule

The id in config file must match the part of the file name after the second dot.

couturier’s picture

So you are saying this is a bug that requires a patch? Are you able to contribute?

ikit-claw’s picture

Assigned: Unassigned » ikit-claw

@couturier I can take a look at some of the easier tickets this week. I like this one.

@Pasqualle thanks for reporting the issue if you see anything else let us know.

emb03’s picture

I got this error also. Any patch coming?

ikit-claw’s picture

Sorry @emb03 I got a bit side tracked. I will get one out for this ASAP

ikit-claw’s picture

Could you give me the details of the server or local setup you are getting this error with?

ikit-claw’s picture

Status: Active » Postponed (maintainer needs more info)

I've tried on a couple of different setups now I can't reproduce this. So it must some how be related to local setup perhaps PHP version.

I need the details of the local or server setups so I can reproduce the issue to fix it.

Pasqualle’s picture

Status: Postponed (maintainer needs more info) » Active

The error is from web\core\lib\Drupal\Core\Config\ConfigInstaller.php createConfiguration()

I do not see any condition which would prevent showing this error. Maybe you have E_USER_WARNING suppressed in your php configuration, or error messages set to hidden on /admin/config/development/logging

Even if you can't reproduce, this is a clear bug. Makes also a problem when you are using the config_update module. The config is listed as new.

ikit-claw’s picture

@Pasqualle if I can't reproduce the issue how can I patch / test / commit the change?

I am a maintainer, if you want to make a patch for this I can check nothing breaks and commit it for you?

Else I need to be able to recreate the situation.

Thanks

Pasqualle’s picture

Status: Active » Needs review
FileSize
333 bytes

D8.6 change record: https://www.drupal.org/node/2974112

This patch works for me

riddhi.addweb’s picture

Status: Needs review » Reviewed & tested by the community
FileSize
215.14 KB
44.93 KB
34.06 KB

@Pasqualle, I got the same warning after installing the module,& I checked this patch using simplytest.me. Please refer my attached screenshot for the same.

Zsuffa Dávid’s picture

#13 works for me.
drupal 8.6.1
php 7.2.10
Apache/2.4.34

ikit-claw’s picture

Thanks for verifying I will get it merged in.

Nick Hope’s picture

I had this warning after installing 8.x-4.0 with Drupal 8.6.3 on Acquia Dev Desktop. I then installed 8.x-4.x-dev (updated 26 Oct 2018 at 19:03 UTC) and no longer get the error.

Anonymous’s picture

I'm getting this when running my rebuild script where I'm composer requiring drupal/backup_migrate:4.x-dev after reading this.

The error is:

[warning] The configuration name "backup_migrate.backup_migrate_schedule.daily" does not match the ID "daily_schedule" ConfigInstaller.php:345

NWOM’s picture

#13 works for me. Thanks!

DamienMcKenna’s picture

Version: 8.x-4.0 » 8.x-4.x-dev
DamienMcKenna’s picture

DamienMcKenna’s picture

Status: Reviewed & tested by the community » Fixed

Committed. Thanks.

DamienMcKenna’s picture

Assigned: ikit-claw » Unassigned

Status: Fixed » Closed (fixed)

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