Views 2 integration [#349662]

Comment #1

NikLP CreditAttribution: NikLP commented 22 December 2008 at 14:44

What sort of features do we require for this to happen? Does having Views integration negate the need for any extra permissions, ie to move the default callback around and still be able to edit the list without having "Admin. Nodes" permissions?

Are we just talking about flagging a node's revisions as a views filter or something?

Log in or register to post comments

Comment #2

add1sun CreditAttribution: add1sun commented 22 December 2008 at 15:29

Basically I mean we should have at least the same views functionality that exists in the D5 version.

Log in or register to post comments

Comment #3

NikLP CreditAttribution: NikLP commented 22 December 2008 at 17:08

Ahhh. I didn't know there was any. Time to look at that version then, I suppose! ;)

Log in or register to post comments

Comment #4

webchick

she/they

English

Vancouver 🇨🇦

CreditAttribution: webchick commented 27 December 2008 at 17:18

Now that Views 2 can create listings of node revisions, I think it might be a good idea to remove any hard-coding listing pages/blocks from this module and replace them with equivalent views which could then be further customized for specific use cases. Seems like this would eliminate a lot of the feature requests that were running around during my day to show/not show the list of revisions to certain roles, or to add another column alongside the node title, or whatever.

Log in or register to post comments

Comment #5

NikLP CreditAttribution: NikLP commented 30 December 2008 at 17:45

I concur - the lack of Views support is what made me hack at the hook_menu_alter function to move the page to a different callback, which of course then broke most of the permissions. Of course, if the view works ok, then the permissions stuff should be irrelevant, which would be doubly awesome.