See my other post, "SSL between Angular and REST" to find out how this was
resolved.
On Wednesday, December 22, 2021 at 4:10:14 PM UTC-6 Glenn G wrote:
> I found the information at the following link, and will continue once I
> have some other things sorted ou
ment.prod.ts
export const environment = {
ui: {
ssl: false,
host: 'localhost',
port: 4000,
nameSpace: '/'
},
rest: {
ssl: true,
host: 'test.ourschool.edu',
port: 443,
nameSpace: '/server',
},
};
On Thursday, December 23, 2021 at 11:32:49 AM
Following the DSpace 7.1 installation guide here,
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace, I am unable to
proceed past step 4.a. When I run "yarn config:check:rest", it produces
this error message:
ERROR connecting to REST API
Error: write EPROTO
I found the information at the following link, and will continue once I
have some other things sorted out.
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues
On Wednesday, December 22, 2021 at 3:30:35 PM UTC-6 Glenn G wrote:
> M
More information from Chrome developer tools:
{"timestamp":"2021-12-22T21:13:29.565+00:00","status":403,"error":"Forbidden","message":"Access
is denied. Invalid CSRF token.","path":"/server/api/eperson/regis
So I finally got this DSpace 7.1 sorta working, but it won't let me log in
through the user interface. If I enter my email address and password, a
pink balloon appears with the message: "Invalid email or password." Chrome
developer tools says, "zone-evergreen.js:2845 POST
I had the same problem at some point. I traced it to the fact that yarn
could not read my environment.prod.ts file, so it was building DSpace with
the default environment values. These include a server at api.dspace.org.
Check the syntax of your environment.prod.ts file, and pay attention to
I'm working on an upgrade from DSpace 6.3 to DSpace 7.1. The base URL
includes a subdirectory, but it doesn't work with DSpace 7.1. When I
browse to https://test.ourschool.edu/uta-ir, I get the basic DSpace 7.1
page, but none of the content, theme or CSS. Chrome developer tools shows
that
gt;> - [dspace]/webapps/xmlui/themes/Mirage2/images
>>>
>>
>> That seemed to do the trick for us.
>>
>> Alex
>>
>>
>> On Monday, 13 January 2020 11:11:12 UTC-5, Glenn G wrote:
>>>
>>> Jolien,
>>>
>>&g
52:25 PM UTC+1, Alex Fletcher wrote:
>>
>> Glenn:
>>
>> I downloaded the orcid_icon.png file that Jolene mentioned earlier and
>> put it here:
>>
>> - [dspace]/webapps/xmlui/themes/Mirage2/images
>>>
>>
>> That seemed to do the trick
:12 AM UTC-6, Glenn G wrote:
>
> Jolien,
>
> Our DSpace installation does not have the path you mentioned. The Mirage2
> directory is located here:
>
> [dspace]/webapps/xmlui/themes/Mirage2
>
> Our [dspace] directory is not literally "dspace". It has the for
you maybe check if the following file exists within the
> install-directory:
>
> webapps/xmlui/themes/Mirage2/images/orcid_icon.png
>
> Thanks!
>
> Best regards,
>
> Jolien
>
> On Tuesday, December 3, 2019 at 12:10:42 AM UTC+1, Glenn G wrote:
>>
>> After ap
After applying the ORCID patch, the functionality my users were most
interested in is missing. The ORCID logo does not appear next to the
author's name, and the name is not clickable, so a list of the author's
publications cannot be retrieved from ORCID as promised. The ability to
search by
Yes, I encountered exactly the same problem. Sorry I don't have a
solution, just wanted to confirm your finding. Possibly something needs to
be added to build.xml, but I have no idea what. -Glenn.
On Tuesday, November 5, 2019 at 2:29:50 AM UTC-6, Muhammad Yousaf wrote:
>
> Hi Everyone,
>
>
Well, I take it back. We're still getting the same error message with the
-r switch. Anyone else figured out how to make it work?
On Wednesday, July 24, 2019 at 11:11:06 AM UTC-5, Glenn G wrote:
>
> Thought I would update this thread in case anyone has the same question.
>
> In
>From the home page of our DSpace 6.3 site, we click Statistics in the
Administrative box. This brings up a page containing a General Overview
and Archive Information. Under that is an Items Viewed section subtitled
"(more than 20 times)". The list of items below ends, somewhat
predictably,
reference, the line that we changed:
org.apache.logging.log4j.Logger;
We changed it to:
org.apache.log4j.Logger;
On Wednesday, June 5, 2019 at 11:00:52 AM UTC-5, Glenn G wrote:
>
> Apologies if this is a dumb question, but how do you apply a patch? We're
> running DSpace 6.3,
We are using DSpace 6.3. This week someone notified me that "View Usage
Statistics" had stopped showing new statistics in January. I think this
resulted from the old GeoLiteCity.dat database being specified in
[dspace]/config/modules/usage-statistics.cfg. As soon as I got the new
I'm trying to install DSpace 6.3 on an Amazon Linux server (kernel 4.14)
running Tomcat 7. Following step 7 in the instructions, where I enter "mvn
package -Dmirage2.on=true", the build fails with the error messages below.
Can anyone suggest a fix?
[ERROR] Failed to execute goal
Suggestions anyone?
On Wednesday, June 5, 2019 at 11:00:52 AM UTC-5, Glenn G wrote:
>
> Apologies if this is a dumb question, but how do you apply a patch? We're
> running DSpace 6.3, and we need to get the CommunityFiliator running with
> the new functionality described in GitHub
Having the same problem after upgrading from 5.5 to 6.3. Tried adding the
link to handlebars 4.0.0, but that doesn't work.
Any new ideas?
Thanks,
Glenn
On Wednesday, October 26, 2016 at 5:04:03 AM UTC-5, Sean Carte wrote:
> Since upgrading to DSpace 6.0, I've noticed that the Lookup button
Never mind. This was due to our solr webapp having a non-default name.
Once we corrected the entry in local.cfg (solr.server =
http://localhost:8080/solr), the links reappeared.
Thanks for your patience,
Glenn
On Thursday, October 11, 2018 at 12:02:10 PM UTC-5, Glenn G wrote:
> We
We're testing an upgrade from DSpace 5.5-SNAPSHOT to 6.3 on a Linux
server. First we upgrade the Postgresql database from 9.2 to 9.6.
Everything is still working. Then we follow the instructions to do the
upgrade. When all steps are completed, the site appears functional.
Graphics, page
23 matches
Mail list logo
