Open xoroz opened 5 years ago
Thanks @xoroz!
We'll take a look and will try to get it up-to-date as soon as possible. Your report is very helpful.
You guys might be interested in reusing the container images I provide for IQSS/dataverse-kubernetes. As long as you provide the necessary env vars and secret files, those are simple to use...
@poikilotherm, we're going to use your images for acceptance/production, @wilkos-dans is working on it now. But the idea to use our current Docker module for the development purposes as it's very easy to build and run Dataverse locally without Kubernetes infrastructure.
@xoroz, I've upgraded Dataverse to the latest version in our 4.15 branch. We've tested already and it seems there are no problems anymore but can you please also test it?
@4tikhonov Thank you for upgrading dataverse-docker to 4.15. I work with @xoroz and we have been testing it. The installation procedure looks ok, but when I go to "My Data", some fields in the graphical interface are not populated correctly (it looks like they are only placeholders), please see the following screenshot: Something similar happens when I try to create a dataset: Again, when I try to manage Dataverse permissions for users:
Thanks a lot for your help!
Thanks a lot, @valentinapasquale! I think some phrases with ??? coming up from missing properties in Bundle.properties file, I'll check that.
I think I've fixed this issue now, please test it again with --no-cache rebuild.
@4tikhonov now it works :) I have used the "master" branch in the end, because I got errors with the "4.15" branch. Did I make something wrong? Are they aligned?
Both branches should be aligned. I'll check for it.
now it works
@valentinapasquale hooray!! 🎉 And thanks for following up on the thread at https://groups.google.com/d/msg/dataverse-community/dsQ6rPOqYIc/iSBUe-1OCQAJ ! 🎉
@4tikhonov heads up that Dataverse 4.15.1 just came out and includes an important fix related to how Dataverse calls into Solr: https://github.com/IQSS/dataverse/releases/tag/v4.15.1
Hello all, same issue is happening on the 4.19 we see the ??? on the login option ???login.signup.blurb???
If it helps, that login blurb was added in Dataverse 4.18 as part of https://github.com/IQSS/dataverse/issues/6170
https://github.com/IQSS/dataverse-kubernetes is up to 4.18.1 so you might not this this problem there.
Sorry if I'm misunderstanding the situation.
@xoroz, I think I understand what's happening. We'll fix it soon.
Any news on the problem, I noticed it also on 4.18
Hi @4tikhonov i just tried with the 4.18.1. same problem on the web interface I see many ?? specially on the Login page and Instution Login pages
Hello, I would like to know if there are any plans to have the latest version 4.15 on docker-compose.
I did try on my end and it is working with some errors.
This was our expierence here at www.iit.it : 1) Replaced all references from postres 9.3 to 9.6 and then I got Right after change postgresql version from 9.3 to 9.6 we had this error: "The data directory was initialized by PostgreSQL version 9.3, which is not compatible with this version 9.6"" Seems we were still missing the correct DB init data and scripts
2)Fix the version downloaded in init.bash Same for the .war file
Force Download version 4.15
wget "https://github.com/IQSS/dataverse/releases/download/v4.15/dvinstall.zip" -O ./postgresql/dvinstall.zip
step2 force download here
wget https://github.com/IQSS/dataverse/releases/download/v4.15/dataverse-4.15.war -O ./dataversedock/dv/deps/dataverse.war inside postgresql testdata we had to get the script
We got the testdata/ from jhove.conf jhoveConfig.xsd and schema.xml https://github.com/IQSS/dataverse/releases/download/v4.15/dvinstall.zip testdata/scripts from git clone --branch v4.15 https://github.com/IQSS/dataverse.git inside dataverse-4.15/scripts I think we need help with the correct Database files ... Still when starting the application we saw the error:
db | ERROR: relation "sequence" does not exist at character 22 db | STATEMENT: SELECT SEQ_NAME FROM SEQUENCE WHERE SEQ_NAME <> SEQ_NAME
"There are current some issues with the menu names showing quotes we are currently testing and will report any more errors."