Editing Upgrading 3.3.12+ to 3.4 (section)

=Upgrade from Tarball=

==Pre-upgrade==
* If you have local modifications to the core files (in /opt/eprints3/perl_lib), you may need to manually migrate your changes.
* If you use Twitter integration, use CPAN to install LWP::Authen::OAuth as this is no longer in perl_lib.  To do so, as root run:
 cpan LWP::Authen::OAuth
* Download each of the Bazaar plugins you have installed as EPM files from your existing repository.
* Make a backup of your local configurations.

==Process==
We will move your existing eprints 3.3.16+ installation from <code>/opt/eprints3/</code> to <code>/opt/eprints3.3</code>, install eprints 3.4, then migrate your configurations into EPrints 3.4; cf. [https://wiki.eprints.org/w/Category:Installation Category Installation]
<br>
'''as root'''
 apachectl stop
 cd /opt
 eprints3/bin/epindexer stop
 mv eprints3 eprints3.3

* Download EPrints 3.4 core and publication flavour tarball and install them from [http://files.eprints.org/ Files.eprints.org] with
 wget https://files.eprints.org/3097/5/eprints-3.4.6.tar.gz
 wget https://files.eprints.org/3097/6/eprints-3.4.6-flavours.tar.gz
'''as root'''
 cd /root
 tar xvzf eprints-3.4.6.tar.gz
 tar xvzf eprints-3.4.6-flavours.tar.gz

* Have a look to <code>/root/eprints-3.4.6/INSTALL</code> for some local adaption options.
'''as root'''
 cd eprints-3.4.6
 ./configure
 make install

* Move your current repository from 3.3 to 3.4
'''as root'''
 cd /opt
 mv eprints3.3/archives/ARCHIVENAME eprints3/archives/
* After moving, make sure all files inside <code>/opt/eprints3</code> are still owned by eprints user and belongs to eprints group, thus
'''as root'''
 chown -R eprints:eprints /opt/eprints3

* Create <code>/opt/eprints3/archives/ARCHIVENAME/cfg/cfg.d/00_flavour.pl</code> to set the appropriate flavour, typically 'pub', i.e. 
 echo "\$c->{flavour} = 'pub';" > /opt/eprints3/archives/ARCHIVENAME/cfg/cfg.d/00_flavour.pl

* create a symbolic link to <tt>default.xml</tt> 
 cd /opt/eprints3/archives/ARCHIVENAME/cfg/templates/ (or /opt/eprints3/archives/ARCHIVENAME/cfg/lang/en/templates/
 ln -s default.xml default_internal.xml

* Audit each of their local config files against the pub_lib flavours config files:
#The first <code>diff</code> below will identify all the files that are the same.  If so, delete the ones in <code>archives/ARCHIVENAME/cfg/cfg.d/</code>.  You almost certainly should not find any, as the files in <code>flavours/pub_lib/cfg.d</code> will at very least have updated copyright/licensing boilerplate.
#The second <code>diff</code> will find where files exists in both directory are different.  Here they should be compared to see, if the local differences are superficial (e.g. slightly different comments or spacing) and therefore can be removed.  Also the pub_lib flavour version may fix an outstanding bug or perform the required functionality more succinctly.  If this is the only change, then the local archive version can be deleted, otherwise the change should be incorporated in the local version.
 cd /opt/eprints3/
 diff -rs archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ are identical$'
 diff -rq archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ differ$'

<ul><li>Compare <code>archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl</code> with <code>flavours/pub_lib/cfg/cfg.d/eprint_fields_pub.pl</code>  maybe with the help of [http://diffuse.sourceforge.net/download_de.html ''diffuse''] to overcome this business easier:<ul>
<li>If these are different and fields are present in <code>eprint_fields_pub.pl</code> and not <code>eprint_fields.pl</code> or the definitions (e.g. type, options, etc.)  for the same field are different then:<ol>
<li>Copy <code>flavours/pub_lib/cfg.d/eprint_fields_pub.pl</code> to their archive's <code>cfg/cfg.d/</code>.
<li>Modify the fields in their archive's <code>cfg/cfg.d/eprint_fields_pub.pl</code> where they have different definitions (e.g. type, options, etc.) to those in <code>eprint_fields.pl</code>.
<li>Remove all fields in their archive's <code>cfg/cfg.d/eprint_fields.pl</code> where they also occur in their archive's <code>cfg/cfg.d/eprint_fields_pub.pl</code>, no matter if already transferred due to previous item or initially the same.</ol>
<li>If there are only additional fields in <code>archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl</code> then just do the last step.
<li>If the two files are identical then you need to do nothing.  However, this is extremly unlikely.
</ul>
Finally, the specification is still the same, but mostly split into two distinct files, which obey the known rule ''Local version overrides central one''.</ul>
* Synchronise <code>archives/ARCHIVENAME/cfg/cfg.d/epm.pl</code> with <code>ingredients/bazaar/cfg.d/epm.pl</code>, i.e. remove <code>archives/ARCHIVENAME/cfg/cfg.d/epm.pl</code> in case of ''no'' local modifications.

* Ensure the following bazaar files are disabled by renaming to FILENAME.pl''.disabled''.  Once they have been reinstalled via the Bazaar then they can be moved back into place.  Using <code>epadmin test</code> is a good way of discovering which files need this doing, but below is a list of common files that should be temporarily moved, if they exist in your archive's <code>cfg/cfg.d/</code> directory:
 mv z_orcid_support.pl z_orcid_support.pl.disabled
 mv zz_hefce_oa_fields.pl zz_hefce_oa_fields.pl.disabled
 mv zz_rioxx2.pl zz_rioxx2.pl.disabled
 mv z_meprints.pl z_meprints.pl.disabled 

* As the eprints user, run <code>epadmin update</code> to add any new fields that were not previously present (typically this is embargo_reason for documents and requester_email for request)
 /opt/eprints3/bin/epadmin update ARCHIVENAME

* Generate new Apache configuration and as root test (fixing any issues) and restart Apache after necessary site-specific adaption are done.
 /opt/eprints3/bin/generate_apacheconf --system --replace ARCHIVENAME
'''as root'''
 apachectl configtest
 apachectl restart

* Once confirming that EPrints is generally working.  Go to Admin->Bazaar then install the Bazaar plugins you downloaded from your 3.3 repository before starting the upgrade process.  This can be done by going to the Available tab in the Bazaar and strolling to the Upload section at the bottom.  Unfortunately, you cannot do a bulk upload, so will need to install each plugin in turn. 

* Move back the files you renamed to FILENAME''.disabled'' earlier, the epindexer into service and reload Apache
'''as root'''
 /opt/eprints3/bin/epindexer start
 apachectl graceful

* Finally, run <code>generate_static</code> to make sure all pages are regenerated with any changes to configuration.
  /opt/eprints3/bin/generate_static ARCHIVEID

==Notes==
* EPrints 3.4.4+ now uses LONGTEXT instead of VARCHAR(255) for the <code>requester_user_agent</code> column. Upgrading from v3.3 '''will not''' automatically update this column definition in the database. Manually altering the column is an option, but may take a long time as the access table can contain millions of rows. See: https://github.com/eprints/eprints3.4/issues/427 
* 3.4 does not automatically update an archive's <code>html/en/</code> files. If there are any bugs with broken JavaScript or unexpected CSS, try deleting the archives <code>html/en/javascript/auto.js</code> or <code>html/en/style/auto.css</code>.  Similarly if a static page cannot be changed try deleting it under the archive's <code>html/en/</code> or running <code>generate_static</code>.
* If some Perl modules are giving out error messages like: 
  Can't locate object method "new" via package "EPrints::Plugin::Event::PIRUS" at /opt/eprints3/bin/../perl_lib/EPrints/PluginFactory.pm line 276.
  Can't locate object method "new" via package "EPrints::Plugin::Screen::EPrint::Box::Tools::SUPER" at /opt/eprints3/site_lib/plugins/EPrints/Plugin/Screen/EPrint/Box/Tools.pm line 12.
It is because their parent module has not been initialised. This happens when the parent module lives in perl_lib, and the problem module live in elsewhere; e.g. parent module of PIRUS(Event.pm) is in <code>./perl_lib</code>, while the <code>PIRUS.pm</code> is in <code>./pub_lib</code>. 
Just need to <code>use</code> the parent module before the <code>ISA</code> line:
 use EPrints::Plugin::Event;

[[Category:Upgrading]]