EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #01892
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Re: saved searches - permission problem
- To: eprints-tech@ecs.soton.ac.uk
- Subject: [EP-tech] Re: saved searches - permission problem
- From: Roland Roth-Steiner <roth-steiner@ulb.tu-darmstadt.de>
- Date: Tue, 23 Apr 2013 15:48:13 +0200
Hello Tim,
Is this related to this bug? http://trac.eprints.org/eprints/ticket/4031
I couldn't make it up by myself. Our previous productive repository ran on eprints v 3.2.3. No CRUD.pm in this version yet.
CRUD.pm seems to have changed a lot since the patch was provided. Could you test the misbehaviour on the latest stable release (3.3.11, which is the one we are running now)?
although I made a saved search public, only the owning user can run it. If not logged in when trying to run the saved search, the Login Screen appears. If I login with the owning user, everything is ok. If I login as another user, an error appears: "You don't have permission to access /id/saved_search/131 on this server."
Thanks a lot Roland -- ....................................... Roland Roth-Steiner M.Sc. Wirtsch.-Inf., Dipl.-Bibl. . Univ.- und Landesbibliothek ... Elektronische Informationsdienste ... Leitung Digitalisierungszentrum ... Fachreferat Wirtschaft . Magdalenenstr. 8, 64289 Darmstadt +49 (0)6151 16-5858 .......................................
- References:
- [EP-tech] Re: saved searches - permission problem
- From: <christian.gutknecht@ub.unibe.ch>
- [EP-tech] Re: saved searches - permission problem
- From: Tim Brody <tdb2@ecs.soton.ac.uk>
- [EP-tech] Re: saved searches - permission problem
- Prev by Date: [EP-tech] OR2013 Early bird registration
- Next by Date: [EP-tech] Re: deposit URL
- Previous by thread: [EP-tech] Re: saved searches - permission problem
- Next by thread: [EP-tech] XML entity error
- Index(es):