Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Thesaurus import glitches #7170

Open
txau opened this issue Aug 30, 2024 · 1 comment
Open

Thesaurus import glitches #7170

txau opened this issue Aug 30, 2024 · 1 comment

Comments

@txau
Copy link
Collaborator

txau commented Aug 30, 2024

Two glitches depending on the backend:

  1. When importing, if the thesaurus does not contain items in the current UI language, the import fails. It should fallback to using the CSV language for all languages.
  2. Moreover, after a failed attempt at importing, it won't allow to re-import the corrected CSV because despite the failed import the thesaurus is created and it is detecting the new import as a new creation, giving a uniqueName error. Either not save the thesaurus, or properly update the front-end so it becomes a saved thesaurus and the operation becomes an update instead of a creation.
@txau txau added the Bug 🐞 label Aug 30, 2024
@aphilop aphilop added this to the Thesauri milestone Sep 3, 2024
@RafaPolit
Copy link
Member

Current UI language should have no influence in what is being imported. The import thesaurus flow should just take into account the CSV contents. The only thing that could impact is the default language configured, but nothing else. Can you provide de CSV being imported?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants