No easily, the idiot* who designed that part of the system didn't put IDs into the triggers, it just makes a list of each trigger function reference for each priority.

https://github.com/eprints/eprints/blob/2d42b2be54004bf3db6881a6d893d39c7a7f909f/perl_lib/EPrints/RepositoryConfig.pm#L96

All I can suggest is, near the end of the cfg.d files (they load alphabetically) remove ALL the triggers from a priority, and reapply just the ones you want. It's a fragile solution.

*I was that idiot, sorry about that.

Is it possible in a local cfg.d script to replace or disable an existing trigger?

 

I’ve realised that, due to non-standard field usage, there are functions that never get triggered for us, so I’d like to replace the existing trigger without hacking the existing plugin module.

 

Thanks,

Alan

 

-- 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 in relation to its secondary activity of credit broking.

*** 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/

-- 
Christopher Gutteridge <totl@soton.ac.uk> 
You should read our team blog at http://blog.soton.ac.uk/webteam/