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.
Problem/Motivation
We currently do the join from the revision data table to the revision table the wrong way round
Proposed resolution
Fix it + write some tests.
Remaining tasks
Commit it
User interface changes
API changes
Data model changes
Comment | File | Size | Author |
---|---|---|---|
#20 | interdiff.txt | 598 bytes | dawehner |
#20 | 2630886-20.patch | 7.78 KB | dawehner |
| |||
#10 | interdiff.txt | 472 bytes | dawehner |
#10 | 2630886-10.patch | 7.68 KB | dawehner |
#3 | interdiff.txt | 3.65 KB | dawehner |
Comments
Comment #2
dawehnerThere we go.
Comment #3
dawehnerThis time with more files.
Comment #4
jibranLooks good to me. Test explains it all. Maybe before and after query of the test view and test only path would also help committers to understand the problem.
Comment #5
dawehnerYou mean completely broken vs. runnable?
Comment #6
jibranI just read #2626166-22: Create a view for content revisions and tested #2626166-28: Create a view for content revisions. Now I know what you mean so never mind me. This will also be usable for #1863906: [PP-1] Replace content revision table with a view so marking it as a major.
Comment #7
dawehnerAdded a remaining task :)
Comment #8
alexpottDo we need an empty update hook to force a cache clear? So that sites can the new views data?
Comment #9
dawehnerYeah I think we totally could. Do we need to test this update then as well?
Comment #10
dawehnerThere we go. I'm not entirely convinced that we need a test for an empty update function
Comment #11
jibranThanks.
Comment #13
dawehnerRandom bot fluctuation
Comment #16
dawehner.
Comment #17
jibranStill RTBC.
Comment #18
jibranStill RTBC.
Comment #19
alexpottYep we don't need a test for a cache clear but we need an new update group...
8.0.0-rc
is history :)We've been saying that anything with an update hook should be 8.1.x but I think this is an exception since it is a bug fix with an empty update hook - therefore I think we should put it in
updates-8.0.x
Comment #20
dawehnerSure, there we go.
Comment #21
xjmThe core committers and Views maintainers (alexpott, xjm, effulgentsia, tim.plunkett, and dawehner) agreed that this is a major issue.
Comment #22
jibranI think @alexpott can decide whether to use 8.0.x or 8.0.4. Other then this is RTBC.
Comment #23
catch8.0.x is good - there's no guarantee this gets released as part of 8.0.4 since that could be a security release, then it'd end up being 8.0.5 - also an update defgroup every six months is plenty.
Committed/pushed to 8.1.x and cherry-picked to 8.0.x. Thanks!
Comment #25
catchComment #27
jibran@catch you only committed http://cgit.drupalcode.org/drupal/commit/?id=f9930b4 to 8.0.x instead of whole patch.
Comment #29
jibranStill RTBC. We need to revert #24 and commit #20 to 8.0.x
Comment #31
catchArrgh. Thanks jibran. Reverted the bad commit and re-committed.