EPrints Technical Mailing List Archive

Message: #06494


< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

Re: [EP-tech] Finding missing components


Spot on both, I hadn’t realised grep was case sensitive (d’oh!) so didn’t find those. Sorted now and my workflow and associated parts now seem to be working dandy! Thanks!

 

From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of John Salter
Sent: 15 May 2017 12:34
To: eprints-tech@ecs.soton.ac.uk
Subject: Re: [EP-tech] Finding missing components

 

Try something like

> grep -r 'TagLite' [EPRINTS_ROOT]/perl_lib [EPRINTS_ROOT]/lib [EPRINTS_ROOT]/archives/[ARCHIVEID]/cfg/

 

(or you could cd into the EPRINTS_ROOT and not include that in the locations to grep within)

 

I suspect there's something like

[EPRINTS_ROOT]/perl_lib/EPrints/Plugin/InputForm/Component/Field/TagLite.pm

that you're missing…

 

Cheers,

John

 

From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Alan.Stiles
Sent: 15 May 2017 11:58
To: eprints-tech@ecs.soton.ac.uk
Subject: Re: [EP-tech] Finding missing components

 

It’s still the exact same error message?

I don’t think it needs anything other than dropping in the same location on the new server as it came from on the old…  Have you grepped for TagLite in [EPRINTS_ROOT]/archives/ARCHIVE_ID/cfg/cfg.d/ on your live box to see whether there’s anything there missing from your new build?

 

From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Andrew Beeken
Sent: 15 May 2017 11:21
To: eprints-tech@ecs.soton.ac.uk
Subject: Re: [EP-tech] Finding missing components

 

Any thoughts on this, folks? I’m likely to find a bunch of these little components that need dragging over as I’m testing my install so any ideas on how to get them running in the new environment would be great.

 

From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Andrew Beeken
Sent: 12 May 2017 10:29
To:
eprints-tech@ecs.soton.ac.uk
Subject: Re: [EP-tech] Finding missing components

 

Hmm, I’ve copied over the Taglite.pm file as well as the live MetaField.pm file, just in case but I’m still getting the error. Does it need initialising anywhere? I’ve reloaded Apache as well.

 

From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Alan.Stiles
Sent: 12 May 2017 09:52
To:
eprints-tech@ecs.soton.ac.uk
Subject: Re: [EP-tech] Finding missing components

 

You should have a metafield definition for TagLite  – probably under perl_lib/EPrints/MetaField…  (off the top of my head)  on your live server that isn’t on the dev one.

Alan

 

From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Andrew Beeken
Sent: 12 May 2017 09:44
To:
eprints-tech@ecs.soton.ac.uk
Subject: [EP-tech] Finding missing components

 

Hello again!

 

So, in my migration I’m taking a piecemeal approach to bringing components over. I’ve found most of what I need so far however I have a few error messages that I know there is a specific way to interpret but I can’t for the life of me remember how. For example:

 

Unknown component type Field::TagLite in

<component type="Field::TagLite" id="c8"><field ref="keywords" input_lookup_url="/cgi/users/lookup/mixed_filesql" input_lookup_params="file=arch_keywords" required="yes"/></component>

 

I’ve found the missing lookup but I’m not sure where to find Field::TagLite. I know there is a way to interpret that command into a location but any pointers would be grand!

 

Andrew


The University of Lincoln, located in the heart of the city of Lincoln, has established an international reputation based on high student satisfaction, excellent graduate employment and world-class research.


The information in this e-mail and any attachments may be confidential. If you have received this email in error please notify the sender immediately and remove it from your system. Do not disclose the contents to another person or take copies.

Email is not secure and may contain viruses. The University of Lincoln makes every effort to ensure email is sent without viruses, but cannot guarantee this and recommends recipients take appropriate precautions.

The University may monitor email traffic data and content in accordance with its policies and English law. Further information can be found at:
http://www.lincoln.ac.uk/legal.

-- The Open University is incorporated by Royal Charter (RC 000391), an exempt charity in England & Wales and a charity registered in Scotland (SC 038302). The Open University is authorised and regulated by the Financial Conduct Authority.