Closed (fixed)
Project:
Configuration Management
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
24 Jul 2012 at 05:04 UTC
Updated:
8 Aug 2012 at 21:21 UTC
Jump to comment: Most recent file
Comments
Comment #1
dagmarMerged #1698432: More Notice messages on configuration migrate page in this issue.
Comment #2
dagmarHere is the patch for both issues.
Comment #3
GDrupal commentedThe issue was still triggering for me.. I have added some default elements to the component array to avoid the warnings. It seems to be doing the trick for now, but perhaps we need to define exactly the structure of the config.export file and double check if it's consistent in all places.
Comment #4
lucascaro commentedThanks @dagmar and @GDrupal!
If you know how to replicate it in a test it would be awesome to have it and also check if the exported file is correct in those cases. Otherwise we need to manually check the configuration file and mark this RTBC.
Comment #5
lucascaro commentedMarked #1415962: Notice & Warning on configuration settings page as duplicated of this issue.
Comment #6
lucascaro commented#3: 1698432.notices_migrate_page.3.patch queued for re-testing.
Comment #8
dagmarWell, I have included some tests to replicate the warnings.
Also, I think I have founded the problem with the issue described in #3.
Comment #9
GDrupal commentedLooks Amazing! RTBC
Comment #10
lucascaro commentedCommitted, thanks.