EPrints Technical Mailing List Archive
Message: #03938
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Re: Errors when requesting /id/eprint/$eprintid after 3.3.13 update
- To: eprints-tech@ecs.soton.ac.uk
- Subject: [EP-tech] Re: Errors when requesting /id/eprint/$eprintid after 3.3.13 update
- From: Gunnar Wolf <gwolf@gwolf.org>
- Date: Tue, 17 Feb 2015 11:50:54 -0600
Lizz Jennings dijo [Tue, Feb 17, 2015 at 05:29:03PM +0000]: > No, it's not just you - I just found and solved the same error about half an hour ago! > > If you replace the line 897 with > > if( $self->scope == CRUD_SCOPE_DATAOBJ || $self->scope == CRUD_SCOPE_USER_CONTENTS ) > > that fixed it for me. Right. In my case, I decided to add a check instead of removing it (even if it almost always becomes a null check), and I have: if( ( $self->scope == CRUD_SCOPE_DATAOBJ && $self->{database} && $self->{database}->base_id ne "subject" ) || $self->scope == CRUD_SCOPE_USER_CONTENTS )
- References:
- [EP-tech] Errors when requesting /id/eprint/$eprintid after 3.3.13 update
- From: Gunnar Wolf <gwolf@gwolf.org>
- [EP-tech] Re: Errors when requesting /id/eprint/$eprintid after 3.3.13 update
- From: Lizz Jennings <E.Jennings@bath.ac.uk>
- [EP-tech] Errors when requesting /id/eprint/$eprintid after 3.3.13 update
- Prev by Date: [EP-tech] Re: Errors when requesting /id/eprint/$eprintid after 3.3.13 update
- Next by Date: [EP-tech] show contributor
- Previous by thread: [EP-tech] Re: Errors when requesting /id/eprint/$eprintid after 3.3.13 update
- Next by thread: [EP-tech] Antwort: Re: Errors when requesting /id/eprint/$eprintid after 3.3.13 update
- Index(es):