Thanks for your support! This is an important feature for our installation here at the SFU student libraries, so I started working on it. It seems clear I need to add four new config parameters for opac and intranet, cgi and html URL prefixes. In my experience with other projects (Gallery, PHP WebDAV and MediaWiki), this parameter is usually named 'baseUrl' or something, however each of these projects has only one URL prefix parameter, they don't separate opac and intranet, cgi and html. As far as distinguishing URL path prefixes from file system path prefixes, I like the Apache Location vs. Directory vocabulary. But for consistency with current 'intrahtdocs' and 'opachtdocs' config parameters, and with the 'intranet-cgi', 'opac-html', etc. path components, I've currently used: * 'intracgi': Should default to '/cgi-bin/koha' * 'opaccgi': Should default to '/cgi-bin/koha' * 'intrahtml': Should default to '' * 'opachtml': Should default to '' Adding the html URL prefixes was easy because html already uses the 'themelang' and 'interface' template variables. I only needed to edit Output.pm:gettemplate Adding the cgi URL prefix seems like it will be more tedious because it's used both in template and Perl code files. Also, before I go editing template files for various translations, I assume each translation is built from one source file? I browsed the developer wiki a bit, but haven't yet found instructions to build a Koha distribution archive from the source repository (presumably this involves compiling localized versions of templates). Please find attached the small patch I created so far and my SSH key. Can I please have access to clone the 2.2 git repository? If anyone can offer feedback or point me at relevant documentation, that'd be much appreciated! Thanks, Jack
Jack Bates <ms419@...> asked:
How do I change the path prefix where Koha looks for HTML / TMPL? Koha has used two VirtualHosts for as long as I've been here, so I'm not sure that's supported yet. It needs a hunt-and-kill on the hard-coded locations. It would be a good thing to do if you have time. Not only would it be a good thing, you'd be rewarded with thanks and
----- "MJ Ray" <mjr@...> wrote: praise :-)
Maybe we should move this discussion to koha-devel? http://lists.nongnu.org/mailman/listinfo/koha-devel Jack Bates <ms419@freezone.co.uk> wrote:
[...] Also, before I go editing template files for various translations, I assume each translation is built from one source file?
I think they're built from the English template and a po file with the tools in misc/translator.
I browsed the developer wiki a bit, but haven't yet found instructions to build a Koha distribution archive from the source repository (presumably this involves compiling localized versions of templates).
In 2.2, it's misc/buildrelease and I don't think it localises templates. In HEAD, that is in rather a state of flux just now. It may end up as "perl Makefile.PL && make dist" but that's not brilliant yet.
Please find attached the small patch I created so far and my SSH key. Can I please have access to clone the 2.2 git repository?
As I understand it, you don't need ssh access to clone it: see http://lists.nongnu.org/archive/html/koha-devel/2007-06/msg00008.html for instructions. 2.2 is the branch origin/rel_2_2 Hope that helps, -- MJ Ray - see/vidu http://mjr.towers.org.uk/email.html Experienced webmaster-developers for hire http://www.ttllp.co.uk/ Also: statistician, sysadmin, online shop builder, workers co-op. Writing on koha, debian, sat TV, Kewstoke http://mjr.towers.org.uk/
participants (2)
-
Jack Bates -
MJ Ray