[MGNLMIGRATION-19] Bootstrap config for tabChannels is not in sync with the one contained in the STK Module. Created: 28/Mar/12 Updated: 02/Apr/12 Resolved: 29/Mar/12 |
|
| Status: | Closed |
| Project: | Migration 4.4 to 4.5 (closed) |
| Component/s: | None |
| Affects Version/s: | 1.0.1 |
| Fix Version/s: | 1.1 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Matt Dertinger | Assignee: | Eric Hechinger |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | stk | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Magnolia 4.5.1, STK 2.0.1 |
||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
Hi, Currently, the following bootstrap file seems out of date with the same file that ships with the STK Module. /src/main/resources/auto_bootstraps_after_migration/config/channels/config.modules.standard-templating-kit.dialogs.generic.pages.tabChannels.xml
This file is bootstrapped during the migration process by PostMigrationProcessing.executeImportBootstraps(). Bootstrapping this file causes the wrong configuration to be loaded for the tabChannels dialog. Please let me know if you have any questions. Cheers, |
| Comments |
| Comment by Eric Hechinger [ 29/Mar/12 ] |
|
Ok, this bootstrap file is outdated. |
| Comment by Eric Hechinger [ 29/Mar/12 ] |
|
To solve it locally, you could replace by the one localized in the STK module |
| Comment by Eric Hechinger [ 29/Mar/12 ] |
|
Replacement the outdated bootstrap file (by the one coming from STK). |