[PP-1] Replace content revision table with a view

Created on 11 December 2012, over 12 years ago

Updated 26 July 2024, 9 months ago

Updated by #80

Convert content revision table to view.

Replace the content revision table with a view.

Mulitlangual support see #77
"Strip HTML" filter/rewrite doesn't work on the log messages.
If we want to retain the yellowish rowstyle for the default revision, and the striped rowstyle in bartik, this might be solved in Twig or we could add a rowstyle plugin to views.
The dropbutton misalignment error, see #1890266: dropbutton text fails to retain .dropbutton-widget width →

Before

After

N/A

N/A

WIP

This is one of the only content listings without it's own custom hook_ENTITY_operations().

📌 Task

Status

Postponed

Version

11.0 🔥

Component

Node system →

Last updated 2 days ago

No maintainer

Created by

🇺🇸United States tim.plunkett Philadelphia

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 9 months ago →
🇳🇿New Zealand quietone
Adding what this is postponed on to the remaining tasks per Remining tasks → .
Status changed to Postponed: needs info 4 days ago3:57am 9 April 2025
Comment 4 days ago →
🇦🇺Australia acbramley
I agree with #108 here, given we will eventually have a generic revision UI, node shouldn't really be doing its own thing with a view. We'd then need a view for every revisionable entity type, and then any non-core entity type would need to implement its own view otherwise the revisions UX would be different - this is bad for editors.

This doesn't seem like something core should support IMO, it could be something explored in contrib.

I'm inclined to set this to won't fix, but given the history here I want to see what others think.

Production build 0.71.5 2024