Question Template Drops when Users/Admin Logged in

I've managed to come up with a fix for this problem, though I'm not sure if there are any side effects yet.

On line 272 of listcat.php I commented out the following line:

After doing that the template loaded as expected.

Just a note that may be useful for the devs. While testing I discovered that if I used the pull-down menu to jump to another board, the template loaded fine, so the problem only seems to be in the top-level category listing page.

Well done on working around the problem - it doesn't solve it by any means, though.

A couple of comments. It's not that "bizarre" that a Joomla extension that has undergone many iterations - indeed, the technical requirements in terms of PHP and SQL are far removed from what was available when Joomla 1.0 was built - so it's not really all that surprising that eventually something would break.

I agree with you that upgrading from from J! 1.0 to J! 1.5 is no trivial matter (and I've stated as such on a dozen or more occasions) but I disagree with your observation that Kunena is essentially "a native component for [the J! 1.0] series and only run in Legacy mode for 1.5" because such claims are disputed by users at the Joomla website. I would rather say that Kunena 1.0.10 was "transitional" ... in between J! 1.0 and J! 1.5.

While there is no definite evidence to support the claim that up to 99% of native extensions work with the legacy plugin turned on, there is much anecdotal evidence to suggest that it's probable that only 1% of native products will fail. It is, however, true that those products that were developed for Joomla! 1.0 will not work in Joomla! 1.5 without the legacy plugin enabled but that there's a high likelihood that some, older, Joomla! 1.0 extensions are inoperable under Joomla 1.5 even with the Legacy Plugin enabled. Given this lack of guarantee, it's also probable that, at some point in time, the development of J! 1.5 "legacy mode" extensions may not operate in the original J! 1.0 environment ... and it looks as though we may have discovered that's the case with Kunena 1.0.10.

However, I agree with you and Matias that it's desirable to fix K 1.0.10 so that it works in the J! 1.0 environment.