Bug 8744: Thesaurus in authorities should not lock fields
Although fields in the authority editor should support thesaurus control, they should never be locked, as authority records commonly refer to other records that may not be in use locally (and therefore might not be in the authority file). Test plan: 1) Make sure a 5xx field in one of your authority frameworks is thesaurus-controlled. 2) Note that you cannot edit the field directly. 3) Apply patch. 4) Note that you can now edit the field irectly. Signed-off-by: wajasu <matted-34813@mypacks.net> Signed-off-by: Paul Poulain <paul.poulain@biblibre.com>
This commit is contained in:
parent
529bb9c2a4
commit
e341c2a717
1 changed files with 2 additions and 3 deletions
|
@ -194,9 +194,8 @@ sub create_input {
|
|||
id=\"".$subfield_data{id}."\"
|
||||
name=\"".$subfield_data{id}."\"
|
||||
value=\"$value\"
|
||||
class=\"input_marceditor readonly\"
|
||||
tabindex=\"1\"
|
||||
readonly=\"readonly\" \/>
|
||||
class=\"input_marceditor\"
|
||||
tabindex=\"1\" \/>
|
||||
<a href=\"#\" class=\"buttonDot\"
|
||||
onclick=\"openAuth(this.parentNode.getElementsByTagName('input')[1].id,'".$tagslib->{$tag}->{$subfield}->{authtypecode}."'); return false;\" tabindex=\"1\" title=\"Tag Editor\">...</a>
|
||||
";
|
||||
|
|
Loading…
Reference in a new issue