koha-bugs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Koha-bugs] [Bug 1107] Authorities broken with new addbiblio templates


From: bugzilla-daemon
Subject: [Koha-bugs] [Bug 1107] Authorities broken with new addbiblio templates
Date: 15 Oct 2006 10:06:45 -0000

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


address@hidden changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |




------- Comment #2 from address@hidden  2006-10-15 23:06 -------
Although this bug was closed by Joshua having looked at all versions  I did not
see any remedy for this in any of them but head. I do not have any other
version running but HEAD so you close this bug if are sure that its working
with your release.
The Bug in detail:
Addbiblio.pl assigns fixed index numbers to all fields and passes it on to the
template which uses this to call value_builder routines and authority routines.
However the new clonesubfield javascripts (in the template)allows you to add
additional subfields on the template, thus changes the indexes. So as an
example you add more 650$x's to your subject fields. Then when you are to fill
700$a from auhtors authority you get the field prior to 700 (690 or 650
whatever) because the index is wrong.
To remedy this i have changed the code in head and added another index.An index
for each tag. This correction requires change in addbinlio.pl , addbiblio.tmpl
and also in authority routines like blind-detail-biblio-search etc. When i
first committed these i put a note about them but it seems nobody applied them
to any version. I cannot correct other versions as i do not have them running
and i do not want to break the  code. 

I am going to open another bug related to this index in marchtml2xml in
Biblio.pm as well 




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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]