although the field is set up to link to original content, it doesn't. previous rc3 version worked well.

Posted a screenshot regarding this issue.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dawehner’s picture

Priority: Critical » Major
Status: Active » Postponed (maintainer needs more info)
FileSize
3.27 KB

A critical bug for me is that you can't use your site at all.

By just using the wizard i produced this view, which worked fine without any problems.
Can you please provide an export and some more information?

orakili’s picture

Status: Postponed (maintainer needs more info) » Active
FileSize
2.55 KB
2.61 KB

Edit: It comes from the changes from http://drupal.org/node/1044000 (http://drupalcode.org/project/views.git/commit/600c6b52565a71e67b49be947...)

To elaborate on this issue. It happens when the "use aggregation" option is selected. Exports of a simple test view with and without aggregation are attached. (It was working fine with rc3.)

The test view is as minimal as possible with only title as field. We can see in the query that the "nid" field is not added when "use aggregation" is on:

Without aggregation:

SELECT node.title AS node_title, node.nid AS nid
FROM 
{node} node
WHERE (( (node.status = '1') ))
LIMIT 10 OFFSET 0

With aggregation:

SELECT node.title AS node_title
FROM 
{node} node
WHERE (( (node.status = '1') ))
LIMIT 10 OFFSET 0
dawehner’s picture

Mh even i kind of think that this is more about a bug in your configuration i'm wondering whether it's worth to remove again.
There are in general two issues here

* Node: title is linked be default so by default aggregation doesn't work as you expect, because node:nid will be part of the query.
So removing it for groupby kind of make sense for me
* BUT: there are actually use cases for adding nid to the query, for example when summing up all field-data of a multi-value field.

idiotzoo’s picture

I missed this one and raised this as a duplicate report. Don't really understand the idea that this is configuration issue of the view. Views provides a simple tick box interface to make the title a link. This used to work, as described above, it no longer does. Behaviour has changed and this breaks the interface. I can't see this as anything other than a bug, and a pretty major one at that.

dawehner’s picture

Status: Active » Fixed

Well most time you actually don't want to aggregate and link to the title.

Committed a fix to 7.x-3.x and 6.x-3.x

rickmanelius’s picture

Status: Fixed » Active

I'm using Drupal 7.9 with views 7.x-3.0 and I can confirm that the links to titles do indeed work.

I also have a different installation with internationalization/localization and get an error... but that's caused by redirects outside of the control of views (the link is fine, but the error resides elsewhere).

@idiotzoo. Can you confirm with a fresh/test installation?

dawehner’s picture

Status: Active » Fixed

reset status.

idiotzoo’s picture

I'll take a look at that when I'm back home in the new year. Quite a few people filing bug reports for workbench moderation, which suffers this problem as it uses views with aggregation.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

ChrDr’s picture

Status: Closed (fixed) » Active

Sorry, I have to reopen this issue.

Using drupal 7.10 and the latest dev-version of views (Jan-11), the option "Link this field to the original piece of content" still does not link a node's title to the node if aggregation is used.

Of course, this can be worked around using the rewrite options, but then the option "Link this field to the original piece of content" still does not do what it promises to do.

JvE’s picture

Component: page displays » node data
Status: Active » Needs review

I cannot reproduce that ChrDr. For me:

  • views 7.x-3.0-rc3 November 16, 2011 - 19:25 works.
  • views 7.x-3.0 December 18, 2011 - 02:07 is broken.
  • views 7.x-3.x-dev January 11, 2012- 01:56 works.

I'm sticking with rc3 until fixes for this and some other issues have made it to stable.

@dereine: with this change you have only partially undone your previous change, leaving a (now) incorrect comment and a superfluous condition check. And I suspect the original issue #1044000: Take sure that fields don't add bad aliases to groupby queries can also be re-opened?

JvE’s picture

Status: Needs review » Active
dawehner’s picture

Priority: Major » Normal

Well sure there should be just one issue, everything else adds some overhead.

The issue is already fixed so i don't think the status should be major, you know you NEVER can fix all issues in the current "stable" version.

Feel free to provide a patch which fixes the incorrect comment.

ChrDr’s picture

Very strange. Trying again the dev-version, it works now. I am shure that I *did* have the dev-version. And I am pretty shure that I did flush the cache. I assume that it was somehow related to the current notice on the views module's home page: "There are currently issues with core's cache flushing that means one cache flush isn't necessarily enough." (although I thought that I did flush the cache twice...)

Anyway, I can confirm that:

views 7.x-3.0-rc3 November 16, 2011 - 19:25 works.
views 7.x-3.0 December 18, 2011 - 02:07 is broken.
views 7.x-3.x-dev January 11, 2012- 01:56 works.

pefferen’s picture

Issue summary: View changes
Status: Active » Closed (works as designed)

on views 7.x-3.7 the aggregated view has links to the nodes. Therefore the aggregation functionality works as expected.