[EP-tech] solved: perl module update introduced some trouble with entities

th.lauke at arcor.de th.lauke at arcor.de
Tue Dec 1 15:22:13 GMT 2020


CAUTION: This e-mail originated outside the University of Southampton.

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%7C24c488b181644d411e6c08d8960ce67d%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637424329431986432%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=J2YSp%2BbNhhNz7c4nK0oZOkhevPXr4XtS05e9raPJ%2Fe4%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



More information about the Eprints-tech mailing list