I tried to switch from the view's standard aggregate feature to view aggregator plus (I disable the standard views aggregate and changed the display to views aggregator plus). The resulting was wrong (look like taking a single random field value).

I had to enable the views' aggregation feature again and disable on each field the aggregation (from average to grouping), then disabling the views's aggregation worked and view aggregator plus calculated the correct average.

The expected behavior is that if the view's standard aggregate feature is disable it should have no effect even if their is still unused settings. I'm not sure if it's a view core bug or a views aggregator plus one.

Comments

gagarine created an issue. See original summary.

jordik’s picture

jordik commented
Status: Active » Postponed (maintainer needs more info)

Might be a problem with caching. Try to replicate the issue using Table as Format instead Table with aggregation options.

gagarine’s picture

gagarine commented

I think it's a problem linked with views itself. When you disable agregeation, the agregeation settings are still saved (I can see them in the config export). Agregestion Plus certainly do something based on those settings.