[MGNLMIGRATION-210] Step Remove template redundancy has a conceptual issue, read the description for more info. Created: 11/Jan/13 Updated: 24/Jan/13 Resolved: 23/Jan/13 |
|
| Status: | Closed |
| Project: | Migration 4.4 to 4.5 (closed) |
| Component/s: | Migration Task |
| Affects Version/s: | 1.2 |
| Fix Version/s: | 1.2.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | Samuel Schmitt | Assignee: | Samuel Schmitt |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
By defintion this step is doing: In this logic we think that a page template is only referenced by one site definition. But this is wrong ! The task can be triggered by the version of a module if the developer knows that the pages templates of its module are only used by one site def. Then this task is helpful to do a kind of cleanup. |
| Comments |
| Comment by Samuel Schmitt [ 15/Jan/13 ] |
|
Initially i wanted to remove the step from the default migration but i dont want to introduce huge change in the migration of STK. |
| Comment by Jan Haderka [ 23/Jan/13 ] |
|
First of all there is a typo in the title that should be fixed and second title doesn't really describe what the issue is. It only described what your solution does. BTW the method called has also typo in the name "...Temlate..". Don't you guys use spellchecker in IDE? |