[MAGNOLIA-7090] Error message when changing a block definition in a light module Created: 10/Jul/17 Updated: 10/Jul/17 |
|
| Status: | Open |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 5.5.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Description |
|
When I change the definition of a block which resides in a light module at runtime, I get this error message. 2017-07-10 14:22:54,379 INFO info.magnolia.dirwatch.DirectoryWatcher : File resource modified at [/Users/czimmermann/demos/content-editor-5/light-modules/stories-demo/blocks/location.yaml] 2017-07-10 14:22:54,391 ERROR info.magnolia.config.registry.RegistryMap : Can't register [block] definition [location] with reference id: [location] from module [stories-demo] at [location] since a definition with the same id location is already registered as [block] definition [location] with reference id: [location] from module [stories-demo] at [location]. 2017-07-10 14:22:54,392 INFO agnolia.config.source.yaml.YamlConfigurationSource: Registered definition from YAML file [/stories-demo/blocks/location.yaml]: [block] definition [location] with reference id: [location] from module [stories-demo] at [location] In this case, the change is however properly picked up. When I tried previously (I was using "blockClass" instead of "class" for accident) then I was having trouble fixing it - it seemed like it was not loading the changes. But perhaps it was user error at that point. |