EPrints Technical Mailing List Archive

See the EPrints wiki for instructions on how to join this mailing list and related information.

Message: #05890

< 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

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/