-
Notifications
You must be signed in to change notification settings - Fork 144
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
Can't create thesauri in internationalized Arches 7.6.x #11794
Comments
Hi @tris-ots , Also can you confirm that you have a language in your languages table that corresponds to |
hi @apeters and thanks so much for all your help with this problem. However, when i set the At one point I got this error which suggested that the language code should be
However, when I set both the values in |
I've experienced this issue on installs of Arches 7.6.0 and 7.6.6; after internationalizing Arches (in my case, French and English) I can't create thesauri in the Reference Data Manager.
Sometimes the newly created thesaurus appears in the list of thesauri, sometimes not. However, after this point, no thesauri can be created, viewed or edited. Clicking on any thesauri that appear in the list displays a "Loading..." message in the righthand pane, apparently forever. As far as I can tell, all the above is true for whatever language the RDM is used in (in my case, either https://domainname/en/rdm or https://domainname/fr-fr/rdm).
@apeters kindly suggested that creating a Thesaurus Service Provider with the
fr-fr
language might fix the issue, but unfortunately this didn't work in my case, on either 7.6.0 or 7.6.6.Steps to reproduce:
python manage.py graph publish --update
Expected behavior:
Digging into the system logs, I found that Arches output variations on this message while I was trying to work with the RDM:
The messages had different concept UUIDs (I guess since I was trying to create or interact with multiple thesauri) but always referred to a
KeyError
and to a problem with theget_sparql_providers
function. Obviously this supports Alexei's thought that there's some issue with the SPARQL endpoint.While I was trying to apply Alexei's suggested fix, I also encountered the bug I described in #11793.
The text was updated successfully, but these errors were encountered: