androoo wrote
I also get this behaviour, when is the fix due any news please ? or any news on how to fix our selves , is in the database logic or aspx ?
1) EVERYONE gets this behavior. The module is unusuable, unless you have only one portal.
2) as previously stated by core team, they're aware of it but have no time frame for a fix
3) unless you want to do some serious re-coding, no fixing it yourself...
4) Just from what i've seen, i'd say its a combination of BOTH... i don't think the tables have enough data to properly differentiate between portals, and the application logic certainly isn't doing its "job" either.
5) search through this post - i've found several good modules that will do what this one should do. Some are free, some arn't - just VERY cheap