EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #08385
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] solved: perl module update introduced some trouble with entities
- To: "th.lauke@arcor.de" <th.lauke@arcor.de>
- Subject: Re: [EP-tech] solved: perl module update introduced some trouble with entities
- From: John Salter <J.Salter@leeds.ac.uk>
- Date: Tue, 1 Dec 2020 16:11:31 +0000
CAUTION: This e-mail originated outside the University of Southampton. Good work everyone - the collective EPrints brain is strong (and long - hello Chris!) today! :) -----Original Message----- From: th.lauke@arcor.de [mailto:th.lauke@arcor.de] Sent: 01 December 2020 15:22 To: John Salter <J.Salter@leeds.ac.uk> Cc: eprints-tech@ecs.soton.ac.uk; martin.braendle@uzh.ch; David R Newman <drn@ecs.soton.ac.uk> Subject: solved: [EP-tech] perl module update introduced some trouble with entities Hi John, > This outlines the issue, and possible resolution: https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Feprints%2Feprints%2Fissues%2F511&data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7C163502b122264dd7b33708d89613c804%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637424358984900804%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Ukb6InFAZtL42Tg6dgw8fuC4npCLaCaqu7DX2M9l%2BMg%3D&reserved=0 that (in combination with a helpful `grep -R expand_entities *` in 3.4.2) was the trick :) > already has an entities.dtd in lib/ and is already used ... yes, when it is explicitly enabled ... > EPrints 3.4_2 has the patch applied for these issues ... unfortunately, I have to apply that fix for 3.4.1 ... > there should be an entities.dtd file in [eprints_root]/lib/, > maybe this is missing or entries are missing in it? no, but due to new standard ignored :( > Also a phrase file should mention that in the > <!DOCTYPE phrases SYSTEM "entities.dtd"> > definition right at the beginning after the XML declaration. everything in place and working until update ... but now again :-) Many thanks for your assistance Thomas
- Follow-Ups:
- Re: [EP-tech] solved: perl module update introduced some trouble with entities
- From: John Salter <J.Salter@leeds.ac.uk>
- Re: [EP-tech] solved: perl module update introduced some trouble with entities
- References:
- Re: [EP-tech] eprints integration with office365 SMTP
- From: <th.lauke@arcor.de>
- [EP-tech] misconfigured or failed upgrade to 3.4.1?
- From: <th.lauke@arcor.de>
- [EP-tech] perl module update introduced some trouble with entities
- From: <th.lauke@arcor.de>
- Re: [EP-tech] perl module update introduced some trouble with entities
- From: David R Newman <drn@ecs.soton.ac.uk>
- [EP-tech] Antwort: Re: perl module update introduced some trouble with entities
- From: <martin.braendle@uzh.ch>
- [EP-tech] Antwort: Re: Antwort: Re: perl module update introduced some trouble with entities
- From: <martin.braendle@uzh.ch>
- [EP-tech] solved: perl module update introduced some trouble with entities
- From: <th.lauke@arcor.de>
- Re: [EP-tech] solved: perl module update introduced some trouble with entities
- From: John Salter <J.Salter@leeds.ac.uk>
- Re: [EP-tech] eprints integration with office365 SMTP
- Prev by Date: [EP-tech] solved: perl module update introduced some trouble with entities
- Next by Date: Re: [EP-tech] Antwort: Re: Antwort: Re: perl module update introduced some trouble with entities
- Previous by thread: [EP-tech] EPrints/CRIS
- Next by thread: [EP-tech] DOI handling in orcid_support_advance
- Index(es):