[MGNLMIGRATION-105] Created component migration scripts: Some areas not detected or incomplete (missing availabe components) Created: 10/Oct/12 Updated: 29/Mar/13 Resolved: 23/Nov/12 |
|
| Status: | Closed |
| Project: | Migration 4.4 to 4.5 (closed) |
| Component/s: | None |
| Affects Version/s: | 1.1.4 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | wolf bubenik | Assignee: | Robert Šiška |
| Resolution: | Outdated | 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 |
|
For each component that has a (new) area, code is created for adding this area to the component configuration. For some areas the list of availableComponents is empty. In some cases the areas are not detected at all even if identical paragraphs in same module have been processed correctly. |
| Comments |
| Comment by wolf bubenik [ 15/Oct/12 ] |
|
I did not find a good example last week. I will add one if the problem still exists in current version (1.1.4). |
| Comment by wolf bubenik [ 18/Oct/12 ] |
|
Example for areas that have not been detected at all:
Identical paragraphs in module that have been processed correctly: 1-size-teaserContainer, 2-size-teaserContainer, 6-size-teaserContainer |
| Comment by wolf bubenik [ 18/Oct/12 ] |
|
Example for detected areas that have no available components:
|
| Comment by Robert Šiška [ 23/Nov/12 ] |
|
ad migros-teaser-management: |
| Comment by Robert Šiška [ 23/Nov/12 ] |
|
ad migros-common-templating: Issue is probably outdated. |