It's set here:

https://github.com/eprints/eprints/blob/3.3/perl_lib/EPrints/Apache/Rewrite.pm#L482

$r->set_handlers(PerlResponseHandler => [ 'EPrints::Apache::Template' ] );

If the URL is not a document or EPrint URL, and ends in .html then apache is told to use that handler. See https://perl.apache.org/docs/2.0/user/handlers/http.html#PerlResponseHandler

The term "pin" is short for lynchpin because that was the term for gaps you left in pre-prepared spells to fill them in at the time you cast them, in a roleplay system I was playing when I designed that bit of the system. It's not perfect, but it's not done badly as a solution for web templating.

Hi All,

I've decided to go back and revisit pins to see how they work. Starting with the "main" pin in my repository default template:

<epc:pin ref="page"/>

According to the EPrints wiki Aprints:Apachec:Template.pm is what I want to look at. Going here I can see a sub:

sub handler {

This subroutine does STUFF to some filename and ends with a call to "prepare_page" which I assume prepares the page.

Excuse me if this is really obvious or naive, but what causes "handler" to be called in the first instance? I've done so many greps and searched everywhere. I've even looked at bin/generate_static to see if that gives any clues. The notes in this module indicate that it's ran on server start-up, but does anybody know when "handler" is called? I want to see how the filenames are passed to handler.

Thanks,

James 

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