[MGNLDAM-397] Migration task CleanContentForDamMigrationTask does not handle i18 case. Created: 19/Feb/14  Updated: 04/Mar/14  Resolved: 03/Mar/14

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: 1.2
Fix Version/s: 1.2.3

Type: Bug Priority: Major
Reporter: Magnolia International Assignee: Eric Hechinger
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image001.png    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

See image, when a component is referencing data in the DMS/DAM with i18, only the default lang field is migrated.



 Comments   
Comment by Roman Kovařík [ 24/Feb/14 ]

Reopened:

  1. Binary compatibility:
    The methods in AbstractPropertyValueSearchDamMigrationTask which were part of dam 1.2.2 should stay there, call new methods and be marked as deprecated.
  2. Please choose diffent name for util class (it's same as info.magnolia.templatingkit.migration.util.MigrationUtil)
  3. Could you assign strings in // WHEN in these tests?:
  • info.magnolia.dam.setup.migration.MigrationUtilTest.testIsPropertyNameI18nBased()
  • info.magnolia.dam.setup.migration.MigrationUtilTest.testBuildI18nSuffixPropertyName()
Generated at Mon Feb 12 04:59:25 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.