https://wiki.eprints.org/w/api.php?action=feedcontributions&user=Neilmarj&feedformat=atomEPrints Documentation - User contributions [en-gb]2024-03-29T07:28:53ZUser contributionsMediaWiki 1.31.8https://wiki.eprints.org/w/index.php?title=LDAP&diff=2624LDAP2006-12-19T10:03:17Z<p>Neilmarj: </p>
<hr />
<div>==Introduction==<br />
<br />
I am hoping that someone will add to this document regarding the importing of users. I decided that importing all users from my LDAP repository was not a good idea, I run Samba and an import would mean setting up 75 computers with access to eprints. I now create each user that requires access and use LDAP for authentication. This means that my users still only need to remember one password.<br />
<br />
The recommendation for Eprints is not to allow users to alter email and passwords, as these changes are not at present written back to the LDAP database.<br />
<br />
==LDAP Configuration==<br />
<br />
All changes for LDAP authentication can be made in a single file, the file contains useful notes on configuration. Here is an example from my site, I have configured a standard Samba Domain using LDAP for authentication, if you have similar then this config may work for you :<br />
<br />
Edit the file :<br />
<br />
vi /var/lib/eprints3/archives/yourarchivename/cfg/cfg.d/user_login.pl<br />
<br />
# This function allows you to override the default username/password<br />
# authentication. For example, you could apply different authentication rules to <br />
# different types of user.<br />
#<br />
# Example: LDAP Authentication (Quick Start)<br />
#<br />
# Tip: use the test script to determine your LDAP parameters first!<br />
# Tip: remove the set-password priviledge from users and editors in<br />
# user_roles.pl. Also consider removing edit-own-record and <br />
# change-email.<br />
#<br />
$c->{check_user_password} = sub {<br />
my( $session, $username, $password ) = @_;<br />
my $user = EPrints::DataObj::User::user_with_username( $session, $username );<br />
return 0 unless $user;<br />
my $user_type = $user->get_type;<br />
if( $user_type eq "admin" )<br />
{<br />
# internal authentication for "admin" type<br />
# return EPrints::Apache::Login::valid_login( $session, $username, $password );<br />
return $session->get_database->valid_login( $username, $password );<br />
}<br />
# LDAP authentication for "user" and "editor" types<br />
#<br />
# LDAP hostname (and port if not the default)<br />
my $ldap_host = "ldap.yourdomain.ac.uk";<br />
# #my $ldap_host = "ldap.host.name:1234";<br />
# #my $ldap_host = "ldaps://ldap.host.name"; # if server supports LDAPS<br />
#<br />
# Distinguished name for this user<br />
# The distinguished name is a unique name for an LDAP entry.<br />
# e.g. "cn=John Smith, ou=staff, dc=eprints, dc=org"<br />
# You will need to derive this from the username or user metadata<br />
my $ldap_dn = "uid=$username,ou=People,dc=yourdomain,dc=ac,dc=uk";<br />
#<br />
use Net::LDAP; # IO::Socket::SSL also required<br />
#<br />
my $ldap = Net::LDAP->new ( $ldap_host, version => 3 );<br />
unless( $ldap )<br />
{<br />
print STDERR "LDAP error: $@\n";<br />
return 0;<br />
}<br />
#<br />
# Start secure connection (not needed if using LDAPS)<br />
my $ssl = $ldap->start_tls( sslversion => "sslv3" );<br />
if( $ssl->code() )<br />
{<br />
print STDERR "LDAP SSL error: " . $ssl->error() . "\n";<br />
return 0;<br />
}<br />
# Check password<br />
my $mesg = $ldap->bind( $ldap_dn, password => $password );<br />
if( $mesg->code() )<br />
{<br />
return 0;<br />
}<br />
return 1;<br />
}<br />
# Advanced LDAP Configuration<br />
#<br />
# 1. It is also possible to define additional user types, each with a different<br />
# authentication mechanism. For example, you could keep the default user, <br />
# editor and admin types and add ldapuser, ldapeditor and ldapadmin types with<br />
# LDAP authentication - this would suit an arrangement where internal staff are <br />
# authenticated against the LDAP server but user accounts can still be granted <br />
# to external users.<br />
#<br />
# 2. Sometimes the distinguished name of the user is not computable from the <br />
# username. You may need to use values from the user metadata (e.g. name_given,<br />
# name_family):<br />
#<br />
# my $name = $user->get_value( "name" );<br />
# my $ldap_dn = $name->{family} . ", " . $name->{given} .", ou=yourorg, dc=yourdomain";<br />
#<br />
# or perform an LDAP lookup to determine it (more complicated):<br />
#<br />
# my $base = "ou=yourorg, dc=yourdomain";<br />
# my $result = $ldap->search (<br />
# base => "$base",<br />
# scope => "sub",<br />
# filter => "cn=$username",<br />
# attrs => ['DN'],<br />
# sizelimit=>1<br />
# );<br />
#<br />
# my $entr = $result->pop_entry;<br />
# unless( defined $entr )<br />
# {<br />
# return 0;<br />
# }<br />
# my $ldap_dn = $entr->dn<br />
#<br />
# Alternatively, you could store the distinguished name as part of the user <br />
# metadata when the user account is imported print STDERR "LDAP SSL error: " . $ssl->error() . "\n";<br />
<br />
After editing restart Apache.<br />
<br />
==LDAP and User Roles==<br />
<br />
It is recommended that certain user rights are removed when using LDAP for login. The user should not be allowed to change their password or their email address. It is also suggested that the user not be allowed to edit their profile, however I have found certain fields that I would like the user to edit. To set the rights edit the file : <br />
<br />
vi /var/lib/eprints3/archives/yourarchivename/cfg/cfg.d/user_roles.pl<br />
<br />
######################################################################<br />
#<br />
# User Roles<br />
#<br />
# Here you can configure which different types of user are <br />
# parts of the system they are allowed to use.<br />
#<br />
######################################################################<br />
$c->{user_roles}->{user} = [qw/<br />
general<br />
edit-own-record<br />
saved-searches<br />
deposit<br />
/],<br />
$c->{user_roles}->{editor} = [qw/<br />
general<br />
edit-own-record<br />
saved-searches<br />
deposit<br />
editor<br />
view-status<br />
staff-view<br />
/],<br />
$c->{user_roles}->{admin} = [qw/<br />
general<br />
edit-own-record<br />
saved-searches<br />
set-password<br />
deposit<br />
change-email<br />
editor<br />
view-status<br />
staff-view<br />
admin<br />
/],<br />
#$c->{user_roles}->{minuser} = [qw/<br />
# saved-searches<br />
# set-password<br />
# change-email<br />
# change-user<br />
# no_edit_own_record<br />
# lock-username-to-email<br />
#/];<br />
<br />
After editing restart Apache.<br />
<br />
==LDAP Import==<br />
<br />
This is where I hope someone else may help!</div>Neilmarjhttps://wiki.eprints.org/w/index.php?title=LDAP&diff=2623LDAP2006-12-19T09:33:55Z<p>Neilmarj: </p>
<hr />
<div>==Introduction==<br />
<br />
I am hoping that someone will add to this document regarding the importing of users. I decided that importing all users from my LDAP repository was not a good idea, I run Samba and an import would mean setting up 75 computers with access to eprints. I now create each user that requires access and use LDAP for authentication. This means that my users still only need to remember one password.<br />
<br />
The recommendation for Eprints is not to allow users to alter email and passwords, as these changes are not at present written back to the LDAP database.<br />
<br />
==LDAP Configuration==<br />
<br />
All changes for LDAP authentication can be made in a single file, the file contains useful notes on configuration. Here is an example from my site, I have configured a standard Samba Domain using LDAP for authentication, if you have similar then this config may work for you :<br />
<br />
Edit the file :<br />
<br />
vi /var/lib/eprints3/archives/yourarchivename/cfg/cfg.d/user_login.pl<br />
<br />
# This function allows you to override the default username/password<br />
# authentication. For example, you could apply different authentication rules to <br />
# different types of user.<br />
#<br />
# Example: LDAP Authentication (Quick Start)<br />
#<br />
# Tip: use the test script to determine your LDAP parameters first!<br />
# Tip: remove the set-password priviledge from users and editors in<br />
# user_roles.pl. Also consider removing edit-own-record and <br />
# change-email.<br />
#<br />
$c->{check_user_password} = sub {<br />
my( $session, $username, $password ) = @_;<br />
my $user = EPrints::DataObj::User::user_with_username( $session, $username );<br />
return 0 unless $user;<br />
my $user_type = $user->get_type;<br />
if( $user_type eq "admin" )<br />
{<br />
# internal authentication for "admin" type<br />
# return EPrints::Apache::Login::valid_login( $session, $username, $password );<br />
return $session->get_database->valid_login( $username, $password );<br />
}<br />
# LDAP authentication for "user" and "editor" types<br />
#<br />
# LDAP hostname (and port if not the default)<br />
my $ldap_host = "ldap.yourdomain.ac.uk";<br />
# #my $ldap_host = "ldap.host.name:1234";<br />
# #my $ldap_host = "ldaps://ldap.host.name"; # if server supports LDAPS<br />
#<br />
# Distinguished name for this user<br />
# The distinguished name is a unique name for an LDAP entry.<br />
# e.g. "cn=John Smith, ou=staff, dc=eprints, dc=org"<br />
# You will need to derive this from the username or user metadata<br />
my $ldap_dn = "uid=$username,ou=People,dc=yourdomain,dc=ac,dc=uk";<br />
#<br />
use Net::LDAP; # IO::Socket::SSL also required<br />
#<br />
my $ldap = Net::LDAP->new ( $ldap_host, version => 3 );<br />
unless( $ldap )<br />
{<br />
print STDERR "LDAP error: $@\n";<br />
return 0;<br />
}<br />
#<br />
# Start secure connection (not needed if using LDAPS)<br />
my $ssl = $ldap->start_tls( sslversion => "sslv3" );<br />
if( $ssl->code() )<br />
{<br />
print STDERR "LDAP SSL error: " . $ssl->error() . "\n";<br />
return 0;<br />
}<br />
# Check password<br />
my $mesg = $ldap->bind( $ldap_dn, password => $password );<br />
if( $mesg->code() )<br />
{<br />
return 0;<br />
}<br />
return 1;<br />
}<br />
# Advanced LDAP Configuration<br />
#<br />
# 1. It is also possible to define additional user types, each with a different<br />
# authentication mechanism. For example, you could keep the default user, <br />
# editor and admin types and add ldapuser, ldapeditor and ldapadmin types with<br />
# LDAP authentication - this would suit an arrangement where internal staff are <br />
# authenticated against the LDAP server but user accounts can still be granted <br />
# to external users.<br />
#<br />
# 2. Sometimes the distinguished name of the user is not computable from the <br />
# username. You may need to use values from the user metadata (e.g. name_given,<br />
# name_family):<br />
#<br />
# my $name = $user->get_value( "name" );<br />
# my $ldap_dn = $name->{family} . ", " . $name->{given} .", ou=yourorg, dc=yourdomain";<br />
#<br />
# or perform an LDAP lookup to determine it (more complicated):<br />
#<br />
# my $base = "ou=yourorg, dc=yourdomain";<br />
# my $result = $ldap->search (<br />
# base => "$base",<br />
# scope => "sub",<br />
# filter => "cn=$username",<br />
# attrs => ['DN'],<br />
# sizelimit=>1<br />
# );<br />
#<br />
# my $entr = $result->pop_entry;<br />
# unless( defined $entr )<br />
# {<br />
# return 0;<br />
# }<br />
# my $ldap_dn = $entr->dn<br />
#<br />
# Alternatively, you could store the distinguished name as part of the user <br />
# metadata when the user account is imported print STDERR "LDAP SSL error: " . $ssl->error() . "\n";<br />
<br />
==LDAP Import==<br />
<br />
This is where I hope someone else may help!</div>Neilmarjhttps://wiki.eprints.org/w/index.php?title=GUI_Submission_with_no_Documents&diff=2620GUI Submission with no Documents2006-12-19T09:00:59Z<p>Neilmarj: </p>
<hr />
<div>==Submitting with no documents==<br />
<br />
I allow this as we may be adding documents in later after the information.<br />
<br />
To allow a submission without a document, edit the file;<br />
<br />
vi /var/lib/eprints3/archives/yourarchivename/cfg/cfg.d/document_upload.pl<br />
<br />
And change the lines;<br />
<br />
$c->{required_formats} =<br />
[<br />
"text/html",<br />
"application/pdf",<br />
"application/postscript",<br />
"text/plain"<br />
];<br />
<br />
<br />
To :<br />
<br />
$c->{required_formats} =<br />
[<br />
# "text/html",<br />
# "application/pdf",<br />
# "application/postscript",<br />
# "text/plain"<br />
];</div>Neilmarjhttps://wiki.eprints.org/w/index.php?title=GUI_Submission_with_no_Documents&diff=2619GUI Submission with no Documents2006-12-19T09:00:42Z<p>Neilmarj: </p>
<hr />
<div>==Submitting with no documents==<br />
<br />
I allow this as we may be adding documents in later after the information.<br />
<br />
To allow a submission without a document, edit the file;<br />
<br />
vi /var/lib/eprints3/archives/yourarchivename/cfg/cfg.d/document_upload.pl<br />
<br />
And change the lines;<br />
<br />
$c->{required_formats} =<br />
[<br />
"text/html",<br />
"application/pdf",<br />
"application/postscript",<br />
"text/plain"<br />
];<br />
<br />
<br />
To :<br />
<br />
$c->{required_formats} =<br />
[<br />
# "text/html",<br />
# "application/pdf",<br />
# "application/postscript",<br />
# "text/plain"<br />
];</div>Neilmarjhttps://wiki.eprints.org/w/index.php?title=Web_Interface_Style_and_Images&diff=2618Web Interface Style and Images2006-12-19T08:55:53Z<p>Neilmarj: </p>
<hr />
<div>==Style Sheet Changes==<br />
<br />
All changes to style sheet setting should be made in the directory /var/lib/eprints3/archives/yourarchivename/cfg/static/style/auto, and updated using the generate_static command. Changes made in the html directory will be overwritten.<br />
<br />
Style sheets are processed alphabetically, eprints has a local stlye sheet setup called zzz_local.css, any changes can be made in this file, and settings from previous css files will be over writen with values in this file. I use the EditCSS function in Firefox to configure my stlye sheets and copy the modifications directly into this file.<br />
<br />
When modifications are completed, as the user apache execute;<br />
<br />
/var/lib/eprints3/bin/generate_static yourarchivename<br />
<br />
==Image Changes==<br />
<br />
Here's where I cheat! I have taken the original files and changed the colour re-saving as the original file name. This can be a little confusing as some of the files contain the colour in the title. Changed files should be saved into the directory : /var/lib/eprints3/archives/yourarchivename/cfg/static/style/images, changes made in the html directory will be overwritten by the generate_static command.<br />
<br />
The Site Logo can be replaced be overwritting the sitelogo.gif in /var/lib/eprints3/archives/yourarchivename/cfg/static/images/sitelogo.gif<br />
<br />
Copy edited images to above directories, as user apache run the command;<br />
<br />
/var/lib/eprints3/bin/generate_static yourarchivename<br />
<br />
Images will now be copied into the html directory.</div>Neilmarjhttps://wiki.eprints.org/w/index.php?title=Web_Interface_Style_and_Images&diff=2617Web Interface Style and Images2006-12-19T08:51:56Z<p>Neilmarj: </p>
<hr />
<div>==Style Sheet Changes==<br />
<br />
All changes to style sheet setting should be made in the directory /var/lib/eprints3/archives/yourarchivename/cfg/static/style/auto, and updated using the generate_static command. Changes made in the html directory will be overwritten.<br />
<br />
Style sheets are processed alphabetically, eprints has a local stlye sheet setup called zzz_local.css, any changes can be made in this file, and settings from previous css files will be over writen with values in this file. I use the EditCSS function in Firefox to configure my stlye sheets and copy the modifications directly into this file.<br />
<br />
When modifications are completed, as the user apache execute;<br />
<br />
/var/lib/eprints3/bin/generate_static yourarchivename<br />
<br />
==Image Changes==<br />
<br />
Here's where I cheat! I have taken the original files and changed the colour re-saving as the original file name. This can be a little confusing as some of the files contain the colour in the title. Changed files should be saved into the directory : /var/lib/eprints3/archives/yourarchivename/cfg/static/style/images, changes made in the html directory will be overwritten by the generate_static command.<br />
<br />
Copy edited images to above directory, as user apache run the command;<br />
<br />
/var/lib/eprints3/bin/generate_static yourarchivename<br />
<br />
Images will now be copied into the html directory.</div>Neilmarjhttps://wiki.eprints.org/w/index.php?title=Adding_a_link_to_the_Front_Page&diff=2600Adding a link to the Front Page2006-12-14T09:53:48Z<p>Neilmarj: </p>
<hr />
<div>==Adding a Link to the Front Page==<br />
<br />
===Top Menu===<br />
<br />
To add a link to the top menu you must edit the default.xml file in the configurtion directory.<br />
<br />
vi /var/lib/eprints3/archives/yourarchivename/cfg/lang/en/templates/default.xml<br />
<br />
I have added a link to Browse by Person.<br />
<br />
<nowiki><ul class="ep_tm_menu"><li><a href="{$config{frontpage}}">Home</a></li><br />
<li><a href="{$config{base_url}}/information.html">About</a></li><br />
<li><a href="{$config{base_url}}/view/year">Browse by Year</a></li><br />
<li><a href="{$config{base_url}}/view/subjects">Browse by Subject</a></li><br />
<li><a href="{$config{base_url}}/view/people">Browse by Person</a></li></ul></nowiki><br />
<br />
After editing, as the apache user run the command;<br />
<br />
/var/lib/eprints3/bin/generate_static yourarchivename<br />
<br />
===Editing the Main Menu===<br />
<br />
To add a new menu, or edit a link in the main menu you must edit the index.xpage file :<br />
<br />
vi /var/lib/eprints3/archives/yourarchivename/cfg/lang/en/static/index.xpage<br />
<br />
I have changed the Browse link to point at all views :<br />
<br />
<nowiki><div class="ep_toolbox"><div class="ep_toolbox_content" ><br />
<a href="{$config{base_url}}/view/">Browse Repository</a><br /><br /><br />
Browse the items in the repository by subject.<br />
</div></div></nowiki><br />
<br />
<br />
After editing, as the apache user run the command;<br />
<br />
/var/lib/eprints3/bin/generate_static yourarchivename</div>Neilmarjhttps://wiki.eprints.org/w/index.php?title=Adding_a_link_to_the_Front_Page&diff=2599Adding a link to the Front Page2006-12-14T09:52:43Z<p>Neilmarj: </p>
<hr />
<div>==Adding a Link to the Front Page==<br />
<br />
===Top Menu===<br />
<br />
To add a link to the top menu you must edit the default.xml file in the configurtion directory.<br />
<br />
vi /var/lib/eprints3/archives/yourarchivename/cfg/lang/en/templates/default.xml<br />
<br />
I have added a link to Browse by Person.<br />
<br />
<ul class="ep_tm_menu"><li><a href="{$config{frontpage}}">Home</a></li><br />
<li><a href="{$config{base_url}}/information.html">About</a></li><br />
<li><a href="{$config{base_url}}/view/year">Browse by Year</a></li><br />
<li><a href="{$config{base_url}}/view/subjects">Browse by Subject</a></li><br />
<li><a href="{$config{base_url}}/view/people">Browse by Person</a></li></ul><br />
<br />
After editing, as the apache user run the command;<br />
<br />
/var/lib/eprints3/bin/generate_static yourarchivename<br />
<br />
===Editing the Main Menu===<br />
<br />
To add a new menu, or edit a link in the main menu you must edit the index.xpage file :<br />
<br />
vi /var/lib/eprints3/archives/yourarchivename/cfg/lang/en/static/index.xpage<br />
<br />
I have changed the Browse link to point at all views :<br />
<br />
<div class="ep_toolbox"><div class="ep_toolbox_content" ><br />
<a href="{$config{base_url}}/view/">Browse Repository</a><br /><br /><br />
Browse the items in the repository by subject.<br />
</div></div><br />
<br />
<br />
After editing, as the apache user run the command;<br />
<br />
/var/lib/eprints3/bin/generate_static yourarchivename</div>Neilmarjhttps://wiki.eprints.org/w/index.php?title=Browse_By_Person&diff=2595Browse By Person2006-12-14T09:30:05Z<p>Neilmarj: /* Views by Person */</p>
<hr />
<div>==Views by Person==<br />
<br />
To allow users to include a list of their documents in home pages, and to genrate a view based on the author edit the file :<br />
<br />
vi /var/lib/eprints3/archives/yourarchivename/cfg/cfg.d/views.pl<br />
<br />
Add in the lines :<br />
<br />
<br />
{ <br />
id=>"people", <br />
allow_null=>0, <br />
fields=>"creators_name/editors_name", <br />
order=>"title", <br />
include=>1 <br />
},<br />
<br />
Don't forget the comma after the previous entry. This will produce out to the views section based on the persons name. It will give you text, html, and include files. I use the include file for displaying items on home pages.<br />
<br />
For instance a link inside a users home page:<br />
<br />
<?php<br />
include ("http://eprints.adastral.ucl.ac.uk/view/people/{Family},_{Given Name}.include")<br />
?><br />
<br />
Will give them a list of all their documents in the eprints repository, and the link :<br />
<br />
http://eprints.adastral.ucl.ac.uk/view/people/<br />
<br />
Will list all people that have published articles into eprints.</div>Neilmarjhttps://wiki.eprints.org/w/index.php?title=Browse_By_Person&diff=2594Browse By Person2006-12-14T09:29:30Z<p>Neilmarj: </p>
<hr />
<div>==Views by Person==<br />
<br />
To allow users to include a list of their documents in home pages, and to genrate a view based on the author edit the file :<br />
<br />
vi /var/lib/eprints3/archives/yourarchivename/cfg/cfg.d/views.pl<br />
<br />
<br />
Add in the lines :<br />
<br />
<br />
{ <br />
id=>"people", <br />
allow_null=>0, <br />
fields=>"creators_name/editors_name", <br />
order=>"title", <br />
include=>1 <br />
},<br />
<br />
Don't forget the comma after the previous entry. This will produce out to the views section based on the persons name. It will give you text, html, and include files. I use the include file for displaying items on home pages.<br />
<br />
For instance a link inside a users home page:<br />
<br />
<?php<br />
include ("http://eprints.adastral.ucl.ac.uk/view/people/{Family},_{Given Name}.include")<br />
?><br />
<br />
Will give them a list of all their documents in the eprints repository, and the link :<br />
<br />
http://eprints.adastral.ucl.ac.uk/view/people/<br />
<br />
Will list all people that have published articles into eprints.</div>Neilmarjhttps://wiki.eprints.org/w/index.php?title=GUI_Submission_with_no_Documents&diff=2593GUI Submission with no Documents2006-12-14T09:28:58Z<p>Neilmarj: </p>
<hr />
<div>==Submitting with no documents==<br />
<br />
I allow this as we may be adding documents in later after the information.<br />
<br />
To allow a submission without a document, edit the file;<br />
<br />
vi /var/lib/eprints3/archives/yourarchivename/cfg/cfg.d/document_upload.pl<br />
<br />
And change the lines;<br />
<br />
$c->{required_formats} =<br />
[<br />
"text/html",<br />
"application/pdf",<br />
"application/postscript",<br />
"text/plain"<br />
];<br />
<br />
<br />
To :<br />
<br />
$c->{required_formats} =<br />
[<br />
];</div>Neilmarjhttps://wiki.eprints.org/w/index.php?title=Removing_User_Registration&diff=2591Removing User Registration2006-12-14T09:26:28Z<p>Neilmarj: </p>
<hr />
<div>==Removing User Registration==<br />
<br />
Disable web user registration, edit the file;<br />
<br />
vi /var/lib/eprints3/archives/yourarchivename/cfg/cfg.d/registration.pl<br />
<br />
Change the line : <br />
<br />
$c->{allow_web_signup} = 1;<br />
<br />
to :<br />
<br />
$c->{allow_web_signup} = 0;<br />
<br />
Change the file;<br />
<br />
vi /var/lib/eprints3/archives/yourarchivename/cfg/lang/en/static/error401.xpage<br />
<br />
<nowiki><p><a href="{$config{perl_url}}/set_password">Register / Reset my password</a></p></nowiki><br />
<br />
to :<br />
<br />
<nowiki><p><a href="{$config{perl_url}}/set_password">Reset my password</a></p></nowiki><br />
<br />
<br />
<br />
To remove register link under the search, edit the file;<br />
<br />
vi /var/lib/eprints3/archives/yourarchivename/cfg/lang/en/phrases/dynamic.xml<br />
<br />
Change the line :<br />
<br />
<epp:phrase id="dynamic:not_logged_in">Not logged in. <a href="{$config{userhome}}">login</a> | <a href="{$config{perl_url}}/register">register</a></epp:phrase><br />
<br />
To :<br />
<br />
<epp:phrase id="dynamic:not_logged_in">Not logged in. <a href="{$config{userhome}}">login</a></epp:phrase><br />
<br />
<br />
Then as apache user run :<br />
<br />
/var/lib/eprints3/bin/generate_static yourachivename<br />
<br />
As root run :<br />
<br />
service httpd restart</div>Neilmarjhttps://wiki.eprints.org/w/index.php?title=Web_Interface_Style_and_Images&diff=2590Web Interface Style and Images2006-12-14T09:25:07Z<p>Neilmarj: </p>
<hr />
<div>==Style Sheet Changes==<br />
<br />
All changes to style sheet setting should be made in the directory /var/lib/eprints3/archives/yourarchivename/cfg/static/style/auto, and updated using the generate_static command. Changes made in the html directory will be overwritten.<br />
<br />
Style sheets are processed alphabetically, eprints has a local stlye sheet setup called zzz_local.css, any changes can be made in this file, and settings from previous css files will be over writen with values in this file. I use the EditCSS function in Firefox to configure my stlye sheets and copy the modifications directly into this file.<br />
<br />
When modifications are completed, as the user apache execute;<br />
<br />
/var/lib/eprints3/bin/generate_static yourarchivename<br />
<br />
==Image Changes==<br />
<br />
Here's where I cheat! I have taken the original files and changed the colour resaving as the original file name. This can be a little confusing as some of the files caontain the colour in the title. Changed files should be saved into a new directory : /var/lib/eprints3/archives/yourarchivename/cfg/static/style/images, changes made in the html directory will be overwritten by the generate_static command.<br />
<br />
mkdir /var/lib/eprints3/archives/yourarchivename/cfg/static/style/images<br />
<br />
Copy edited images to above directory, as user apache run the command;<br />
<br />
/var/lib/eprints3/bin/generate_static yourarchivename<br />
<br />
Images will now be copied into the html directory.</div>Neilmarjhttps://wiki.eprints.org/w/index.php?title=Manual&diff=2587Manual2006-12-14T09:13:19Z<p>Neilmarj: </p>
<hr />
<div>[[:Category:Installation|Installing]] EPrints on various platforms.<br />
<br />
{{manual}}<br />
<br />
The pages linked on the right represent the core pages of the EPrints manual. Other pages on this wiki may be useful as well, but new users should start here.<br />
<br />
See the [[Main Page]] for other areas of this wiki.<br />
<br />
[[EPrints Directory Structure]] - will be linked somewhere better, later.<br />
<br />
[[Workflows]] - the structure of the EP3 workflow files<br />
<br />
[[EPScript]] - documentation for the EP3 Scripting language (for use in citations and workflow files).<br />
<br />
[[Preservation Support]] in GNU EPrints 3<br />
<br />
[[Customisation]]</div>Neilmarjhttps://wiki.eprints.org/w/index.php?title=Manual&diff=2475Manual2006-11-10T13:51:22Z<p>Neilmarj: </p>
<hr />
<div>[[Installing Eprints 3 on Fedora Core 5]]<br />
<br />
[[Installing EPrints 3 on RedHat Enterprise 4]]<br />
<br />
{{manual}}<br />
<br />
The pages linked on the right represent the core pages of the EPrints manual. Other pages on this wiki may be useful as well, but new users should start here.<br />
<br />
See the [[Main Page]] for other areas of this wiki.<br />
<br />
[[EPrints Directory Structure]] - will be linked somewhere better, later.<br />
<br />
[[Workflows]] - the structure of the EP3 workflow files<br />
<br />
[[EPScript]] - documentation for the EP3 Scripting language (for use in citations and workflow files).</div>Neilmarjhttps://wiki.eprints.org/w/index.php?title=Manual&diff=2474Manual2006-11-10T13:50:59Z<p>Neilmarj: </p>
<hr />
<div>[[Installing Eprints 3 on Fedora Core 5]]<br />
<br />
[[Installing on RedHat Enterprise 4]]<br />
<br />
{{manual}}<br />
<br />
The pages linked on the right represent the core pages of the EPrints manual. Other pages on this wiki may be useful as well, but new users should start here.<br />
<br />
See the [[Main Page]] for other areas of this wiki.<br />
<br />
[[EPrints Directory Structure]] - will be linked somewhere better, later.<br />
<br />
[[Workflows]] - the structure of the EP3 workflow files<br />
<br />
[[EPScript]] - documentation for the EP3 Scripting language (for use in citations and workflow files).</div>Neilmarj