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

Concept mappings: Can't define multiple matches #345

Closed
mgbeyer opened this issue Jul 7, 2015 · 5 comments
Closed

Concept mappings: Can't define multiple matches #345

mgbeyer opened this issue Jul 7, 2015 · 5 comments

Comments

@mgbeyer
Copy link

mgbeyer commented Jul 7, 2015

If you edit a concept and define multiple matches, they are instantly scheduled for deletion after you hit the save button (see screenshots). They'll be gone after publishing the new concept version.
If you just define a single match it will be saved just fine. If you then create a new version of the concept afterwards and define another (additional) match, the first one will be purged right after you hit 'save' (there's also a message telling you it's scheduled for deletion).

So as it seems to me there's only the possibility to create one single match per concept? If this was the case in practice it would be a rather painful limitation. So I wonder if this is actually a bug or a feature?

fireshot screen capture 005 - coin collecting iqvoc - iqvoc_local_en_concepts_coin_collecting_edit_html_published 0
fireshot screen capture 006 - coin collecting iqvoc - iqvoc_local_en_concepts_coin_collecting_html_published 0

@mgbeyer
Copy link
Author

mgbeyer commented Jul 7, 2015

ps: Here's some version info:

iQvoc version:
4.9.0
iQvoc revision
-
RAILS_ENV:
development

@phschaer
Copy link

phschaer commented Jul 8, 2015

Just to add some more background information: When I try to reproduce this issue in version 4.8.2 on http://try.iqvoc.net it works just fine. I can define multiple matches without running into the reported behaviour.

So this might be a problem with 4.9.0...

@mgbeyer
Copy link
Author

mgbeyer commented Jul 13, 2015

I can confirm that. Running Iqvoc 4.8.2 locally works just fine. Must be an 4.9.0 specific issue.

@mjansing
Copy link
Contributor

Thanks for the report. I'll check that.

@mjansing
Copy link
Contributor

Should be fixed with 19a5ba9. I also fixed a bug with job creation for non iqvoc federation sources. Can you confirm that? Feel free to reopen this issue if there are any further problems.

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

No branches or pull requests

3 participants