gitea
/
Koha-clms
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Koha-clms/value_builder
History
tipaul 6231cad8cb 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. 
That was coded "$X" => $X
when $X=0 or ' ', that meaned $X set to 0, thus not selected.

reported a long time ago, but i never take time to fix it.
 		2005-12-15 10:05:53 +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_leader.pl bugfix : all plugins used "parameters" as permission flag, they should use "editcatalogue" 2005-12-08 09:35:50 +00:00
unimarc_field_4XX.pl bugfix : all plugins used "parameters" as permission flag, they should use "editcatalogue" 2005-12-08 09:35:50 +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 bugfix : all plugins used "parameters" as permission flag, they should use "editcatalogue" 2005-12-08 09:35:50 +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