[MGNLCT-34] Detect and register newly added content-types at runtime also on 5.6 branch Created: 09/May/18 Updated: 26/Jul/18 Resolved: 24/May/18 |
|
| Status: | Closed |
| Project: | Content Types |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 0.6.1 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Ewa Snopczynska-Sienczylo | Assignee: | Michael Mühlebach |
| Resolution: | Fixed | 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: | |||||||||||||
| Sprint: | Basel 147 | ||||||||||||
| Story Points: | 2 | ||||||||||||
| Description |
|
Removes the need to manually trigger reload of module for registration to happen. This does not cover more sophisticated use-cases like, changes to files. It worked only on 5.5 branch. |
| Comments |
| Comment by Mikaël Geljić [ 22/May/18 ] |
|
esienczylo can you be more specific about what doesn't work "on 5.6 branch" and edit summary and description accordingly? Are you aware of version 0.6? This one specifically removed dependency on the old activation module. It was released back in February, despite version still showing as "unreleased" in Jira (fixing that now). EDIT: Clarified now w/ ilgun that somehow version 0.6 did not branch from the right place in history, and in particular did not include the fix for |