pyragony54 wrote on Sep 9
th, 2017 at 9:38am:
Quote:An Error Has Occurred. Use of uninitialized value $boardv in hash element at Sources/BoardIndex.pm line 2307.
This error appears only once and you do not get to the board index. If I reload the page, the board index appears as if nothing had happened.
$boardv can legitimately be blank -
but I don't why your system is throwing a hissy and mine doesn't. The error clears up because the Variables/user.log gets rewritten everytime someone enters the forum or looks at something.
In BoardIndex find
foreach (@logentries) {
( $name, $date1, $last_ip, $last_host, undef, $boardv, undef ) =
split /[|]/xsm, $_, 7;
Add after
$boardv ||= q{};
Quote: Quote:An Error Has Occurred. Use of uninitialized value $boardname in concatenation (.) or string at Sources/Load.pm line 442.
This is going to be due to bad data in forum.master. There's a board in there that doesn't have data in the first field. (look for '$board{'admin'}' as that shouldn't be there in 2.7 But I also just noticed that data didn't transfer for admin/admin_fix into forum.control
)
as a fix try:
In Load.pm find
my $boardname = ${$board{$i}}[0];
$mybrds .= qq~$boardname<br />~;
return 1;
replace with
if (${$board{$i}}[0]) {
my $boardname = ${$board{$i}}[0];
$mybrds .= qq~$boardname<br />~;
return 1;
}
All of these, so far, have nothing to do with Mods. For whatever reason, your install is more sensitive to uninitialized values than mine - maybe it's a Perl difference or a Perl on Windows difference.
But it isn't a bad thing. As I said before: old YaBB ignored a lot of things that
should have thrown errors. 2.7 throws the errors.
But once I see where the error message is pointing to I can see exactly what's happening and why.