[MGNLADMLEG-44] Make sure configuration between migrated and fresh instance is the same Created: 14/Nov/13  Updated: 20/Nov/13  Resolved: 15/Nov/13

Status: Closed
Project: Admininterface Legacy 4.x (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 5.2

Type: Bug Priority: Neutral
Reporter: Roman Kovařík Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLADMLEG-40 remove unused bootstrap files Sub-task Closed Roman Kovařík  
MGNLADMLEG-37 clean up configuration on migration f... Sub-task Closed Roman Kovařík  
Template:
Acceptance criteria:
Empty
Epic Link: Enable 4.5 to 5.x upgrade
Sprint: 5.2-rc2

 Description   
  • fresh vs migrated instance contains:
    • controls: fckEdit,
    • pages: configuration, repositoryBrowser, users
    • menu/tools/migrationTool ( fix for this difference doesn't go into 5.2, see MAGNOLIA-5460)
  • migrated vs fresh instance contains:
    • virtualURIMapping:
      • adminCentral,
      • magnoliaToAdminCentral

diff report: http://hudson.magnolia-cms.com/view/X/job/magnolia-4-5-migration_with_integration_tests/ws/magnolia-migration-integration/diff-reports/modules.adminInterface.html ( is not recent until we integrate the latest changes to master)


Generated at Sun Feb 11 23:09:02 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.