[post:538#5352]
Ggultra2764
08/31/2011 01:13 AM
Reviews: 2354
Posts: 568
|
Considering my entry for Taiyō no Ōji: Horusu no Daibōken didn't have a year keyword for it, I chose to create a keyword for 1968 (year the movie was created) by year I could add to the keyword listings for the movie. But when you try to click on 1968 to pull up a list of titles with the keyword, I get this error message:
error: Can't use an undefined value as an ARRAY reference at /mnt/rest/home/turner/Dropbox/perl/anime/html/comp/limit_cat line 41.
context:
...
37: <%def .table>
38: <%args>
39: $cols
40: $data
41: </%args>
42:
43: <%perl>
44: our $categories;
45: for (my $i=0;$i<=$#$data;$i++) {
...
code stack: /mnt/rest/home/turner/Dropbox/perl/anime/html/comp/limit_cat:41
/mnt/rest/home/turner/Dropbox/perl/anime/html/by-key.html:121
/mnt/rest/home/turner/Dropbox/perl/anime/html/autohandler:102
raw error
|
Loading, please wait... |
|
[post:538#5353]
Devil Doll
08/31/2011 01:25 AM
Reviews: 365
Posts: 1574
|
Interestingly, adding "1969" as keyword and assigning it to the same anime fixes the symptoms.
Could the reason be linked to the subrange of release year values containing a gap with 0 anime for 1969?
Adding Category 2014 (but not 2013) and not assigning any anime to it apparently causes the same effect; the error also appears if 2014 is the only release year of some anime (just like "1968" for Taiyō no Ōji: Horusu no Daibōken).
Edited
on 08/31/2011 01:35 AM.
|
Loading, please wait... |
|
[post:538#5354]
Ggultra2764
08/31/2011 01:51 AM
Reviews: 2354
Posts: 568
|
So essentially, setting up keywords by year requires a proper numerical order for the system to interpret the new entries or else it acts like a spaz and flips out with the mentioned error?
|
Loading, please wait... |
|
[post:538#5355]
Devil Doll
08/31/2011 01:40 PM
Reviews: 365
Posts: 1574
|
I haven't seen the source code, I can only report the result of my experiments (plus guess the possible reason for the problem). But I don't think it will be difficult to fix, probably just some unjustified implicit assumption about something that should be checked instead.
At least it would explain why we never ran into this error before: Because the next year to be created as category ("2012" having been the most recent candidate) never left a gap open.
Edited
on 09/01/2011 01:29 AM.
|
Loading, please wait... |
|