Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Broken/missing handler (Module: node) …
Add a new node revision view, and you will see it.
Comment | File | Size | Author |
---|---|---|---|
#16 | 2229167-12.patch | 8.35 KB | dawehner |
#14 | 2229167-14.patch | 8.29 KB | marthinal |
#12 | interdiff-2229167-9-12.txt | 946 bytes | marthinal |
#12 | 2229167-12.patch | 8.35 KB | marthinal |
#9 | interdiff.txt | 2.06 KB | dawehner |
Comments
Comment #1
Bojhan CreditAttribution: 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 CreditAttribution: Bojhan commentedComment #4
Bojhan CreditAttribution: 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 CreditAttribution: 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 CreditAttribution: 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 CreditAttribution: marthinal commentedReviewing the patch :)
Comment #13
damiankloip CreditAttribution: 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 CreditAttribution: 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 CreditAttribution: 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!