EPrints Technical Mailing List Archive
Message: #08829
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] Eprints 3.4.3 RIOXX2 plugin issue
- To: David R Newman <drn@ecs.soton.ac.uk>, "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: Re: [EP-tech] Eprints 3.4.3 RIOXX2 plugin issue
- From: Lee Paton <patonl@cardiff.ac.uk>
- Date: Thu, 13 Jan 2022 13:17:14 +0000
CAUTION: This e-mail originated outside the University of Southampton.
Hi David That’s great – that’s resolved my problem, many thanks The version of the Generic Reporting Framework we’re using is 2.0, upgrading the plugins is next on my to-do list We’re using shibboleth for authentication, would that change how $user is defined? Thanks again Lee From: David R Newman <drn@ecs.soton.ac.uk> Hi Lee, I have not been able to reproduce the same issues as you reported when tying to edit an item. I did initially get some errors in the apache log relating to not having the Generic Reporting Framework plugin installed but this did not give a 500 error in
my web browser and was easily remedied by installing this plugin through the Bazaar.
One issue may be the versions of the RIOXX2 and Generic Reporting Framework plugin you are running. I have just installed the following versions: reports=3.1 rioxx2=1.0.5 Which versions do you have installed? You can check this most easily by going to the /cgi/counter page for your repository in a web browser. Looking at the first line of your errors, it reports a problem with calling isa method on an undefined value on line 8. I have grepped through the code and found that this could relate to some new as of 3.4.3 configuration code that was added to ensure
local passwords are no longer than a certain length, (in this case 200 characters), which was identified as a potential vector of attack. It is possible that in line 8 of lib/cfg.d/user_password_maxlength.pl there is no user defined so this generates this first error message. However, I am not sure how this could have anything to do with the RIOXX2 plugin. My advice would be to modify line
8 of the file from: return unless $user->isa( "EPrints::DataObj::User" ) && $field->type eq "secret"; to: return unless defined $user && $user->isa( "EPrints::DataObj::User" ) && $field->type eq "secret"; And see if that remedies your issue. I am not sure how this trigger could be called without $user (or more generally a dataobj that might be a user) being defined. However, it is the only place I could find the isa method called on line 8 of a file. Regards David Newman On 12/01/2022 16:36, Lee Paton wrote:
|
- Follow-Ups:
- Re: [EP-tech] Eprints 3.4.3 RIOXX2 plugin issue
- From: Lee Paton <patonl@cardiff.ac.uk>
- Re: [EP-tech] Eprints 3.4.3 RIOXX2 plugin issue
- References:
- [EP-tech] Eprints 3.4.3 RIOXX2 plugin issue
- From: Lee Paton <patonl@cardiff.ac.uk>
- Re: [EP-tech] Eprints 3.4.3 RIOXX2 plugin issue
- From: David R Newman <drn@ecs.soton.ac.uk>
- Re: [EP-tech] Eprints 3.4.3 RIOXX2 plugin issue
- From: Lee Paton <patonl@cardiff.ac.uk>
- Re: [EP-tech] Eprints 3.4.3 RIOXX2 plugin issue
- From: Lee Paton <patonl@cardiff.ac.uk>
- [EP-tech] Eprints 3.4.3 RIOXX2 plugin issue
- Prev by Date: Re: [EP-tech] Eprints 3.4.3 RIOXX2 plugin issue
- Next by Date: Re: [EP-tech] Eprints 3.4.3 RIOXX2 plugin issue
- Previous by thread: [EP-tech] Sort view with creators_name and corp_creators
- Index(es):