Repository CSV import fails when new terms added to Description Statuses in import file
|Google Code Legacy ID:||Tested version:||2.5, 2.6|
Reported via the User forum (2.5) here - reproduced in vagrant qa/2.6.x, 2020-04-13.
In issue #10472 we added support for a repository CSV import. However, currently attempts to add new terms to some of the taxonomy-linked fields causes the import to fail, rather than adding the term and informing the user in the console.
Use the attached test file - it contains the word "Coffee" in the first row's descriptionStatus column, and the second example row has been changed to
fr in the culture column.
Import it with:
php symfony csv:repository-import /path/to/culture-test-example-repositories.csv
- Import fails
- Error in console: "Could not find "Coffee" in description status terms array."
See the attached screenshot, repo-descriptionStatus-import.png
- The term "Coffee" should be created in the Description Statuses taxonomy on import and the user notified in the console log
- The import should not fail due to a new term being added
Note: we should also review other related fields for similar behavior.