Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
views.module
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
30 Mar 2014 at 10:50 UTC
Updated:
29 Jul 2014 at 23:30 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Bojhan commentedI am not sure if "$display_options['fields']['title']['link_to_node_field_revision'] = 1;" is needed but, the remaining patch seems to resolve the issue. The modal for selecting fields seems broken, but I am not sure if thats related to this.
Comment #2
Bojhan commentedComment #4
Bojhan commented1: 2229167.patch queued for re-testing.
Comment #5
dawehnerNice work! I will review it properly tomorrow and probably also write a test for it.
That change is not needed.
Comment #6
Bojhan commentedYhea, kinda figured it wasn't needed. I am not sure how to test this :) I thought we had tests for it already but I guess that only tests whether we actually get results from this.
Comment #7
dawehnerHere is a test.
Comment #8
damiankloip commentedWhile we are changing these, shall we make them real booleans?
Didn't know you had to do that, I would have just called isNewRevision() and saved again. Does it need to be a new object? Sorry, haven't looked at the entity system changes for quite a while! More of a question than anything.
Also, how was anything working before without the join to node_revision from node_field_revision??
Comment #9
dawehnerNothing did, seriously!
I tried without the duplication and it simply did not worked at all.
Comment #10
tim.plunkettWas this supposed to be setNewRevision()? isNewRevision just returns a boolean, it doesn't *do* anything.
Otherwise I think this is fine.
Comment #11
dawehnerUPs yeah
Comment #12
marthinal commentedReviewing the patch :)
Comment #13
damiankloip commentedShould the tests have passed anyway when the nodes were not being set as new revisions as per Tim's comment above?
Comment #14
marthinal commentedBy default, when we are creating a new node, the new revision id is added to the node_revision table. So, should not fail and afaik we don't need to force a new revision in this test. Removing this method from the test...
Comment #15
damiankloip commentedSorry, do you have an interdiff for that? :)
Comment #16
dawehnerSorry but I really think #14 is wrong as it does not contain revisions anymore. We actively want to test that specfic scenario: nodes with multiple revisions.
Comment #17
tim.plunkettThe last hunk is out of scope, but it's not too bad.
Nice test, thanks!
Comment #19
catchCommitted/pushed to 8.x, thanks!