Differences

This shows you the differences between two versions of the page.

--- dev:opac:template-toolkit [2011/10/19 15:24] – [Template Toolkit OPAC] lebbeous
+++ dev:opac:template-toolkit [2022/02/10 13:34] (current) – external edit 127.0.0.1
@@ Line 33: / Line 33: @@
   * The eventual goal is to fully integrate the TT OPAC into the staff client.  Until it's complete, it's necessary to manually configure the staff client to use the new OPAC.
-  * To use the Template Toolkit OPAC as the catalog in the staff client, as opensrf:<code>
+  * To use the Template Toolkit OPAC as the catalog in the staff client, click the **Toggle Template Toolkit OPAC** link on the staff client landing page. You might need to restart the staff client to make the change take effect.
-echo "urls['opac'] = '/eg/opac/advanced';
-urls['opac_rdetail'] = '/eg/opac/record/';
-urls['opac_rresult'] = '/eg/opac/results';
-urls['opac_rresult_metarecord'] = '/eg/opac/results?metarecord=';
-urls['browser'] = urls.opac;" > /openils/var/web/xul/server/skin/custom.js;</code>
 ==== Customizing ====
@@ Line 47: / Line 42: @@
   * Create a directory where you will store your template customizations, let's say ''/openils/var/my_own_templates''.
+  * Edit your Apache configuration to include the overriding template directory _after_ the main template directory:<code>
-  * Look for the node ''<template_paths>'' in your ''/openils/conf/oils_web.xml'' file.
+# Templates will be loaded from the following paths in reverse order.
+PerlAddVar OILSWebTemplatePath "/openils/var/templates"
-  * Add a new ''<path>'' child node directly //above// all existing ones so that everything within ''<template_paths>'' now looks something like this:
+PerlAddVar OILSWebTemplatePath "/openils/var/my_own_templates"
+</code>
-<code>
+    * You can, for example, customize skins on the basis of the hostname being used via virtual hosts; note that the base template directory gets loaded first in eg_vhost.conf, so you're just specifying the customizations here:<code>
-  <template_paths>
+<VirtualHost *:80>
-    <path>/openils/var/my_own_templates</path>
+        ServerName myhostname
-    <path>/openils/var/templates</path>
+        DocumentRoot /openils/var/web/
-  </template_paths>
+        DirectoryIndex index.xml index.html index.xhtml
+    Include eg_vhost.conf
+    <Location /eg>
+        PerlAddVar OILSWebTemplatePath "/openils/var/my_own_templates"
+    </Location>
+</VirtualHost>
 </code>
   * Place your version of all ''.tt2'' files that you would edit into a directory structure that mirrors that of the stock template path.  That is, if you want to have your own version of ''/openils/var/templates/default/opac/parts/topnav.tt2'', put it at ''/openils/var/**my_own_templates**/default/opac/parts/topnav.tt2''.
@@ Line 67: / Line 66: @@
 === String Localization ===
-  * Create a .po file for your locale.  Requires Locale::Maketext::Extract::Plugin::TT2<code>
+  * Create a ''.po'' file for your locale. Requires the ''Locale::Maketext::Extract::Plugin::TT2'' Perl module:<code>
-sudo -u opensrf xgettext.pl --plugin=tt2 --directory=Open-ILS/src/templates/opac/ --output-dir=/openils/var/data/locale --output=tpac.fr_CA.po</code>
+sudo -u opensrf xgettext.pl --plugin=tt2 --directory=Open-ILS/src/templates/opac/ --output-dir=/openils/var/templates/locale --output=tpac.fr_CA.po</code>
-  * Add your .po file to /openils/conf/oils_web.xml<code>
+  * Add your .po file to the Apache ''eg_vhost.conf'' file in the ''<Location /eg>'' section:<code>
-    <locales>
+    PerlAddVar OILSWebLocale "en_ca"
-        <en_US/>
+    PerlAddVar OILSWebLocale "/openils/var/templates/locale/tpac.en_CA.po"
-        <en_CA>/openils/var/data/locale/tpac.en_CA.po</en_CA>
+    PerlAddVar OILSWebLocale "fr_ca"
-        <fr_CA>/openils/var/data/locale/tpac.fr_CA.po</fr_CA>
+    PerlAddVar OILSWebLocale "/openils/var/templates/locale/tpac.fr_CA.po"
-    </locales></code>
+</code>
   * Edit strings in your new .po file.  For example:<code>
 ...