[MAGNOLIA-7271] Deprecation can't be applied at runtime Created: 01/Mar/18 Updated: 29/Jun/23 |
|
| Status: | Accepted |
| Project: | Magnolia |
| Component/s: | configuration |
| Affects Version/s: | 5.6.2 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Roman Kovařík | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Epic Link: | Easy cloud upgrades | ||||||||||||||||
| Description |
|
Defnition is not reregistered when deprecation is added since its metadata has changed, see 2018-03-01 08:20:53,177 ERROR info.magnolia.config.registry.RegistryMap : Can't register [template] definition [home] with reference id: [travel-demo:pages/home] from module [travel-demo] at [pages/home][template] definition [home] with reference id: [travel-demo:pages/home] from module [travel-demo] at [pages/home] which is deprecated [Since=5.6,Description=dewad] since a definition with the same id travel-demo:pages/home is already registered as [template] definition [home] with reference id: [travel-demo:pages/home] from module [travel-demo] at [pages/home][template] definition [home] with reference id: [travel-demo:pages/home] from module [travel-demo] at [pages/home] which is deprecated [Since=5.6,Description=dewad]. This also means that the actual template is not replaced with new version. |
| Comments |
| Comment by Chuck Aksamit [ 29/Jun/23 ] |
|
I'd like to bump this one. Now that we run projects and deploy light modules often but not the core Magnolia project as often, we are seeing these errors arise in our server logs on each LM deploy. We know they are kinda bogus and the results are that they new code takes precedence as we would expect. It was different when everything is always deployed together because only FE devs would ever see this and we all knew what these were but now anyone with access to server logs and stats can see these errors pile up. Since this is linked to an epic with easy in the name, can we get this prioritized? |