gitea
/
Koha-clms
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Koha-clms/value_builder
History
tipaul 675f9d5b01 reverting cloneTag bugs (see joshua mail on koha-devel) : 
* going back to a previous version, with server call to clone a Tag
* keeping BIG_LOOP in template (just 1 template for every tag)
I didn't check npl templates, but synch'ing them should not be too hard.

(ps : i've reverted default templates to 1.33.2.23)
 		2006-06-19 13:18:17 +00:00
..
labs_theses.pl Bug Fixing : unimarc_field_210c.pl getting page search work and adding scrolbars. 2005-10-15 16:45:42 +00:00
marc21_field_003.pl new plugin for fixed field 003 2006-03-19 02:51:20 +00:00
marc21_field_005.pl adding some marc21 plugins 2006-03-01 17:58:00 +00:00
marc21_field_006.pl bugfixing 2006-03-13 18:37:18 +00:00
marc21_field_007.pl bugfixing 2006-03-13 18:37:18 +00:00
marc21_field_008.pl removing warn. 2006-04-02 18:33:40 +00:00
marc21_field_008_authorities.pl Add some new plugins for authorities management 2006-03-04 03:16:30 +00:00
marc21_leader.pl fixing extra leader position. 2006-04-02 18:32:20 +00:00
marc21_leader_authorities.pl typo fix 2006-03-04 07:36:51 +00:00
marc21_leader_book.pl adding some marc21 plugins 2006-03-01 17:58:00 +00:00
marc21_leader_computerfile.pl adding some marc21 plugins 2006-03-01 17:58:00 +00:00
marc21_leader_video.pl adding some marc21 plugins 2006-03-01 17:58:00 +00:00
unimarc_field_4XX.pl reverting cloneTag bugs (see joshua mail on koha-devel) : 2006-06-19 13:18:17 +00:00
unimarc_field_60X.pl bugfix : all plugins used "parameters" as permission flag, they should use "editcatalogue" 2005-12-08 09:35:50 +00:00
unimarc_field_100.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_105.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_106.pl bugfix : all plugins used "parameters" as permission flag, they should use "editcatalogue" 2005-12-08 09:35:50 +00:00
unimarc_field_110.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_115a.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_115b.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_116.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_117.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_120.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_121a.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_121b.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_122.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_123a.pl bugfix : all plugins used "parameters" as permission flag, they should use "editcatalogue" 2005-12-08 09:35:50 +00:00
unimarc_field_123d.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_123e.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_123f.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_123g.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_123i.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_123j.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_124.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_124a.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_124b.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_124c.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_124d.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_124e.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_124f.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_124g.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_125.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_125a.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_125b.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_126.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_126a.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_126b.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_127.pl bugfix : all plugins used "parameters" as permission flag, they should use "editcatalogue" 2005-12-08 09:35:50 +00:00
unimarc_field_128a.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_128b.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_128c.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_130.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_135a.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_140.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_141.pl there was a bug in most plugins : when a value is sent to the template, we often use "$X" => 1 to select a value in a list. 2005-12-15 10:05:53 +00:00
unimarc_field_210c.pl bugfix : all plugins used "parameters" as permission flag, they should use "editcatalogue" 2005-12-08 09:35:50 +00:00
unimarc_field_225a.pl * (UNIMARC specific bugfix) when an editor is entered, with no ISBN, the collection plugin (225a) can find collections attached to the editor name. Note that if there are more than 1 EDITORS authority for a given editor, only the 1st will be used to create collection list. 2006-01-05 15:14:47 +00:00
unimarc_field_700-4.pl changes to reflect official API 2002-12-20 14:02:39 +00:00
unimarc_field_700_701_702.pl why isn't it in CVS ? dunno. Should be there for many months 2004-11-08 19:58:38 +00:00
unimarc_leader.pl bugfix : all plugins used "parameters" as permission flag, they should use "editcatalogue" 2005-12-08 09:35:50 +00:00
usmarc_field_952v.pl Adds a function to autogenerate the date for dateaccessioned for usmarc (would 2005-12-09 16:53:45 +00:00