[Koha-bugs] [Bug 2774] New: Theme not pointing to correct xslt file

[bugzilla-daemon at pippin.metavore.com]

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2774

           Summary: Theme not pointing to correct xslt file
           Product: Koha
           Version: rel_3_0
          Platform: PC
        OS/Version: Linux - Debian
            Status: NEW
          Severity: normal
          Priority: P3
         Component: OPAC
        AssignedTo: jmf at liblime.com
        ReportedBy: dearden at sarsf.org
         QAContact: koha-bugs at lists.koha.org


I turned on both OPAC xslt options and edited the MARC21slim2OPACDetail.xsl
file in the default prog theme to change the way the link under the title
works.  I am running multiple databases and only wanted this to apply to a
single one.  I copied the prog directory as a new name, and set the xsl file in
the prog theme to the original one and the xsl file in my new theme to my new
one.  I then changed the opacthemes option to point to the new theme.  I
connected to the OPAC and there was no difference from the original.  I then
changed a color in the css file in the new theme location to confirm it was
looking in the correct place, the color changed on the OPAC.  I renamed prog to
progx, and tried again.  I get this error.
Koha error

The following fatal error has occurred:

Could not create file parser context for file
"/usr/share/koha/opac/htdocs/opac-tmpl/prog/en/xslt/MARC21slim2OPACDetail.xsl":
No such file or directory at /usr/share/koha/lib/C4/XSLT.pm line 121

Apache  Server version: Apache/2.2.3 Server built: Mar 22 2008 09:29:10
Koha    3.00.00.107
Koha DB 3.0000107
MySQL   mysql Ver 14.12 Distrib 5.0.32, for pc-linux-gnu (i486) using readline
5.2
OS      Linux SAR56Linux 2.6.18-6-686 #1 SMP Sun Feb 10 22:11:31 UTC 2008 i686
GNU/Linux
Perl    5.008008

Looks like the pointer to the xslt directory is still pointing to the one in
the prog theme instead of my new theme.




------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.