EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #05896
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] request copy error message
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: Re: [EP-tech] request copy error message
- From: Michael Eadie <Michael.Eadie@glasgow.ac.uk>
- Date: Thu, 1 Sep 2016 15:08:41 +0000
Hi John, Thanks for looking at this - those files are in the 'wrong' place as I was trying to copy existing files out from the perl_lib directory and into /lib to create a new 'request data' plugin (because I didn't to interfere with existing stuff that works in our Publications repo). However I've changed tack after your comments! I've just renamed existing files and kept them in the same structure e.g. /perl_lib/Eprints/Plugin/Screen/Public/RequestCopy.pm >> RequestData.pm /cgi/request_doc >> request_data And then the recollect_summary_page code xml is the same This seems to work. At least I can get to my RequestData screen now with all the relevant parameters and it puts the request into the request table in the db. I'm now getting an error ' this system is currently unable to send email' but I guess this is now a different problem! Cheers Mick -- Mick Eadie +44 (0) 141 330 6294 -----Original Message----- From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of John Salter Sent: 31 August 2016 09:02 To: eprints-tech@ecs.soton.ac.uk Subject: Re: [EP-tech] request copy error message Hi Mick, >From what I can see in the Recollect plugin (http://bazaar.eprints.org/367/) doesn't include the files you list below. The paths to those files look like they're not the default ones that ship with EPrints - so there's some other reason they exist... My hunch is that it's not dealing with an eprintid properly. Does it work when passing it a docid? Cheers, John -----Original Message----- From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Michael Eadie Sent: 26 August 2016 16:07 To: eprints-tech@ecs.soton.ac.uk Subject: [EP-tech] request copy error message Hi list I'm getting this error in EPrints: 'Bad parameters. Do not try and access this script directly.' I'm trying to set up 'request copy' on our research data repository (3.3.12 and using the recollect plugin) Can anyone shed any light? As far as I can see the relevant parts of this plugin are present and correct: /lib/plugin/EPrints/Plugin/Screen/Public/RequestCopy.pm archives/researchdata/cgi/request_doc archives/researchdata/cfg/cfg.d/request_copy.pl and in recollect_summary_page.xml: <epc:set name='docs' expr='$item.documents()'> <epc:if test="length($docs) = 0"> (<a href="{$config{http_cgiurl}}/request_doc?eprintid={eprintid}"><epc:phrase ref="request:button" /></a>) </epc:if> </epc:set> -- Mick Eadie Research Data Management Officer University of Glasgow Tel: +44 (0) 141 330 6294 http://researchdata.gla.ac.uk | www.glasgow.ac.uk/services/datamanagement/ *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech *** Archive: http://www.eprints.org/tech.php/ *** EPrints community wiki: http://wiki.eprints.org/ *** EPrints developers Forum: http://forum.eprints.org/ *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech *** Archive: http://www.eprints.org/tech.php/ *** EPrints community wiki: http://wiki.eprints.org/ *** EPrints developers Forum: http://forum.eprints.org/
- References:
- [EP-tech] request copy error message
- From: Michael Eadie <Michael.Eadie@glasgow.ac.uk>
- Re: [EP-tech] request copy error message
- From: John Salter <J.Salter@leeds.ac.uk>
- [EP-tech] request copy error message
- Prev by Date: Re: [EP-tech] Atom.xsl Patch Submission
- Next by Date: [EP-tech] Altmetrics and Connotea
- Previous by thread: Re: [EP-tech] request copy error message
- Next by thread: Re: [EP-tech] request copy error message
- Index(es):