Aggregated field is replaced, which causes problems when its a ID

same problem for me too... I thought I could bypass it by using the tokens to reconstruct the link, but no luck so far.

Ah I really neeed this too!

Link this field to its taxonomy term page has no effect when checked.

Surely this is a serirous flaw! Having a list of the data, but not being able to link the information!!!!!
Escalating to Critical

Irakli??

Have you tried theming?

Can you be specific? Ithis is a really importsnt thing for me. Normally with views i can click on link to taxonomy term page or link to node.

That option is the same for when we group and count.

If you use the node count module, which only works when creating a new taxonomy term view/block, the link to term works correctly when the option is checked. The downside of that module is it is very limited in the available filters, and can not hide empty .

Your module is great as you can use it in the node type view with all filters... But it cant create a link to the taxonomy term.

I mean if you are going to create a list with totals, it is the most impiortant thing for the user to be able to click on the terms in that list.

Am I supposed to put a search box under the list so they have to manually search for the taxonomy listed? that would be bad user experiance I think.

Please tell me what every I have to do this is a very very very important thing.

Thanks

You should be able to link it if you override a theme: http://views-help.doc.logrus.com/help/views/using-theme

I will try to look into why it may not be working out-of-the-box, too, but later.

Look, I have no idea why the link is not being created to the taxonomy term. honestly themes are my weakest point that I have had no time to even care about. Right now I am trying to create a tour ' d force... to find out the most I can do with my data.

I am so bad with everything... the least I excpect hope and xdream for as the modules to work.. I will kill myself infront of my computer everyday and sacrifice my endless and hopeless idealism to make the most minute of an expression bfore I die.

most of the modules work so well it is only but my meaningless existanse which prohiibits me from understadning and flly untilizing their maximum potential.

This is the exception,. I think I understand how to use your module. However ironically from my seat in this lonseme place in China, a stranger to all life outside in a land that is not my own, I can see that the most simple function of adding a link to the taxonomy terms does not work.

I realize that when you make it work I will only be left with mmy aspirations and dreams and hopes to do something to make this world a better place..

And there a a million other problems that tell me I will die and am a fool for even trying...

But that one effort you can give to make the fuction work will make the chance of having the workd a better place.\

I am at your mercy,

I had the same problem and after much frustration...I found a workaround.

I actually had to add NID as a field (Excluded from display) at the very top of the stack, then include it in "Fields to group on".

It seems the "Group by" is somehow chunking the NID - so the link can't use it.

I think the issue here is that when using a ID field (TID, NID, UID) as the aggregated field, the result of that select is now the count value.

This count value is then used by views in the creation of links, which clearly is then wrong/broken e.g.

A view which shows the top posters of a given content type, Group By field is username, aggregated field is the UI. Works, but then the links for the users are then /user/{number_of_nodes}, instead of /user/{uid}.