Hi,
I have error 500 in the frontend, checking it seems they keep calling http
and not https, maybe some suggestions to be able to review and know what
the error is to correct.
my setup: ubuntu 20.04, dspace DSpace 7.6
local.cfg ===
dspace.ui.url = https://repository.domain/
Hi Matthias,
Thanks for this information. For the moment I wound up copying over
src/themes/custom/app/forgot-password/ into my theme and
modifying forgot-email.component.html to remove the form and just have some
text with a link to our password reset page. I might dig deeper into it
Dear All,
The author's search in the default setting has an apparent usability issue.
Here is a situation.
Namely, when I type "Surname, Name" (image 1 attached), even when the
corresponding authority is available in Solr, many times it doesn't appear
in the search results at all. However,
I'm trying to update a collection logo in 7.6.
When I add the file to the uploader, nothing happens and I get a Uploading
Collection failed error.
The console also shows a 400 error on the upload and also shows a Syntax
Error - Not valid JSON
--
All messages to this mailing list should
Hi Tomas,
at least I can give you the location where this can be changed in the
source code of the angular-frontend.
There is a component
.../src/app/shared/log-in/methods/password/log-in-password.component.html
that should look like this:
{{"login.form.email" | translate}}
Hi,
I'm currently running DSpace version 7.6.1 and using LDAP
authentication. I'm wondering if there is a method of either removing
the "Have you Forgot your password?" link or being able to change the link
to point to another site.
I saw a related issue
I'm wondering if the content is correct. Looks like you are trying to index
content larger than 32766 but that's coming from the field bi_2_dis_prefix.
Are you sure that the content in that field is correct.
To handle content larger than 32766 you need to change the field type in
the Solr
Hi Michael,
Thank you for this, it worked! My issue is that it is not following the
styling of the other metadata even though I added the classes I found in
the other metadata such as the URI field. I resolved it by manually adding
an inline CSS rule and I don't know if this is the right way
