Steps to reproduce:
- Try to migrate content with not unique keys.
- Add not valid one.
- Check log messages.
Expected result:
All error/notification logs for content with duplicates exist.
Actual result:
No logs for content with duplicates.
Hello!
I got this issue during a migration from a csv file. The file contained a list of articles and one column was for images names. Images were migrated in a separate migration and of course names were not unique. So I skipped rows with used names.
BUT in case when the image was not found, the log message(which was create after first mention) was deleted before skipping.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | drupal-migration_logs-2860125-2.patch | 1.04 KB | OlgaRabodzei |
Comments
Comment #2
OlgaRabodzei commentedI attach the patch
Comment #4
heddnA test demonstrating this would go a long way to getting further along.
Comment #17
mikelutzWe can't do this because prepare row might save a message when it skips, which would then be deleted. Your source plugin is responsible for ensuring unique ids for each row.