officium.pl: Use of uninitialized value $value in string eq at DivinumOfficium/RunTimeOptions.pm line 24.

[Augustinus-Altovadensis]

Laudétur Jesus Christus!

In the current version, the output of my web server keeps showing following line:
officium.pl: Use of uninitialized value $value in string eq at divinum-officium-work/web/cgi-bin/horas/../DivinumOfficium/RunTimeOptions.pm line 24.

For every page reload, it shows 26 times...

This error message points to a line in bold in the else loop:

sub unequivocal {
  my ($value, $tablename) = @_;
  my @values_array = main::getdialog($tablename);

  my @r = grep {/$value/} @values_array;

  if (@r == 1) {
    return $r[0] =~ s/.*\///r;
  } else {
    **@r = grep { $_ eq $value } @values_array;**

    if (@r == 1) {
      return $r[0] =~ s/.*\///r;
    } else {
      return;
    }
  }
}

It doesn't seem to do anything, but the error message is kind of annoying (26 times!). Does anybody have an idea, what it does and what can be done to get rid of that? (apart from skipping the entire $value and returning nothing right away, of course).

Thanks, have a nice weekend!

[FAJ-Munich]

Such an error would occur if the function is called without the right number of arguments. Can you narrow it down, when the function is called?

@mbab any other ideas from your end what could cause duchess behavior?

[Augustinus-Altovadensis]

It's a bit strange. When I tried to follow my browser history, I was able to replicate it at a point, where I went back to 30-Apr-2025, Vespers, in the Altovadense version, Latin + Czech. But if I do the same in a new window, I cannot replicate it, so it seems that something stuck from my yesterday's experimenting with Responsorium prolixum or other things I was doing. Once the bug started, it showed on this day for the canonical Office, Office for the Dead and Option page, where I switched off everything apart from the Building script and Contrast background.

And funny thing is that it stopped by itself. And I also tried it right now, the error message showed, then I went into the Options page, switched on the Building script and it was gone. So I switched the Building script off again, and no error message.

Strange.

[FAJ-Munich]

Resolving the issue by entering the options menu could be caused by old cookies on your system which then have been overridden at that point.

[Augustinus-Altovadensis]

Seems that way. I haven't seen it since, therefore we can close. Thank you!