Question profile link should not display in forum stats

HI I am very happy with Kunena 1.09 and Joomla 1.5, expeically the integraoitn with Community Builder which works wonderfully.

My first little site is set up not to display user profiles unless they are registered, and also to display forum stats. However there is a link to the most recent user profile in the forum stats, which is therefore a broken link unless the user is logged in.

Is there a way to stop a broken link to the user profile for visitors in the forum stats section? it is generating broken link reports from Google.

More information: I enabled profile viewing in Community builder for unregistered users, and the profle stats link is still broken, because the link is trying to return a Kunena forum link instead of a community builder link.

It is a larger problem to stop profile viewing by unregistered browsers, because all the forum posts also have links to the profiles which still work for unregistered viewers, even if profile browsing is restricted in community builder. I think this is not such a big problem by restricting details for users in the public profile view, but the link to the user in forum stats is still a problem.

The broken link could be a relic templating issue from an upgrade. My template had the following in template/default/plugin/stats/frontstats.php:

I changed it to

and the link works, now I have enabled cb browsing of profiles in the frontend. I guess there should be a check in lib/kunena.link.class.php if profile browsing is enabled, and if not, to display a message that the user needs to be logged in to view profiles. Otherwise it presents the general 'unauthorized to view resource' message.
I was able to get this working by editing frontstats.php from

Nice catch! Will fix that soon.

The same problem occurs in recentposts.php

It's more complicated if the post is by a guest, there is no logic in place not to display the link if the userid is not a registered one. I just set "$showname=o;" at the top of recentposts.php as a temporary workaround.

We have just made test release from 1.0.10, but if there will be other bug fixes as well, I will fix this one, too.

If you find more of those, please report them in here.