FIXED: Accessing an undefined category causes SQL syntax error

Example: http://anime.mikomi.org/by-key/undefined

Now it gives you a more reasonable error message. The only weird thing is if you go to say: http://anime.mikomi.org/by-key/undefined/Action Then it'll give you the contents of the Action category. (Normally it'd be the intersection of the results of the two categories.)

"(Normally it'd be the intersection of the results of the two categories.)"

I noticed that too. When I want to search for two genres at once, I can't click next without losing the search as it reverts back to the original topic. Like when you have a "Harem/Fan Service Titles" double search on screen, when you go to hit next, it reverts back to just a "Harem" search. We have 80 harems and 220 fan-service titles. Once harem is clicked, it says 46 fan-service titles are available within the harem genre. With the double search displayed, it starts on page one and the dropbox says there are 8 pages of the double search criteria, but remember you can't hit next without it reverting back to the 80 harems.

You see the problem here? Not even the drop box there works as it still reverts back to the regular harem search.

Edited on 09/12/2008 08:53 AM.

I confirm Xenoknight's observation. Other than that, I'm fine with the fix of the SQL issue (I only stumbled over it when mistyping keywords while setting links via the [keyword:] namespace, I'm not even sure whether I could use two keywords here...?).

I didn't actually understand what you were talking about when you first wrote this, but I do now:

When viewing a compound by-key page, using the pager reverts to a view of only the first keyword.

Can you fix that? Is their a way browse by the double keyword search? It would save alot of time when looking for new stuff to watch.

*eyeroll* Of course I can fix it. =) Give me a second to actually look into the problem. I was just sharing when I first figure out what the heck was meant. (I appreciate your eagerness but it also does seem to rub me the wrong way some times too.) It is, now, in fact, fixed.

Edited on 09/17/2008 01:53 PM.