Bug 14446: Workaround to resolve uninitialized value in goto warning
Forcing both GetTab calls to list context resolves the warning. A workaround, not a real fix. Test plan: Search for something in the syspref text bar. Without this patch, you will have a warn: Use of uninitialized value in goto With this patch, you won't. Signed-off-by: Aleisha Amohia <aleishaamohia@hotmail.com> Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de> Signed-off-by: Nick Clemens <nick@bywatersolutions.com>
This commit is contained in:
parent
9bfb3bc378
commit
dbdd85ee1e
|
|
@ -229,7 +229,8 @@ sub SearchPrefs {
|
|||
our @terms = split( /\s+/, $searchfield );
|
||||
|
||||
foreach my $tab_name ( keys %tab_files ) {
|
||||
my $data = GetTab( $input, $tab_name );
|
||||
# Force list context to remove 'uninitialized value in goto' warn coming from YAML::Syck; note that the other GetTab call is in list context too. The actual cause however is the null value for the pref OpacRenewalBranch in opac.pref
|
||||
my ($data) = GetTab( $input, $tab_name );
|
||||
my $title = ( keys( %$data ) )[0];
|
||||
my $tab = $data->{ $title };
|
||||
$tab = { '' => $tab } if ( ref( $tab ) eq 'ARRAY' );
|
||||
|
|
|
|||
Loading…
Reference in New Issue